4GB Patch vs LAA

D-Jones · 07-27-23, 01:44 PM

What's the difference? I've been (trying) to run TMO-BH with LAA. No go. Whenever it gets "busy", i.e., when I'm attacking a convoy or TF, it CTDs. Haven't tried it with the 4GB Patch. If it CTDs with LAA, is there a chance that the 4GB patch might correct this?

Thanks.

propbeanie · 07-27-23, 03:00 PM

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.

D-Jones · 07-27-23, 03:40 PM

Yeah. As always with Widows they make things unnecessarily hard. I tried un-checking "Read Only" and it reverts back seconds later. This is their strongarm, unasked for security.

I'm going to try again with the 4GB patch. My save folder will BE EMPTY.

Thanks, prop.

propbeanie · 07-27-23, 06:59 PM

If you have SH4 installed in a Program Files folder, then that could be the reason the SH4.exe reverts back to Read-only. Having SH4 installed there would cause other modding issues also, and cause several CTD situations. You would want to re-install the game in a folder of your own making not in Program Files, such as "C:\Games\Silent Hunter...", or whatever you want to name it. Also, if you are not running Windows with Administrator priveleges, that could possibly do it also.

D-Jones · 07-27-23, 08:48 PM

No. It's installed outside of Program File--both installs. One has FotRS and the other TMO-BH (or it will shortly--again).

Is it just the SH4.exe that has to be off Read Only, or the entire game folder? I got the exe off the accursed Read Only.

propbeanie · 07-27-23, 09:17 PM

At least the SH4.exe, and the FileManager.dll in the SH4 game folder have to be write-enabled (Read-only box cleared). If using two or more folders of SH4 games, you should of course use MultiSH4 to keep their data segregated...

D-Jones · 07-27-23, 10:53 PM

Both the exe and FileManager.dll have Read Only un-checked. Going to try it with the 4GB patch.

Prop, I just cut/paste the current save game folder onto my desktop. Been working fine so far.

fitzcarraldo · 07-28-23, 12:24 PM

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

D-Jones · 07-28-23, 09:46 PM

It's working! At least so far. The 4GB patch seems to have done it. Tested it on a couple of large TFs, and no CTD yet. That WAS when I always got CTDs.

Great mod. Now I have to figure out how to actually survive and/or get an occasional torpedo to not be a dud or go under the enemy ship, but that's Okay. That's what the real guys had to deal with. Wonder if they had Sub Rage? I would have. I'd have needed therapy.

07-27-23, 01:44 PM	#1
D-Jones Helmsman Join Date: Jan 2023 Posts: 107 Downloads: 173 Uploads: 0	4GB Patch vs LAA What's the difference? I've been (trying) to run TMO-BH with LAA. No go. Whenever it gets "busy", i.e., when I'm attacking a convoy or TF, it CTDs. Haven't tried it with the 4GB Patch. If it CTDs with LAA, is there a chance that the 4GB patch might correct this? Thanks.

07-27-23, 03:00 PM	#2
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,098 Downloads: 451 Uploads: 2	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. __________________ "...and bollocks to the naysayers" - Jimbuna

07-27-23, 06:59 PM	#4
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,098 Downloads: 451 Uploads: 2	If you have SH4 installed in a Program Files folder, then that could be the reason the SH4.exe reverts back to Read-only. Having SH4 installed there would cause other modding issues also, and cause several CTD situations. You would want to re-install the game in a folder of your own making not in Program Files, such as "C:\Games\Silent Hunter...", or whatever you want to name it. Also, if you are not running Windows with Administrator priveleges, that could possibly do it also. __________________ "...and bollocks to the naysayers" - Jimbuna

07-27-23, 09:17 PM	#6
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,098 Downloads: 451 Uploads: 2	At least the SH4.exe, and the FileManager.dll in the SH4 game folder have to be write-enabled (Read-only box cleared). If using two or more folders of SH4 games, you should of course use MultiSH4 to keep their data segregated... __________________ "...and bollocks to the naysayers" - Jimbuna

07-27-23, 03:40 PM	#3
D-Jones Helmsman Join Date: Jan 2023 Posts: 107 Downloads: 173 Uploads: 0	Yeah. As always with Widows they make things unnecessarily hard. I tried un-checking "Read Only" and it reverts back seconds later. This is their strongarm, unasked for security. I'm going to try again with the 4GB patch. My save folder will BE EMPTY. Thanks, prop.

07-27-23, 08:48 PM	#5
D-Jones Helmsman Join Date: Jan 2023 Posts: 107 Downloads: 173 Uploads: 0	No. It's installed outside of Program File--both installs. One has FotRS and the other TMO-BH (or it will shortly--again). Is it just the SH4.exe that has to be off Read Only, or the entire game folder? I got the exe off the accursed Read Only.

07-27-23, 10:53 PM	#7
D-Jones Helmsman Join Date: Jan 2023 Posts: 107 Downloads: 173 Uploads: 0	Both the exe and FileManager.dll have Read Only un-checked. Going to try it with the 4GB patch. Prop, I just cut/paste the current save game folder onto my desktop. Been working fine so far.

07-28-23, 09:46 PM	#9
D-Jones Helmsman Join Date: Jan 2023 Posts: 107 Downloads: 173 Uploads: 0	It's working! At least so far. The 4GB patch seems to have done it. Tested it on a couple of large TFs, and no CTD yet. That WAS when I always got CTDs. Great mod. Now I have to figure out how to actually survive and/or get an occasional torpedo to not be a dud or go under the enemy ship, but that's Okay. That's what the real guys had to deal with. Wonder if they had Sub Rage? I would have. I'd have needed therapy.