From owner-freebsd-bugs Fri Mar 3 15:10:24 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA05651 for bugs-outgoing; Fri, 3 Mar 1995 15:10:24 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id PAA05643 for ; Fri, 3 Mar 1995 15:10:21 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA06483; Fri, 3 Mar 95 16:02:00 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9503032302.AA06483@cs.weber.edu> Subject: Re: Problems with 950210-SNAP To: joerg_wunsch@uriah.heep.sax.de Date: Fri, 3 Mar 95 16:02:00 MST Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <199503032225.XAA01119@uriah.heep.sax.de> from "J Wunsch" at Mar 3, 95 11:25:01 pm X-Mailer: ELM [version 2.4dev PL52] Sender: bugs-owner@FreeBSD.org Precedence: bulk > > > 1. BIOS memory reduced by 1K to 639K causing warning message, > > > machine report 640K BIOS memory using the 2.0-RELEASE version > > > If your CMOS value has changes, I seriously consider testing to > > see if you have an MBR virus or have rewritten your MBR. > > No Terry, this is simply caused by the fact that some BIOSes tend to > steal 1 KB off the base memory to put their ``hard disk parameter > table'' there. So when you ask the BIOS about base memory, they tell > ya 639 K. AMI gave you the choice between the stolen kilobyte and > placing the table on BIOS stack... I know. If you look in the system initialization code, you'll see that this was patch one (by me) to 386BSD 0.1, at least in the patchkit patch order. The problem is that he says that the amount reported is different between the 2.0-RELEASE and the current snap. Since it is otherwise impossible to have changed, something he did or something he ran (voluntarily or involuntarily) changed it for him. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.