WOW another thread, must be 10 now all with does this work and no one actually posting "Hey this works". so I am assuming its crap

Yes this works. It enables me to play mods like 7DS on bigger maps etc.... Not sure if it changes checksum though and by that disable option to play on ICO .....

Best solution though is just to install linux and play on that. I do know that it was achieved that sins use 12 GB of memory on linux OS..... 

Not a solution for a usual gamer... first, you need the VMware ESX or ESXi who is far to be free... this is a hardware virtual machine who is run before any OS is loaded... i don't think that gamers will spend hundred if not thousand $$$ for make run faster a 35$ game...

Second, you need your own fine tune compiled WINE version... mainly moving the main memory cache for texture to the graphic card memory itself... not a big problem if you have a graphic card with plenty of memory... but a hell for people have graphic card with less or equal to 512 mb...

Finaly, forget online/LAN game... desync become the norm...

For info, I was the guy who was able to reach 12gb ram for sins... in fact, i am pretty sure that more is possible but i have not the few thousand $$$ needed for test it...

The large address Aware is a funny thing... make a software aware of something other don't mean that the software will be able to use it... in fact, the "large address Aware" thing simply add a tag at the begin of the code, it don't change the code itself...

Let take a simple example... i have a Aixam car who have a max speed of 45 km/h... if i apply a "200 km/h" sticker on my car, it will not make it run faster...

General Memory Limits                                                   32-Bit                                                          64-Bit
Total virtual address space (based on a single process)      4GB                                                            16TB
Virtual address space per 32-bit process                           2GB (3GB if system is booted with /3GB switch) 4GB if compiled with /LARGE­AD­DRESSAWARE (2GB otherwise)
Virtual address space per 64-bit Process                            Not applicable                                              8TB

Take a good look at the table... specialy at the "if compiled with... otherwise". on 32 bits system, the max virtual address space was 4 gb where 2 are for process and 2 are for system ( can be changed by editing the boot.ini )... with the "/LARGE­AD­DRESSAWARE" tag, application can use 2 gb by process ( 4 gb if it was compiled with the tag on )... sins is not recompiled with the little software piece that everybody speak off... the main advantage of the tag is that the sins game have 2gb for him alone in place of sharing the same 2gb with driver, antivirus, firewall and any other service in a 32 bit system...

Something similar can be reach with PAE and the 3GB on a 32 bits OS because since the pentium pro from 1995, processor are 36 bits ( good for a max of 64 GB of physical memory )... by example, windows 2000 datacenter 32 bits allow to use 32 gb of memory... The real limit are the Microsoft license... the 32 bits edition of server 2008 allow to use 64 gb of ram !!! Since game dev make a game for the majority of people, they can only use method who are shared by the more people... since usual Joe gamer have only the cheap limited home version of a Microsoft OS, game need to be build for these OS and cannot be made for a professional version...

In short, myfist0 is right... since on a x64 win OS with more that 4GB ram, the WOW64 mode used for run 32 bits application already allow to use 4gb by process if the application was compiled to use it... on 32 bits OS, only top version ( server, datacenter ) allow it... for desktop 32 bits version, best is to enable PAE and 3GB... PAE will put the address range of material over the 4 gb limit and 3G tag will allow 3GB for application and 1GB for OS...

By the way, the Fallout 3 mod is not a mod but a tool who apply several of the thing that i have post here... mainly increase the total virtual address space... but don't change the virtual address space per 32-bit process...

And finaly, a other possible problem is that it can in reality lead to more memory use... The main disadvantage of 64-bit is that relative to 32-bit , the same data occupies more place in memory (due to swollen pointers and other types and alignment padding). This increases the memory use for a process and can have lead to related to efficient processor cache utilization.

Final point is sins is a 32 bit application... and miracle don't exist... best is to work on a sins II where 64 bits and multicore will be something native... all the rest are tip and trick who can lead to little result or in some case to a more bad result...

the LAA is ONLY a flag change in the headers of the program, so any of the LAA altering programs can work on any of the programs that get out of ram errors, BUT ifyou have a 32bit windows it does NOT help unless you modify the deep settings for windows, and if you have a 64bit windows it CAN help, but sins IS CPU/ram SPEED bound, more so than ram SPACE bound, and unfortunately the LAA does NOT alter RAM access SPEEDS so you will get even worse slideshows due to the huge numbers of mines,strikecraft and frigates that sins AI likes to use.

harpo

greg30007, yes on windows 64bit, IT does allow the available ram per program to exceed the 2gb per program that is enforced in an UNMODIFIED 32 bit windows, and for that reason ON 64 BIT WINDOWS ONLY it can help when running the VERY LARGE MODS/maps, BUT you STILL NEED a high to VERY high ghz cpu to get the best out of sins, preferably with very high ghz RAM as well, and just for your info I have several machines with varoius speeds of cpu AND ram, and the most playable is the highest ghz per core cpu with the highest GHZ ram speed.

harpo