Memory Does Not Match Amount of Installed Memory
Reported Memory Does Not Match Amount of Installed Memory
http://support.microsoft.com/default.aspx?kbid=146912
When you view the Performance tab in System properties, the amount of memory reported may differ from the actual amount of memory installed in the computer.
This behavior can occur for any of the following reasons:
1. Himem.sys is not using all the memory on an EISA computer.
2. A driver or program loading from the Config.sys or Autoexec.bat file is claiming a portion of RAM.
3. A virtual device driver loading from the System.ini file is claiming a portion of RAM.
4. A protected-mode driver is causing the memory mismatch.
5. The registry is damaged.
6. A CMOS setting is disabling some of the RAM.
7. You have the "maxphyspage=" setting in your System.ini file set to restrict Windows 95 from using some of the installed memory.
8. Ramdrive.sys is being loaded in the Config.sys file.
METHOD 2
When you view the Performance tab in System properties, the amount of memory reported may differ from the actual amount of memory installed in the computer.
This behavior can occur for any of the following reasons:
- Himem.sys is not using all the memory on an EISA computer.
- A driver or program loading from the Config.sys or Autoexec.bat file is claiming a portion of random access memory (RAM).
- A virtual device driver loading from the System.ini file is claiming a portion of RAM.
- A protected-mode driver is causing the memory mismatch.
- The registry is damaged.
- A CMOS setting is disabling some of the RAM.
- You have the "maxphyspage=" setting in your System.ini file set to restrict Windows from using some of the installed memory.
- Ramdrive.sys is being loaded in the Config.sys file.
- You are using a video adapter that is integrated into the motherboard.
Back To The Top
Bud's CDs FREE MP3s Alphabetical Index Of Everything In This Site