Quote:
Originally Posted by propbeanie
Both apps accomplish the same thing, just with a slightly different interface. LAA uses the netFramework paradigm, while the 4Gig Patch is self-contatined. Both set the header bits of SH4.exe to "show" Windows that the app can address more RAM.
There is a 4Gig Patch on the site here, but I can never tell which is the one to link, so here is the NTCore 4Gig Patch page...
Warning!: noob information follows, just to cover all of the bases 
In the meantime, not having something giving SH4 a bit more "breathing room" could be your issue. You firstly want to right-click the SH4.exe app and choose Properties on the context menu. Then make certain the "Read-only" tick box is clear under "Attributes" on that first "General" tab encountered. When applying the LAA version, you do not receive a "message" of confirmation of a proper application of LAA. Most failures are usually caused by that Read-only attribute still being set. You can re-run LAA on the SH4.exe and see if the tick mark indicates the applet applied properly. Same with the 4Gig Patch though, but it will do a pop-up window with either the success or failure of its use.
Another contributing factor with crashes in mods is the failure to clear the Save folder after applying a major mod set. TMO, both the original and BH, are similar to Stock in some aspects, and to each other, but if you do not use Windows Explorer and delete the C:\Users \UserName \Documents \SH4 folder prior to running the new set-up, you might have similar issues. There can be other contributing causes, of course.  |
This is why I prefer 4Gb patch. You canīt forget to disable the read-only attribute in SH4.exe...
First: right click on SH4.exe, disable read-only. Then, apply LAA or 4Gb patch. If you donīt disable read-only, 4Gb patch alert you the app canīt update your exe file.
Best regards.
Fitzcarraldo
