It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
Warcraft II Battle.net EditionWarcraft 2 wont start(17 posts)(17 posts)
(17 posts)
Pages:
1
2
This is my favourite topic
Posted April 01, 2019
I played the game for a couple of hours yesterday and when i tried to start it today nothing happens

when i press the play button in GOG the launcher pops up but when i click the to play warcraft 2 nothing happens

hope you can help
Posted April 01, 2019
there is option in gog galaxy menu when u choose warcraft 2 -> more ->manage the installation-> check/fix
Posted April 02, 2019
avatar
Szwagiermc: there is option in gog galaxy menu when u choose warcraft 2 -> more ->manage the installation-> check/fix
Which is a "first possibility," but not the most likely one. I, also, am having a similar issue here, with the game going through the full "pick what you want to play" sequence... when I click "single player" and then the upgraded version, my screen simply "winks out" and the game ends, without ever entering the gameplay engine. This seems to only be the case with the "new" version, not with the "classic" one, in this case.

EDIT: I also just tested it with the "original" version and it crashes to desktop as well.

Interestingly, a disk-based install on this machine runs perfectly, though.

I ran the file-checking feature of "Galaxy" twice now, so I know it's not a corrupted installation. It'd definitely a bug. But it seems like it's probably a relatively straightforward one... and since at least one other person is having it, besides me... no error message, no nothing. The game starts fine, you go through everything up until starting a new game... and then it fails.

The full event manager log entry reads as follows. I'll redact anything PERSONAL in there.

************************************************************************************************************** *******

Log Name: Application
Source: Application Error
Date: 4/1/2019 11:23:01 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: (redacted)
Description:
Faulting application name: Warcraft II BNE.exe, version: 2.0.2.1, time stamp: 0x3b098e14
Faulting module name: HsSrv.dll, version: 1.0.10.917, time stamp: 0x4c930239
Exception code: 0xc0000005
Fault offset: 0x000010ba
Faulting process id: 0x3eec
Faulting application start time: 0x01d4e90baa7b63a7
Faulting application path: F:\GoG\GalaxyClient\Games\Warcraft II BNE\Warcraft II BNE.exe
Faulting module path: C:\Windows\SysWOW64\HsSrv.dll
Report Id: fffa5d3c-54fe-11e9-a05f-5cf3707b1877
Event Xml:
<Event xmlns="[url=http://schemas.microsoft.com/win/2004/08/events/event"&gt]http://schemas.microsoft.com/win/2004/08/events/event"&gt[/url];
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-04-02T04:23:01.000000000Z" />
<EventRecordID>241338</EventRecordID>
<Channel>Application</Channel>
<Computer>(redacted)</Computer>
<Security />
</System>
<EventData>
<Data>Warcraft II BNE.exe</Data>
<Data>2.0.2.1</Data>
<Data>3b098e14</Data>
<Data>HsSrv.dll</Data>
<Data>1.0.10.917</Data>
<Data>4c930239</Data>
<Data>c0000005</Data>
<Data>000010ba</Data>
<Data>3eec</Data>
<Data>01d4e90baa7b63a7</Data>
<Data>F:\GoG\GalaxyClient\Games\Warcraft II BNE\Warcraft II BNE.exe</Data>
<Data>C:\Windows\SysWOW64\HsSrv.dll</Data>
<Data>fffa5d3c-54fe-11e9-a05f-5cf3707b1877</Data>
</EventData>
</Event>
*************************************************************************************************

Now, HsSvr.dll is marked from "C-Media," which is the creator of the sound chip in my current system, so it SEEMS that this is likely an audio-related issue (explaining why both the classic and "upgraded" versions would see this). Note, this has NOT been an issue for Diablo, or for any other version, nor for the version of Warcraft 2 I have running in DOSBox based upon a CD installation.

EDIT: I just ran the program after changing from my default sound card (with 7.1 surround, running at a high fidelity setting) to a basic USB sound adapter, in stereo and lower quality sound, and THAT seems to be "workable."

So... it's established, the issue is with the Windows version of this not being compatible with either (a) any C-Media adapter, or (b) surround sound, or (c) high-quality sound reproduction.

One more edit:

I have now tested with 5.1 surround, and that seems to be OK. 7.1 Surround, however, fails. Additionally, while running at 16-bit, 48000hz sound works, running at 24-bit, 192000 sound fails. There are other options in the list of choices for me, but so far that's what's proven to work.

