Posted January 09, 2025
... spent too many hours trying to figure out why this does not work.
The re-release (now the exe is calling the game "Sudden Strike Forever", which was "Sudden Strike GOLD", et cetera) has newly compiled executables which seem to be obfuscating any attempt of WINE to invoke the proper DLLs to run this game.
No WINETRICKS (DirectPlay), WINEPATH, WINEDLLOVERRIDES or other measures are working (afai have been able to test). WINEDEBUG points to a random inability to read the "Menu_dll.dll". The internal error code is "126" which one might think points to the code line, but does not.
The search on the web about this topic is ... tragic. I could have asked my dog, if he learned to program in C. Same result.
I do not know the history of this game, the devs and publisher(s) behind it. Maybe you guys know more about the history of the current executables.
I would bet my salary from 1985 that the original game (CD-Version) will run in Wine without a hitch. The SS1-Demo still runs great (just tested it. No - cannot make the full game run with the demo.exe)
Any takers?
I leave this post here (unless it will be deleted) to encourgage smarter brains to figure out how to make the current GOG/Steam versions to run with WINE/Proton.
This here is a great bad example how 're-releases' and fondling with the old game files and original executables are causing issues in the long run. Not only with WINE or Proton, trying to make sense of the commands, but also with every ever evolving Microsoft update, which turns Windows 10 and 11 into an actively 'anti-gaming' OS, with all the DRM-ish Kernel and memory management fondling, in the name of 'Privacy & Security' and Anti-Exploit marketing blah. Old and not so old (abandoned) game executables cannot keep up with the times and will end up - eventually - in the quarantine bin (or getting straight up deleted by Windows - cuz, 'users' cannot be trusted?!)
The re-release (now the exe is calling the game "Sudden Strike Forever", which was "Sudden Strike GOLD", et cetera) has newly compiled executables which seem to be obfuscating any attempt of WINE to invoke the proper DLLs to run this game.
No WINETRICKS (DirectPlay), WINEPATH, WINEDLLOVERRIDES or other measures are working (afai have been able to test). WINEDEBUG points to a random inability to read the "Menu_dll.dll". The internal error code is "126" which one might think points to the code line, but does not.
The search on the web about this topic is ... tragic. I could have asked my dog, if he learned to program in C. Same result.
I do not know the history of this game, the devs and publisher(s) behind it. Maybe you guys know more about the history of the current executables.
I would bet my salary from 1985 that the original game (CD-Version) will run in Wine without a hitch. The SS1-Demo still runs great (just tested it. No - cannot make the full game run with the demo.exe)
Any takers?
I leave this post here (unless it will be deleted) to encourgage smarter brains to figure out how to make the current GOG/Steam versions to run with WINE/Proton.
This here is a great bad example how 're-releases' and fondling with the old game files and original executables are causing issues in the long run. Not only with WINE or Proton, trying to make sense of the commands, but also with every ever evolving Microsoft update, which turns Windows 10 and 11 into an actively 'anti-gaming' OS, with all the DRM-ish Kernel and memory management fondling, in the name of 'Privacy & Security' and Anti-Exploit marketing blah. Old and not so old (abandoned) game executables cannot keep up with the times and will end up - eventually - in the quarantine bin (or getting straight up deleted by Windows - cuz, 'users' cannot be trusted?!)