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

×
i used the default settings and choose the classic game and BANG!!!!!!!!!!!!!!

CPU was 100% in USE system was unstable, fans were spinng lake mad , lots of noise , unable to make screenshot , had to shutdown pc manually ( power of) cause nothing replied ...................... almost a flatliner


This is not supposed to happen .... (✖╭╮✖)
Disabling DEP also solved my issue, now the game boots without problem. I hope that sooner or later GOG or Blizzard patches the game so we don't need to disable it, through. It's a safety hazard, after all.

Thanks, people.
avatar
St.Ross: It would be rather problematic to help all of you in this thread, so if you still experience any issues with the game, feel free to contact our wonderful support team :)
Thats very nice of the team ... but this might give you lots and lots of single requests, while maybe a common solution might be considered first.
avatar
nicolas_yad: Crashes at start for me too, I've just contacted support.
I'm really sad that it doesn't work, I was really looking forward playing Diablo again. :(
same here but instead i had to pull the plug to prevent 'fire in the hall'

Its is possible to make old win she ites work though, redalert seems to be free now read it online, seems some 'fans' made a menu to tweak things, it has a lot of options , and i managed to make it work for my setup :D

Anyway... kinda sad that a happy afternoon turned bad ......, and almost a ++++ PC *sighs*

avatar
Xulomander: Disabling DEP also solved my issue, now the game boots without problem. I hope that sooner or later GOG or Blizzard patches the game so we don't need to disable it, through. It's a safety hazard, after all.

Thanks, people.
DEP? so we have to turn off some things again in order to make a game run ? (︶︹︺)


edit: if i disable all the sync, ansitorpic nonsens and other 'filters' and reduce the frames / hertz or whatever they call it to 60 sh ites then i the cpu bashing goes down to 56 which is still too high ...
anyway its getting late im off ... :D
Attachments:
Post edited March 07, 2019 by gamesfreak64
avatar
bdschnei: I experienced similar symptoms. For me it helped to disable the Data Execution Prevention (DEP) feature in Windows.
(Either globally or by putting the diable executable to the exception list)
This is not a fix, but a workaround.
The game is not working as is downloaded.
GoG you are selling a non-working game.

edit: the same issue is present on Act of War
which came out 1-2 years ago, and I don't believe they fixed it there either
Post edited March 08, 2019 by StrEagle
Disable Vsync too !!!

OPnly classic version work for me, But the Non classic version don't work at all
Post edited March 08, 2019 by Bottox
Still not working for me
Tried reinstaling, tried the DEP thing. Nothing works. But the Belzebub and Technoborg on original D1 works. ( I am using laptop with integrated INTEL HD 4600 chipset)
Wow, GoG didn't bother to fix the DEP issue? This is exactly the kind of thing you're meant to take care of when getting old games to run on current systems!

You know you can patch(hexedit) storm.dll to allocate read+write+executable memory, right? So when it tries to run its dynamically generated code it won't trigger a NX exception...
avatar
DarthElwood: Still not working for me
You have to restart your computer if you haven't already
avatar
DarthElwood: Still not working for me
avatar
Tajasaurus: You have to restart your computer if you haven't already
same situation :(
even after disabling the DEP the high-res game doesn't work
only the classic one starts to work
high rated
avatar
squid_80: You know you can patch(hexedit) storm.dll to allocate read+write+executable memory, right? So when it tries to run its dynamically generated code it won't trigger a NX exception...
Good hint! After patching the respective storm.dlls by changing 2 bytes from 04 to 40 at offsets 0x1d43b and 0x1dce8
Diablo.exe seems to run ;)

(This changes the flProtect argument to two VirtualAlloc() calls, 04 is PAGE_READWRITE, 40 is PAGE_EXECUTE_READWRITE)

storm.dll:
0x1d43b: 04 -> 40
0x1dce8: 04 -> 40

After these changes, Diablo also runs without disabling DEP.

UPDATE: This is now included in

Internal Hotfix v3 (11 March 2019)
added a potential fix for mouse issues;
added a workaround for DEP issues on some machines;


No need to patch manually :)
Post edited March 11, 2019 by bdschnei
Disabling or enabling doesn't help me at all. I really wanted to spend my weekend with Diablo, but I can't because of this.
Post edited March 08, 2019 by Papier2234
avatar
bdschnei: Good hint! After patching the respective storm.dlls by changing 2 bytes from 04 to 40 at offsets 0x1d43b and 0x1dce8
Diablo.exe seems to run ;)
Happy to help, maybe GoG can use these details to fix their broken game.
avatar
bdschnei: Good hint! After patching the respective storm.dlls by changing 2 bytes from 04 to 40 at offsets 0x1d43b and 0x1dce8
Diablo.exe seems to run ;)
Thank you! I wasn't able to get either version to run under Win7(64bit) until applying this fix.