OK, there's some scary stuff going on here but I think MultiSH4 is least likely to to blame for the simple reason it does so little.
MultiSH4 patches a file called FileManager.dll. If a problem can be traced back to FileManager.dll then it's fair enough to ask what if any part MultiSH4 had to play. If the problem does not involve FileManager.dll then MultiSH4 is automatically excluded from consideration.
The only thing MultiSH4 does to FileManager.dll is to find and if necessary change the three characters that constitute the hard-coded SH4 save game folder name within My Documents. If you're using an unpatched version of FileManager.dll then those characters will be "SH4", as in "My Documents\SH4". If you've patched it to something like "UBM" then you can check that very simply by running MultiSH4 again and just reading what it reports as the current save file name.
I have copies of every version of FileManager.dll and on my system MultiSH4 works with all of them. If anyone thinks MultiSH4 is causing them a problem then try this test:
1. Create a temporary folder.
2. Copy MultiSH4 1.5 and FileManager.dll into that folder.
3. Run MultiSH4.
If MultiSH4 successfully patches FileManager.dll in that environment then it's easy to see that the problem must lie elsewhere.
|