Reducing sound fidelity to 48000hz at 16-bit and keeping at 5.1 channel or at stereo (or presumably mono) allows the game to run in either of the two GoG provided versions. But running about either of those results in a "no message crash to desktop."
Post edited April 02, 2019 by CLBrown
Posted April 02, 2019
There have been other reports of sound issues (mostly no sounds heard except music, not crashes - although who knows how many of the generic "it won't run" posts match this fault) with multi-channel configurations, for both Diablo and Warcraft. Seems GoG only tested with basic stereo output.
Posted April 02, 2019
avatar
squid_80: There have been other reports of sound issues (mostly no sounds heard except music, not crashes - although who knows how many of the generic "it won't run" posts match this fault) with multi-channel configurations, for both Diablo and Warcraft. Seems GoG only tested with basic stereo output.
Yep, sure seems they only tested in very limited fashion.

I've run a bit deeper testing, having gotten THIS far.

As it turns out, mono, stereo, quadraphonic, 5.1 surround, or 7.1 surround all work. Given the below.

16-bit or 24-bit sound both work, also given the below.

The trick is, the game ONLY works as long as the playback is at 48000hz... no higher, no lower. 44100hz, 96000hz or 192000hz each results in the "no message crash."

So, at least on MY system, the root cause can be traced to that. Somehow, the sound playback from the program is "mis-interfacing" with the audio system if the audio system is not set to 48000 hz.

I typically leave mine at 192000 hz, as I have this wired into a nice "audiophile" level sound system, and do some audio work on it as well as using it for entertainment. It seems that if I ever want to play the GoG release of Warcraft 2, I'll have to lower my sound fidelity... at least until GoG and Blizzard fix this bug.

EDIT... ONE... MORE... TIME...

Well, not quite. I tested each individually, but as it turns out, at 48000, 24-bit, 7.1 causes the crash as well, but 5.1 does not.
Post edited April 02, 2019 by CLBrown
Posted April 02, 2019
Huh... well, I just played through the first level, at 24bit x 48000 at 5.1. The game ran fine. But at the end of the mission, another "message-free crash to desktop" (without saving my game , of course). Again, sound related.

