A customer is running out of memory when executing their application code. Is there a way to obtain additional memory for the application above the 2GB Windows default?

If you are running VA Smalltalk 7.5 or earlier, you can use the Microsoft utility EDITBIN to modify the executables. To modify a VA Smalltalk 7.5 or earlier executable, launch EDITBIN with the /LARGEADDRESSAWARE option -- for example:

Beginning with VA Smalltalk 7.5.1, the product executables (abt, nodialog, esvio, abtntsir, and abtntsrv) are linked with the /LARGEADDRESSAWARE switch so that more than 2GB of memory can be referenced if the Windows environment is setup properly to support such access. 

For information on the maximum amount of memory available to an application program on various Windows releases, refer to the MSDN article Memory Limits for Windows Releases.

For information on how to setup the Windows environment to support more than 2GB of application memory on 32-bit versions of Windows, see the MSDN article 4-Gigabyte Tuning.

On 64-bit versions of Windows, 32-bit applications always have access to 4GB of application memory. This has been true since VA Smalltalk 7.5.1.

Beginning with VA Smalltalk 9.0, applications built using the 64-bit version of VA Smalltalk will have access to the full memory address space accessible to a 64-bit process, which is theoretically somewhere between 2^63 and 2^64 bytes of memory. The 32-bit version of VA Smalltalk 9.0 will continue to have the same aforementioned 32-bit restrictions.