[Reprinted] windows 2K3 server x86 4G memory test note

[Reposted from:Http://blog.pcbeta.com/html/64/t-337164.html]

I had nothing to do today. I started a 2G DDR2 667 Kingston memory and installed it in my notebook. Started my 4G memory experience.

First, describe the configuration of my notebook. Sony cr392b
CPU: t8100
Memory: single 2G DDR2-667
Motherboard: pm965
Hard Disk: 250 GB
Wireless NIC: atheros 5006
The notebook officially states that the maximum memory is 3 GB.

Operating System:
Windows 2008 server x64
Windows 2008 server x86
Windows 2003 Server x86

Multi-system boot Environment

This test does not pursue performance. It only tests whether the 4G memory is supported normally and whether the memory is stable. The memory stick parameters are exactly the same as those of Sony's original memory stick. This is an accident. Because I was going to buy MHz.

After the memory is plugged in, I enter all three systems and use the Everest and system information display functions to confirm that 4G memory is correctly identified and enabled.

Use Photoshop to open 10 mb psd files at the same time, as well as some large office applications.ProgramSwitch back and forth, and perform some memory-consuming graphics processing.
These tests are successful and quite stable,
I did not record the specific test data because it was mainly for testing stability.

The following lists the status of each system.

1. 2003 SERVER + SP2 x86 automatically enables PAE (physical address extension). In this case, the/PAE parameter I is not in Boot. ini, and only/noexecute = optiin is enabled.
The system recognizes the normal 4G memory and displays the physical address extensions in the computer attributes. The program running and loading speed has been significantly improved, and the program switching is smooth.
I do not play games, so I will not comment on this.

Problem: the original normal wireless network card is displayed in the Device Manager, the device cannot be started, and the latest driver has been replaced. Other hardware is normal

2. 2008 SERVER + SP1 x86 automatically enables PAE (physical address extension). It can be seen in bcdedit that PAE takes effect automatically.
The system recognizes the normal 4G memory and displays the physical address extensions in the computer attributes. The program running and loading speed has been significantly improved.
The wireless Nic device cannot be started. If the latest driver is changed, the device cannot be started.

3. 2008 SERVER + SP1 x64. The system identifies a normal 4G memory, and all hardware is properly driven and available. The running and loading speed of the program has been significantly improved, and the program switching is smooth. The wireless Nic device is normal.

Test description.
The 32-bit win2003 and win2008 in this notebook can well identify 4G memory. Of course, the main board pm965 itself supports better is also one of the reasons.
However, the wireless Nic cannot be started.

After querying some information, some memory resources are retained in the 32-bit System for driver and resource addressing of hardware devices.
4G memory can be enabled through physical address extension, but some hardware drivers still use the original address. In 4G memory, PAE occupies this part of the address. As a result, the hardware cannot be started normally. To solve this problem, you must adjust the resource usage of the PCI device through bios, enable memory address ing, or change the resource address by hardware driver. Avoid memory usage. In this way, the system and hardware can be coordinated.

However, my laptop BIOS's PCI and other settings are blocked and there are no available options. This is the sorrow of the laptop BIOS. However, PAE can only be disabled and 3G memory can be used to coordinate the work between the memory and the wireless network card.

Dep must be disabled when PAE is disabled in Windows 2003,
In boot. ini, change noexecute to/execute = optin. Do not add/PAE,

In Windows 2008 x86, you can use the easybcd tool to set advanced options, change/noexecute = alwaysoff, and do not select to enable Pae.

After the restart, the wireless network cards of the two systems are restored to normal. However, the memory can only use 3 GB.

The above is a 32-bit system that uses a 3G solution to handle hardware incompatibility.

In a 64-bit system, the driver of the wireless network card uses a 64-bit addressing address, which perfectly supports 4 GB memory.

By the way, 64-bit applications cannot be used perfectly due to laptop architecture problems, so I cannot make more comments on memory performance here.

Some other friends on the Internet have encountered this problem. Although the hardware is different, some are sound cards, some are network cards, and only PAE is disabled to achieve the goal of balancing.

Of course, I personally will soon transition to 2008 or even 64-bit applications, and then 4G will be fully usable.

My experience does not necessarily apply to the hardware and software configurations of everyone. It is just a reference for friends who encounter similar problems.