Hi, Background: Windows 2000 Professional, Windows 2000 Server, Windows XP Professional only normally support 2GB of physical RAM for userland. A special boot.ini switch exists "/3GB" that allows a user mode application to benefit from 3GB of physical RAM on a 4GB system (the remaining 1GB goes to kernel).
According to Microsoft, an application can use 3GB of RAM if the binary has a special linker flag when compiled. http://www.microsoft.com/hwdev/platform/server/PAE/PAEmem.asp Excerpt =================== Application Changes. No APIs are required to support application memory tuning. However, it would be ineffective to automatically provide every application with a 3-GB address space. Executables that can use the 3-GB address space are required to have the bit IMAGE_FILE_LARGE_ADDRESS_AWARE set in their image header. If you are the developer of the executable, you can specify a linker flag (/LARGEADDRESSAWARE). To set this bit, you must use Microsoft Visual Studio Version 6.0 or later and the Editbin.exe utility, which has the ability to modify the image header (/LARGEADDRESSAWARE) flag. For more information on setting this flag, see the Microsoft Visual Studio documentation. Some manufacturers preconfigure their applications to use application memory tuning, making it unnecessary for you to make this change. For more information, see your application documentation and contact your application vendor to determine whether they support Large Address Awareness or whether you can enable it in their application. Question for SAPDB =================== What is SAPDB's stance on support of this? Is the LARGEADDRESSAWARE flag set? I couldn't figure out how to use EDITBIN.EXE to see what the current value is, it only seems to allow changing the flag :) My 4GB system is still on order, so I haven't had a chance to test in person yet... Thanks. Stephen _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
