Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!imci3!imci4!newsfeed.internetmci.com!avalon.net!localhost!vince From: Vince Kub <vince@gw2kbbs.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Intel Endeavor install problems (639K != 640K -> SIG 11) Date: Sat, 6 Apr 1996 12:05:30 -0600 Organization: Avalon Networks Inc. Lines: 27 Message-ID: <Pine.BSF.3.91.960406115709.10897D-100000@localhost> References: <4judaa$c9k@spirit.dynas.se> <4k1iok$krb@uriah.heep.sax.de> NNTP-Posting-Host: foobar.gw2kbbs.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: vince@localhost In-Reply-To: <4k1iok$krb@uriah.heep.sax.de> On 4 Apr 1996, J Wunsch wrote: > mikko@dynas.se (Mikko Tyolajarvi) writes: > > > When booting, all report: > > > > BIOS basemem (639K) != RTC basemem (640K) > > Nothing you really need to care for. It means your BIOS, or some > virus :), steals one kilobyte from the BIOS-reported basemem, for > example to install the disk parameter table there. Most commonly the "missing" 1k is the BIOS code neccessary to support the PS/2 style mouse on those systems that have a built-in AUX port (most of them nowadays). In DOS/Windoze environments the phenomenon is usually masked by the presence of a memory manager but when something goes wrong with that machine Joe User notices the missing memory and then hears that this is a sign of a virus (which it sometimes is). Trying to get rid of the "infection" can then make for some black comedy . . . . - Vince