You're setting a switch on the hosts' .exe file so that the OS believes the executable is "LargeMemoryAware". This causes the loader to behave differently and allowing for a larger memory allocation. You need to run a utility (comes with some development packages) to apply the switch and that's what could be called a "hack". The problem is if the host application wasn't really written to be LMA it could lead to hard crashes.
If these tests are positive however, we could possibly bug the host developers to set the switch officially and thus support the 3GB switch. I've discussed this already with one developer and they had tested this before but with mixed results as they managed to get the system onto its knees during hard stress tests... Ups and downs.
/Mattias
If these tests are positive however, we could possibly bug the host developers to set the switch officially and thus support the 3GB switch. I've discussed this already with one developer and they had tested this before but with mixed results as they managed to get the system onto its knees during hard stress tests... Ups and downs.
/Mattias