https://bugs.winehq.org/show_bug.cgi?id=43434
Bug ID: 43434 Summary: StarCraft: Brood War stopped running after 1.19 update Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: iop_jr@yahoo.com Distribution: ---
Created attachment 58800 --> https://bugs.winehq.org/attachment.cgi?id=58800 Log when trying to start StarCraft 1.19
After the recent update, there's a similar message to bug #42741. But even using staging ClientSdk.dll fails to initialize. So StarCraft is broken again.
Full debug logs:
http://www.filedropper.com/log_24
https://bugs.winehq.org/show_bug.cgi?id=43434
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Does anyone know how to debug this with a windows debugger (like x32dbg/olly) without getting this debugger-specific crash?
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #2 from Igor Polyakov iop_jr@yahoo.com --- slackner posted this patch on IRC that solves one of the issues (GetProcessWorkingSetSizeEx) :
https://bugs.winehq.org/show_bug.cgi?id=43434
Richard Allen ra@ra.is changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ra@ra.is
https://bugs.winehq.org/show_bug.cgi?id=43434
graham@heunox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |graham@heunox.com
https://bugs.winehq.org/show_bug.cgi?id=43434
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=43434
Luiz Angelo Daros De Luca luizluca@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |luizluca@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
termac terror.macbeth.I@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |terror.macbeth.I@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
ogunden@phauna.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ogunden@phauna.org
https://bugs.winehq.org/show_bug.cgi?id=43434
Emanuel Rietveld codehotter@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |codehotter@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
Kenton MacDowell kmacdowell2013@fau.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kmacdowell2013@fau.edu
--- Comment #3 from Kenton MacDowell kmacdowell2013@fau.edu --- The issue persists in Wine Staging 2.13.
https://bugs.winehq.org/show_bug.cgi?id=43434
ratonwasher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ratonwasher@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
Andreas Schallenberg Andreas.Schallenberg@Eurobild.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Schallenberg@Eurobi | |ld.com
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #4 from Igor Polyakov iop_jr@yahoo.com --- To clarify, the full debug logs I posted are with slackner's patch since I get a GetProcessWorkingSetSizeEx issue when I run 1.19 without it.
https://bugs.winehq.org/show_bug.cgi?id=43434
whatbug n296869@rtrtr.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |n296869@rtrtr.com
https://bugs.winehq.org/show_bug.cgi?id=43434
m8r-lh9sv7@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |m8r-lh9sv7@mailinator.com
https://bugs.winehq.org/show_bug.cgi?id=43434
kap kyle.pollock7@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.pollock7@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #5 from Igor Polyakov iop_jr@yahoo.com --- I asked Andrew Wesie and he pointed me in the right direction.
1. I built the latest staging from git. https://github.com/wine-compholio/wine-patched this is up to date 2. I had to set StarCraft.exe to Windows 2003 so it would run - Windows XP resulted in a crash, Windows 10 resulted in the previous bug
https://bugs.winehq.org/show_bug.cgi?id=43434
Vedran Rodić vrodic@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vrodic@gmail.com
--- Comment #6 from Vedran Rodić vrodic@gmail.com --- I confirm Starcraft 1.19 works with https://github.com/wine-compholio/wine-patched, and Windows version set to Windows 2003 or Windows Vista
https://bugs.winehq.org/show_bug.cgi?id=43434
Igor Polyakov iop_jr@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|StarCraft: Brood War |StarCraft: Brood War |stopped running after 1.19 |doesn't run without setting |update |the Windows version to 2003 | |or Vista
https://bugs.winehq.org/show_bug.cgi?id=43434
bancha@bancha.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bancha@bancha.eu
https://bugs.winehq.org/show_bug.cgi?id=43434
Ivan Bodrov securesneakers@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |securesneakers@gmail.com
--- Comment #7 from Ivan Bodrov securesneakers@gmail.com --- I tried to run it using Wine 2.14. It indeed does not start if Wine emulates Windows XP by default because of missing GetProcessWorkingSetSizeEx() in kernel32.dll, but this is precise behavior you can get on XP, since GetProcessWorkingSetSizeEx() is only available since Vista.
After changing Windows version to Vista or anything newer StarCraft does not start because of integer zero division when initializing ClientSdk.dll:
0008:0009:exception in PE entry point (proc=0x10025ae0,module=0x10000000,reason=PROCESS_ATTACH,res=0x1) 0008:0009:Ret PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_ATTACH,res=0x1) retval=0 ... 0008:0009:Call PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_DETACH,res=0x1) 0008:0009:Ret PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_DETACH,res=0x1) retval=0 0008:err:module:attach_process_dlls "ClientSdk.dll" failed to initialize, aborting 0008:err:module:LdrInitializeThunk Main exe initialization for L"H:\Games\StarCraft\StarCraft.exe" failed, status c0000094
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #8 from Igor Polyakov iop_jr@yahoo.com --- If you have problems with the launcher, just put `wine StarCraft.exe -launch` command line parameter to launch the game directly without the launcher.
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #9 from Ivan Bodrov securesneakers@gmail.com --- Using "wine StarCraft.exe -launch" does not change anything for me. But I noticed that if I run "winedbg StarCraft.exe" then it fails differently (it is able to show message box). Trace output from the same thread:
002d:exception in TLS callback (proc=0x1073d8f8,module=0x10000000,reason=PROCESS_ATTACH,reserved=0) 002d:Call PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_ATTACH,res=0x1) ... 002d:Call user32.MessageBoxW(00000000,0033f680 L"Game Initialization Failed!",0033f6c8 L"ERROR",00000010) ret=100262fa
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #10 from Igor Polyakov iop_jr@yahoo.com --- You're supposed to use Windows 2003
https://bugs.winehq.org/show_bug.cgi?id=43434
lukas.schneiderbauer@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lukas.schneiderbauer@gmail. | |com
https://bugs.winehq.org/show_bug.cgi?id=43434
BogDan Vatra bog_dan_ro@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bog_dan_ro@yahoo.com
https://bugs.winehq.org/show_bug.cgi?id=43434
J kalaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kalaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43434
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #11 from Anastasius Focht focht@gmx.net --- Hello Igor
--- quote --- that if I run "winedbg StarCraft.exe" then it fails differently (it is able to show message box). Trace output from the same thread:
002d:exception in TLS callback (proc=0x1073d8f8,module=0x10000000,reason=PROCESS_ATTACH,reserved=0) 002d:Call PE DLL (proc=0x10025ae0,module=0x10000000 L"ClientSdk.dll",reason=PROCESS_ATTACH,res=0x1) ... 002d:Call user32.MessageBoxW(00000000,0033f680 L"Game Initialization Failed!",0033f6c8 L"ERROR",00000010) ret=100262fa --- quote ---
Please don't run Blizzard games under a debugger unless you know what you are doing. There are anti-debugger checks in the startup code. Besides these software protection related issues with StarCraft are already known/documented in various tickets.
I still don't get the purpose of this ticket?
https://us.battle.net/forums/en/starcraft/topic/20754255399
--- quote --- Win XP WILL NOT work beyond 1.16.1. Unfortunately, the Installer for 1.18 DOES NOT tell the User this information; INSTEAD, the 1.18, (StarCraft Anthology), Installer goes through the ENTIRE installation, AND THEN prevents the game from Launching. --- quote ---
IMHO this ticket is invalid.
Regards
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #12 from Igor Polyakov iop_jr@yahoo.com --- The game doesn't run perfectly out of the box for me without the workaround.
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #13 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- Windows XP resulted in a crash, Windows 10 resulted in the previous bug --- quote ---
I still don't get it. Why are you complaining about 'Windows XP' here? Since some time ago, newly created WINEPREFIXes have 'Windows 7' setting by default.
If you are recycling an old WINEPREFIX with 'Windows XP' setting and expecting the game to run then you obviously didn't get the message. Blizzard officially stated that Windows XP is a no longer unsupported OS (EOL) and there are many forums posts/announcements about this change. They even implemented several measures, showing warnings, preventing launchers to run etc.
Everything else is already covered by other bug reports.
-> INVALID
Regards
https://bugs.winehq.org/show_bug.cgi?id=43434
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #14 from Igor Polyakov iop_jr@yahoo.com --- Windows 7 does not work on my machine.
https://bugs.winehq.org/show_bug.cgi?id=43434
Igor Polyakov iop_jr@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #15 from Igor Polyakov iop_jr@yahoo.com --- I just tested on Wine 3.7 staging and I no longer need the work-around (I needed it for the 32 bit profile), so I'm marking this as fixed
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #16 from Nikolay Sivov bunglehead@gmail.com --- Does it work with vanilla Wine 3.7 or 3.8?
https://bugs.winehq.org/show_bug.cgi?id=43434
--- Comment #17 from Igor Polyakov iop_jr@yahoo.com --- staging 3.7
I don't have the option to set it to staged for some reason
https://bugs.winehq.org/show_bug.cgi?id=43434
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED Ever confirmed|0 |1
--- Comment #18 from Nikolay Sivov bunglehead@gmail.com --- Reopening.
https://bugs.winehq.org/show_bug.cgi?id=43434
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #19 from Maciej Stanczew maciej.stanczew+b@gmail.com --- This bug was submitted when ClientSdk.dll issue was present also in Staging. It doesn't seem to be valid anymore - Starcraft can be launched without changing Windows version to 2003 or Vista. Of course a PE build of Staging is needed for it to work, but this is covered by bug 42741. Shouldn't this one be closed or marked as duplicate?
https://bugs.winehq.org/show_bug.cgi?id=43434
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED CC| |o.dierick@piezo-forte.be
--- Comment #20 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I'll mark this fixed since the issue here was that the staged patchset from bug 42741 didn't work in win7/win10 mode for some reason and then the OP reported that it was fixed.
(In reply to Igor Polyakov from comment #15)
I just tested on Wine 3.7 staging and I no longer need the work-around (I needed it for the 32 bit profile), so I'm marking this as fixed
Marking fixed.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=43434
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.14.