Leon said:
Right! Not only is it slower, it's erratic, and as an inferior, and
incomplete
a product that MS has ever marketed. It will only recognize 3 meg of
memory.
As it turns out, the memory limitation of a Windows 32 bit OS, is
an artificial situation. Someone has hacked Vista 32 bit for example,
and run 8GB of memory on it. PAE supports at least up to a 36 bit
address (more bits than that, in the AMD architecture), so technically,
a 32 bit OS could address a lot more. But Microsoft decided that would
eat into their server business, so they limited the "memory license" to
4GB (minus the space used by hardware busses).
http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm
The hardware busses take address space. A major consumer of space on
those busses, is the memory on the video card.
The hardware solves this problem, by remapping memory above 4GB. But
the Microsoft license, prevents you from accessing up there. Depending
on how the mapper is set up, it may "hoist" everything above 3GB, into
a place that you can't use it. That is one reason for the 3GB number.
There is one motherboard (in a Dell), where an unfortunate choice was
made to change the lift point to 2GB. On that particular system, even
with a video card with tiny onboard memory, a 32 bit Windows OS will
only allow 2GB max. The offset and granularity of the lifting thing,
affects what you get to use. At least Dell was good enough, to
warn about this, on one of their web pages for the product.
If a user installs 4GB of memory, and two 512MB video cards in SLI,
they get to use 2.75GB of memory, after all bus addressing requirements
are met. If you make the video card memory big enough (Asus Mars),
you can get to a point where there is no longer any room to address
system memory (with a 32 bit OS).
One other tidbit I've learned. You *can* use memory above 4GB, with this
product. I've actually tested this. Using WinXP 32 bit, with 6GB memory
installed in the computer, I had 3.2GB free for programs, and a 2GB
RAMDisk for high speed storage. That is a total of 5.2GB on a 32 bit
system. It seems that somehow, you can define a RAMDisk up there, but
not run programs up there. On the one hand, PAE makes the addressing
part of the problem a solved issue, but the real question, is how
did these people manage to map what they needed ? That's pretty
clever.
http://memory.dataram.com/products-and-services/software/ramdisk
My RAMDisk in action, benching at close to 4GB/sec. On a 32 bit OS...
And living in "high memory". I only kept this config long enough,
to finish the benchmark.
http://img196.imageshack.us/img196/8694/hdtunedataram2gbabove.gif
Paul