Maximum memory for Windows 2003 server 32 bits on ProLiant DL385

[G. Vollant]

Hello,
I want upgrade memory on a ProLiant DL385 to the maximum. The computer uses Windows 2003 server x86, standard edition, SP2.

I found somes low price (refurbished part from ohter server) 512 MB and 1 GB DDR ECC registered module. (I found two module of 512 MB for 2*$40, by example)

If I upgrade the server to 4 GB of Ram, I suppose I'll be able use only 3.6 GB under Windows 2003 server. (because there is memory space for pci extended configuration space.

If I put more than 4 GB of RAM , do you known if Windows 2003 server standard will be able to use more than 3.6 GB ?

I prefer a server with 6 GB of physicall memory (only 4 GB used) and a server with 4 GB memory (and 3.6 GB used), because memory is cheap and will be useful?

On a workstation (Asus P5B motherboard), I found a "remap" option on the Bios to move the memory on the "pci configuration space" above of 4GB. Is the HP setup contain this feature?

[Blazhev_1]

Hi,

you are right.
1. Windows Server Standard Edition supports no more than 4GB, even if you install 6GB.

2. There is a memory not available to OS that is reserved for the PCI space(there is a customer advisory about that). To recognize the more space(above 4GB) you need the /PAE(Physical Address Extension) switch in the boot.ini, so with standard edition the memory reported must be 4GB too, not 3.75. Normally PAE is used in standard edition to bing the above 4GB space to the OS...
In boot.ini after /fastdetect write /PAE...
This must show all 4GBs...

Check :

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00883105&prodTypeId=15351&prodSeriesId=428936

Regards,
Pac

[G. Vollant]

the HP document (your link) say
"The installed system memory that would have been located in these regions is automatically remapped to above the 4 GB boundary on HP ProLiant servers."

So, for Windows 2003 server 32 bits standard edition with 4 GB of memory, the solution is just install 4 GB of physicall memory (more is not useful), and add /PAE on boot.ini.

/PAE will be used to use 256 MB or 512 MB which will be remapped above 4GB

[G. Vollant]

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01199560
page say

"For ProLiant AMD Opteron servers including the ProLiant DL385, ProLiant DL585, ProLiant BL25p, ProLiant BL35p, and ProLiant BL45p servers, there are no plans to add support for remapping the 512 MB of memory lost on these platforms. However, future ProLiant AMD Opteron servers with PCI Express Technology will support remapping the 512 MB of memory lost to PCI memory above 4 GB."


http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c00883105&prodTypeId=15351&prodSeriesId=428936

say
"The addressable memory space allocated to the PCI Hole and the PCI Extended Configuration Space is not available for installed system memory. The installed system memory that would have been located in these regions is automatically remapped to above the 4 GB boundary on HP ProLiant servers. This means that the memory is still available to the OS, but 32-bit operating systems must be configured to access above 4 GB."

[juan quesada]

Hi.

check http://msdn2.microsoft.com/en-us/library/aa366796.aspx
and http://msdn2.microsoft.com/en-us/library/aa366778.aspx

they are Microsoft Documents that explain PAE (Physical Address Extension)

How to enable PAE on Windows.

1. Click on â Startâ .
2. Navigate to â Control Panelâ .
3. Then click on â Systemâ .
4. When the â System Propertiesâ window opens click on the â Advancedâ tab.
5. Then click on â Settingsâ .
6. When the â Startup and Recoveryâ window loads click on â Editâ , after that the â boot.iniâ file will open.

7. The â boot.iniâ file will look something like this by default, make sure you select the OS you want to recognize the additional memory.
8. Add â /PAEâ at the end of the string and youâ re good to go.
9. Now click on â Fileâ .
10. And finally click â Saveâ to finish.

Something really important that you should know. This procedure is not supported by HP. use it under your own risk (I tried this serveral times and worked fine)