Is it possible for a program (like a batch file) to launch another program and - key point - set the LAA flag "on" in the program that's being loaded? Theoretically it's just a change to a single hex. Some background on this request:
I work on a mod for an older game (Medieval Total War II @2007) that does not have the LAA flag set in the exe. As a result, the game only uses 2 GB of memory, and as a mod team we've pushed the engine so far that we're experiencing an increasing number of "random" CTDs. Fortunately there are utilities which change the flag, thereby making the application "Large Address Aware". We've tested this and it works great - all the random CTDs disappear, and the mod is highly stable - literally 100's of turns without a crash.
The problem is, the LAA utility tool changes the exe, and the game company considers this a violation of the EULA, so we are prohibited from even discussing this as an option. We've made it quite clear that we aren't distributing modified exes nor advocating true EULA violations (this flag is common to ALL applications), but simply trying to explain how game users can solve this issue on their own, all to no avail.
So we're trying to figure out whether it's possible to set the flag using some other method, one which doesn't involving changes to the exe itself. Any thoughts or guidance would be greatly appreciated.
I work on a mod for an older game (Medieval Total War II @2007) that does not have the LAA flag set in the exe. As a result, the game only uses 2 GB of memory, and as a mod team we've pushed the engine so far that we're experiencing an increasing number of "random" CTDs. Fortunately there are utilities which change the flag, thereby making the application "Large Address Aware". We've tested this and it works great - all the random CTDs disappear, and the mod is highly stable - literally 100's of turns without a crash.
The problem is, the LAA utility tool changes the exe, and the game company considers this a violation of the EULA, so we are prohibited from even discussing this as an option. We've made it quite clear that we aren't distributing modified exes nor advocating true EULA violations (this flag is common to ALL applications), but simply trying to explain how game users can solve this issue on their own, all to no avail.
So we're trying to figure out whether it's possible to set the flag using some other method, one which doesn't involving changes to the exe itself. Any thoughts or guidance would be greatly appreciated.
