Lem said:
Note that of the 4GB Address Space that Tim's article mentions, only a
2GB virtual address space is available to a given application (unless
the /3GB boot.ini switch is used, in which case the max app address
space is 3GB for a properly coded app).
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
Lem, you're confusing physical and virtual memory. My article talks
about the physical side of things: using the 4GB (physical) address
space to access RAM as well as video memory, etc.
Each process in WinXP gets a 4GB virtual address space, regardless of
how much physical RAM is actually installed (I assume this is greatly
increased in 64-bit OSs). That virtual address space, as you say, is
evenly split between the OS and the user program unless the /3GB
switch is used.
More physical RAM will make it easier for the OS to keep working
storage sets of more virtual address spaces in RAM, thereby reducing
the usage of the swap file and speeding things up. But all of a
virtual address space is (as far as I know) used to address virtual
memory - not video or anything else.