Eliot Miranda wrote:
Here are some additional links...
/LARGEADDRESSAWARE (Handle Large Addresses)
http://msdn.microsoft.com/en-us/library/wz223b1z.aspx
Memory Limits for Windows and Windows Server Releases
http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx
I learnt something new reading this article. For Win 8.1 64-bit, the
/3GB switch is not applicable or required. However the
/LARGEADDRESSAWARE�� linker option is critical for both 32-bit and
64-bit VMs. Its only the default setting that changes between compiling
32-bit or 64-bit applications. Some extracts...
Limits on memory and address space depend on whether the
IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and
4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is
set or cleared by using the /LARGEADDRESSAWARE linker option.��
4-gigabyte tuning (4GT), also known as application memory tuning, or
the /3GB switch, is a technology (**only applicable to 32 bit
systems**) that alters the amount of virtual address space available to
user mode applications.
On x64-bit MS Windows, User-Mode virtual address space for each 32-bit
process
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
On x64-bit MS Windows, User-Mode virtual address space for each 64-bit
process
8 TB With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
cheers -ben