From owner-freebsd-hackers Wed Mar 4 08:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25051 for freebsd-hackers-outgoing; Wed, 4 Mar 1998 08:02:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from enteract.com (good@enteract.com [206.54.252.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25045 for ; Wed, 4 Mar 1998 08:02:16 -0800 (PST) (envelope-from good@enteract.com) Received: (from good@localhost) by enteract.com (8.8.8/8.7.6) id KAA21666; Wed, 4 Mar 1998 10:02:03 -0600 (CST) From: The Good/John Scholvin Message-Id: <199803041602.KAA21666@enteract.com> Subject: Re: Help: 2.2.5 crashing on boot after I add RAM To: khansen@njcc.com Date: Wed, 4 Mar 1998 10:02:02 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <34FC31FA.5B5D@njcc.com> from "Ken Hansen" at Mar 3, 98 11:38:18 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ken Hansen wrote: > The Good/John Scholvin wrote: > > I've got an old Compaq Contura 4/25 laptop which I'm trying to install 2.2.5 > > on, and I've got a problem I can't figure out. The machine boots the GENERIC > > kernel fine when it has 8MB RAM installed. I've got an expansion RAM card > > which, when installed, ups the total to 20MB. > > I wonder if the ram expansion is good - have you tried using the same > exp. board > under a different OS - Win or other? Just a thought... Well, how embarrassing. Turns out I got bad RAM. DOS booted OK but I never tried running Windows, and DOS never exercised the high addresses since I don't have HIMEM or any of that junk. A little diagnostic tool found the bad bits up around the 15M point. Thanks for the advice, and thanks to all you FreeBSD hackers for putting out an unbelievably cool product. John -- good@enteract.com is The Good, or probably John Scholvin speaking for them. OUR WEB SITE IS UP! Check out http://www.enteract.com/~good To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message