- Joined
- Apr 7, 2009
What first comes to mind is to check the applicable "boot.ini" file, if it exists (typically at the root of a boot partition or floppy). The boot.ini file is a file used by the Windows 2000/XPServer 2003 and 64-bit versions' boot loader (NTLDR) to specify operating systems and with what parameters to load the operating systems.
If there is a parameter you are uncertain about, find more information about it. Be aware that a reduction of RAM availability need not be explicit. For example, a kernel or HAL may be explicitly defined in boot.ini and the defined kernel or HAL may limit or fail to make available all RAM.
Be aware that if a floppy drive has a boot loader with a boot.ini file, it takes precedence if the floppy precedes other devices in boot order.
The next thing that comes to mind is your use of sessions. It is clear from the picture you provided that the use of multiple sessions are permitted (otherwise the connection to the machine via Terminal Services/RDP would not have been possible). I am somewhat unfamiliar with the use and management sessions, but I would think that memory allocated to a resources from or for a session might not be available to other sessions. Also, it would seem plausible that a limitation on the amount of RAM might be explicitly set.
Please note that the task manager and system properties of Windows 2000/XP/Server 2003 family operating systems report on available RAM (in use plus free memory) rather that installed RAM.
Do you have physical access to the machine at issue?
If there is a parameter you are uncertain about, find more information about it. Be aware that a reduction of RAM availability need not be explicit. For example, a kernel or HAL may be explicitly defined in boot.ini and the defined kernel or HAL may limit or fail to make available all RAM.
Be aware that if a floppy drive has a boot loader with a boot.ini file, it takes precedence if the floppy precedes other devices in boot order.
The next thing that comes to mind is your use of sessions. It is clear from the picture you provided that the use of multiple sessions are permitted (otherwise the connection to the machine via Terminal Services/RDP would not have been possible). I am somewhat unfamiliar with the use and management sessions, but I would think that memory allocated to a resources from or for a session might not be available to other sessions. Also, it would seem plausible that a limitation on the amount of RAM might be explicitly set.
Please note that the task manager and system properties of Windows 2000/XP/Server 2003 family operating systems report on available RAM (in use plus free memory) rather that installed RAM.
Do you have physical access to the machine at issue?