Article View: comp.sys.ibm.pc.misc
Article #6020Re: Reclaiming Memory From BIOS setup...
From: Russell J Mellon
Date: Mon, 09 Nov 1992 11:11
Date: Mon, 09 Nov 1992 11:11
18 lines
1520 bytes
1520 bytes
In article <1992Nov6.233959.3288@rei.com> fox@rei.com (Fuzzy Fox) writes: >umnoor@ccu.umanitoba.ca (Nasir Ahmed Noor) writes: > >>When system starts up, it reports [familiar tick sound and RAM test] only >>7808K. It should, according to my calcs, report 8192K [i.e. 8 Meg]. > >The missing 384K is between 640K and 1024K. This is the area where I/O >devices (cards, etc.) put their address space. RAM can only be made to >appear in this location if you have a Shadow RAM chipset which will put >it there. It may be that this address space is inaccessible on your >system. > I have the same problem with my 386-40mhz. The problem is caused by shadow RAM. certain chip sets put 384k of reserved memory ( I don't know what that is, but it isn't the memory between 640k and 1meg ) in low memory with an I/O port-selectable method of getting to it. got this info from QEMM. have to use the NOSH (no shadow ram) option. don't worry too much, there ain't much that can be done.
Technical Details
Message-ID:
<BxG4FM.6vB@mentor.cc.purdue.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!purdue!mentor.cc.purdue.edu!sage.cc.purdue.edu!russ1066References:
<BxA7D7.9Gx@ccu.umanitoba.ca> <1992Nov6.233959.3288@rei.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!ames!purdue!mentor.cc.purdue.edu!sage.cc.purdue.edu!russ1066 From: russ1066@sage.cc.purdue.edu (Russell J Mellon) Subject: Re: Reclaiming Memory From BIOS setup... Message-ID: <BxG4FM.6vB@mentor.cc.purdue.edu> Sender: news@mentor.cc.purdue.edu (USENET News) Organization: Purdue University Computing Center References: <BxA7D7.9Gx@ccu.umanitoba.ca> <1992Nov6.233959.3288@rei.com> Date: Mon, 9 Nov 1992 11:11:46 GMT Lines: 20