Hmmm... and even if I reduce to stereo, 16-bit, 48000hz, the game still crashes (with a "sound DLL" basis) upon finishing the level. But you DO get to save before ending the level, so if you remember to do so, you can pick up there next time. Sadly, this isn't much help, though. Especially since attempting to load the saved game results in... yep... the crash.
Post edited April 02, 2019 by CLBrown
Posted April 02, 2019
avatar
Szwagiermc: there is option in gog galaxy menu when u choose warcraft 2 -> more ->manage the installation-> check/fix
Thanks this fixed it
Posted March 07, 2021
avatar
CLBrown: ...having a similar issue here, with the game going through the full "pick what you want to play" sequence... when I click "single player" and then the upgraded version, my screen simply "winks out" and the game ends, without ever entering the gameplay engine...
I had the same problem, but nothing to do with sound. Tried all of the fixes, nada. Yesterday I was getting "can't save file" errors because I'd hit a limit. I was deleting from the Save menu, but (some of) the deleted file would reappear and I'd get the error again. I kept on playing (didn't exit gam until EOD).

Today the crash-on-start happened. After some research, I hypothesized that the save file limit was reached. Files are saved at:

C:\Program Files (x86)\GOG Galaxy\Games\Warcraft II BNE\Save

I had 108 files. I deleted down to 37, and everything worked. I'm thinking the limit might be 100ish, and if you reach it in game things get wonky, and the crash-on-start problem will start on next load.
Post edited March 07, 2021 by eldergod0515
Posted March 09, 2021
avatar
eldergod0515: Today the crash-on-start happened. After some research, I hypothesized that the save file limit was reached. Files are saved at:

C:\Program Files (x86)\GOG Galaxy\Games\Warcraft II BNE\Save

I had 108 files. I deleted down to 37, and everything worked. I'm thinking the limit might be 100ish, and if you reach it in game things get wonky, and the crash-on-start problem will start on next load.
Glad that worked for you, but it wasn't the case for me. I no files in that location at all, as this was a new installation.

Good to know a potential solution for others, but it didn't work for me.
Posted March 24, 2021
I've been having a similar problem. The whole thing just crashes less than a second after launching, it can't even get through the blizzard logo. I'm running an up to date version of Windows 7 if that helps at all, and am just doing the default launch of the program through gog galaxy.

Any suggestions? I've tried "Verify/Repair" galaxy but I'm not that well versed with files and compatibility so I've not done much else.
Posted April 09, 2021
Agreed. It does not start on my Windows 10 build 1909. Event Viewer indicates smackw32.dll is the culprit:

---
Faulting application name: Warcraft II BNE_dx.exe, version: 2.0.2.1, time stamp: 0x3b098e14
Faulting module name: smackw32.dll, version: 3.0.0.0, time stamp: 0x34bfa011
Exception code: 0xc0000005
Fault offset: 0x0000375e
Faulting process id: 0x1bbb8
Faulting application start time: 0x01d72cc26efa3c47
Faulting application path: C:\Program Files (x86)\GOG Galaxy\Games\Warcraft II BNE\Warcraft II BNE_dx.exe
Faulting module path: C:\Program Files (x86)\GOG Galaxy\Games\Warcraft II BNE\smackw32.dll
Report Id: bcefaff0-f54c-4b09-8c73-60c4303c3ac9
Faulting package full name:
Faulting package-relative application ID:
---

EDIT: Adding Warcraft 2 BNE and Warcraft 2 BNE_dx to the Data Execution Prevention exceptions fixed my problem.
Advanced System Settings --> Performance --> Data Execution Prevention tab.
Post edited April 09, 2021 by nslay
Posted June 11, 2021
high rated
I found something that fixed the issue for me, hopefully it works for others as well. Try deleting smackw32.dll from the game's folder. This caused the game to be playable again for me.

Been having this exact problem, the game was working perfectly for months (i've logged ~30 hours on it!) and then suddenly it didn't want to open without immediately crashing (twice, for some reason). Like others, the crash logs in event viewerpointed to smackw32.dll as the culprit. Nothing suggested online fixed it , not reinstall, verify/repair, run as admin, compatibility mode, DEP exception, changing playback device, updating drivers, etc (DEP was already disabled for all but windows services, too).

On a whim I deleted smackw32.dll from the game's folder, the same one with Warcraft II BNE_dx.exe in (at Z:\GOG\Warcraft II BNE for me), and tried to launch the game. And voila, it launches without crashing now! The only problem i've noticed so far is the blizzard intro doesn't play anymore, small price to pay for a working game though. My bigger concern is if the mid-campaign/finale cinematics will cause issues.

EDIT: After further playtime, the only issue that arises from doing this is the cinematics don't play, the game simply acts is if they had and moves on. This includes the Blizzard logo, intro cinematic, and all mid-campaign and finale cinematics. So it isn't a perfect solution, but at least it works for playing the game and you can look the cinematics up on YouTube if you want to see them.
Post edited June 15, 2021 by XWhiteish
Posted September 16, 2021
Thank you very much! I read your post and deleted the smackw32.dll and it solved my problem!
Posted February 04, 2022
avatar
XWhiteish: I found something that fixed the issue for me, hopefully it works for others as well. Try deleting smackw32.dll from the game's folder. This caused the game to be playable again for me.

Been having this exact problem, the game was working perfectly for months (i've logged ~30 hours on it!) and then suddenly it didn't want to open without immediately crashing (twice, for some reason). Like others, the crash logs in event viewerpointed to smackw32.dll as the culprit. Nothing suggested online fixed it , not reinstall, verify/repair, run as admin, compatibility mode, DEP exception, changing playback device, updating drivers, etc (DEP was already disabled for all but windows services, too).

On a whim I deleted smackw32.dll from the game's folder, the same one with Warcraft II BNE_dx.exe in (at Z:\GOG\Warcraft II BNE for me), and tried to launch the game. And voila, it launches without crashing now! The only problem i've noticed so far is the blizzard intro doesn't play anymore, small price to pay for a working game though. My bigger concern is if the mid-campaign/finale cinematics will cause issues.

EDIT: After further playtime, the only issue that arises from doing this is the cinematics don't play, the game simply acts is if they had and moves on. This includes the Blizzard logo, intro cinematic, and all mid-campaign and finale cinematics. So it isn't a perfect solution, but at least it works for playing the game and you can look the cinematics up on YouTube if you want to see them.
Thank you! This worked for me :)
Posted February 05, 2022
Im install widescreen hack mod. And that result in crashing game refering to smakw32.dll. But restoring whole game folder from backup (i did backup whole game), removing WinRegisty entries - still smakw32.dll error. A lot of launches for both Classic\Enchancent and CD version happened on same machine just day ago.
Probably im need in Alt+F4-Restart 9exactly in that way). Im not sure why DEP start to cause this, so not sure if this is DEP related.

There is a way to disable DEP for each exe without changing option to "enable to all programs" by WinRegisrty. In that case easy to do so is set this to steam or galaxy exe file and start game from them as links.
Pages:
1
2
This is my favourite topic
Community
Warcraft II Battle.net EditionWarcraft 2 wont start(17 posts)(17 posts)
(17 posts)