This is an application that assists in making applications large address aware. When a 32-bit application is large address aware, it can access up to 4 GiB on x64 operating systems and all memory that isn't used by the operating system and other applications on x86. 64-bit versions of Windows require no modifications to the operating system to benefit from this application; however, in 32-bit versions of Windows, you must increase the user memory setting. Instructions how to do this are in spoiler below. It is not advised to use this application if you have less than 3 GiB of RAM.

This application may not work on older executables (predating 2000).

Basic mode:
1) Open an executable to modify (click on the "..." button to browse). Alternatively, you can drag and drop a file on the gray text box.
2) Check or uncheck the box specifying whether or not you want to make it large address aware.
3) Click on save to commit the changes.

Intermediate and advanced mode (Advanced shown):
1) Add files through the "Add" drop down menu or click on on Add Files. Alternatively, you can drag and drop the files into the list view.
2) Select the files you wish to modify by checking the boxes or using the "Select" drop menu.
3) Either click on "Switch Large Address Aware" (turns true to false and false to true) or select an option from the "With Selected" drop down menu.
4) If you wish to remove files from the list, you may do so in Advanced mode via the "Remove" drop down menu.

Requirements:
.NET Framework 3.5 or newer (get the latest version from Windows Update under optional updates).

Disclaimer:This software is provided without guarantee nor warranty. Use at your own discretion. The creators of this software and the owners of this site cannot be held liable for any damages inflicted.

Process Monitor:
Process Monitor is useful in discovering if making the application large address aware will be helpful.

WARNING: Upgrading the operating system to 64-bit is the best solution. Continue at your risk!

1. In Windows Explorer, navigate to the system partition. This is the partition that holds hardware specific Windows files such as Boot.ini and NTLDR.

2. If you cannot see the Boot.ini file, it could be because the folder options are set to hide protected operating system files. If this is the case, in the Explorer window, click Tools, Folder Options, and then click View. Clear the Hide protected operating system files (Recommended) check box. When prompted, click Yes.

3. After the Boot.ini file is visible in Explorer, right-click the file, click Open With, and then click Notepad to open the file.

4. Add the /3GB switch to the end of the line starting with "multi" under the [Operating Systems] section.

5. Save the changes and close Notepad.

6. Restart the computer for the change to take effect.

1. In Windows Explorer, navigate to the system partition. This is the partition that holds hardware specific Windows files such as Boot.ini and NTLDR.

2. If you cannot see the Boot.ini file, it could be because the folder options are set to hide protected operating system files. If this is the case, in the Explorer window, click Tools, Folder Options, and then click View. Clear the Hide protected operating system files (Recommended) check box. When prompted, click Yes.

3. After the Boot.ini file is visible in Explorer, right-click the file, click Open With, and then click Notepad to open the file.

4. Remove the /3GB switch from the end of the line starting with "multi" under the [Operating Systems] section.

1. Open command prompt with Adminitrator rights. To do this, go to Programs, Accessories, right-click on Command Prompt and select "Run as Administrator."

2. Enter the following at the prompt and press enter:

Code:

bcdedit /set IncreaseUserVA 3072

3. Close the prompt and restart the computer.

1. Open command prompt with Adminitrator rights. To do this, go to Programs, Accessories, right-click on Command Prompt and select "Run as Administrator."

2. Enter the following at the prompt and press enter:

Code:

bcdedit /deletevalue IncreaseUserVA

3. Close the prompt and restart the computer.

2.0.4 - Drag and Drop now only accepts executables. Added Remove -> From List and History -> All and Selected menu options. This is useful for if you enable "Load Previous Files."
2.0.3 - Adds an option for loading previous files. Note that enabling this, the application will hang on startup or immediately after checking it as it attempts to load all the files previously examined by the application.
2.0.2 - Fixed a major bug in 2.0.1 that would prevent it from working.
2.0.1 - Adds basic multithreading support.
2.0.0 - Has three modes (Basic, Intermediate, and Advanced) with drag and drop support, the capability of handling multiple files simutaneously, and numerous other major changes.

Drag and drop from the desktop may not work (it will show the access denied icon when hovering) on some computers with UAC enabled because the program requires higher permissions than the desktop. Use the browse functionality to add the files if this is the case.

Many, MANY modern games that crash to desktop are because they're hitting the 2GB limit.

As said in the first post: this does NOTHING on its own if you have a 32 bit OS. You need to modify the OS to change from a 2GB limit to a 3GB limit (which is different between XP and vista - the instructions in the OP are for XP)

I modded sims3 some time ago (and uploaded it to people) - solved my crashing in the game after a few hours at +3 speed

Click to expand...

When I saw that, I knew it was possible (didn't know about it or anything prior to seeing the modified Sims 3 binary). I wasn't inspired to write the application until today when I had the same problem with The Saboteur (ironically, also an EA title).

I checked Mass Effect, Startopia (circa 2001), The Saboteur, and The Sims 3. It should work on other applications like Microsoft Word 2003 (not that I would) as well.

Edit: I could make a separate application to enable the /3GB or perform the BCDEDIT operation. I think I would want to keep it separate because it only needs to be done once.

Does anyone know if the instructions are the same for Windows 7 as they are for Windows Vista?

No, unless the application is already Large Address Aware. You need 4 GiB of RAM and Windows 7/Vista x86 to do that (strongly advised against if you don't.). It can actually slow down the operating system because it doesn't have as much memory to play with.

Edit: I could make a separate application to enable the /3GB or perform the BCDEDIT operation. I think I would want to keep it separate because it only needs to be done once.

Click to expand...

I looked into this but it doesn't look possible. As expected, Windows is guarding boot.ini with its life so no application not belonging to the "SYSTEM" user group can access it. I could only make it update Vista/7.

Which executable are you try to edit? If it is an executable belonging to Windows, Windows may forbid that it be edited. Also, if the application is currently running, it may need to be closed prior to saving.

The exes were GTA IV, Quake 4, NFS Shift, UT3 & SimCity Societies
Yeah.. am quite familiar with the Admin rights stuff, so that's not the issue, nor were the exes in question locked/write protected - with only a question mark over the GTA IV exe.

Large Address Aware won't work on applications with security features that perform a checksum on the binary. If using the application on a binary has unintended consequences, simply run LAA again and put the checkbox to the way it was before modifying it.

Large Address Aware won't work on applications with security features that perform a checksum on the binary. If using the application on a binary has unintended consequences, simply run LAA again and put the checkbox to the way it was before modifying it.