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

×
So I tried running the Classic edition of the game since it's the one that supports Battle.net but it freezes on the first title screen (where the Blizzard logo pops up, it doesn't play all the way through) so i tried to skip it next time around only to have it freeze on the title screen with the music still playing. Also trying to choose options triggers the sound of doing something but it's no use since I can't see anything that I'm doing. Alt-enter wont change to window mode and alt-tab brings me to the menus screen which is also frozen thereafter.

I tried many compatibility options, soo I thought maybe it was a problem with the graphics setting (openGL comp or something like that..) so I downloaded DDwrapper but now the game asks me for a CD-rom to insert which I tried to fix by copying DIABTDAT.MPQ to the DX folder to no avail..

Does anyone have an idea what the solution to this is? Modern version works fine but it's without Battle.net support which kinda sucks.

I'm running on a laptop with Win7 64bit with integrated Intel graphics..
This question / problem has been solved by Realpsojedimage
I solved this issue on my laptop by using another wrapper, one not included in the default GOG installation.

http://www.strangebytes.com/index.php/projects/1-diablo-1-windows-7-vista-patch

Note that in fullscreen mode you get no texts on battle.net, and in windowed mode the battle.net interface is displayed off-screen, so it's not ideal.

I'm also using a modified nocd patch to bypass the insert CD error.
играйте на battle.net не в классическую версию :)
https://www.gog.com/forum/diablo/run_diablo_1_gog_no_classic_in_window_and_play_on_battlenet
Видео: https://youtu.be/ivHzD9SdCrg

Или можете попробовать запустить классическую версию в оконном режиме
Видео: https://youtu.be/QQ71nq10vO8
avatar
Realpsojed: I solved this issue on my laptop by using another wrapper, one not included in the default GOG installation.

http://www.strangebytes.com/index.php/projects/1-diablo-1-windows-7-vista-patch

Note that in fullscreen mode you get no texts on battle.net, and in windowed mode the battle.net interface is displayed off-screen, so it's not ideal.

I'm also using a modified nocd patch to bypass the insert CD error.
Hi, it seems it's not so much the problem around the wrapper as it is around getting the game to run with no CD. I've tried now plenty of no-cd loaders (just not the ones that change registry entries since I kinda don't trust those) and patches but none seem to do the job. it still keeps asking me for a CD and for reasons I can't explain mounting a virtual drive is impossible on my system atm so that's out the window. It only seems to be asking me for a CD after I install a wrapper that should fix the freeze.
avatar
sifaaa: играйте на battle.net не в классическую версию :)
https://www.gog.com/forum/diablo/run_diablo_1_gog_no_classic_in_window_and_play_on_battlenet
Видео: https://youtu.be/ivHzD9SdCrg

Или можете попробовать запустить классическую версию в оконном режиме
Видео: https://youtu.be/QQ71nq10vO8
Hi, so I followed your steps but I encountered two problems... first I don't have bncache.dat in my root folder and second is that when I went to add he lines to the registry it was in binary format soo it wasn't as simple as adding a line I think.. I tried maybe going to the D1 registry folder and adding it there but it was already identical to what you suggested soo...

Thanks for the suggestion fellas, I'm at a loss here though. SP is fine and dandy but I was really hyped to play it online for once. I think they made this re-release really sloppy for such a classic game but I don't know if I'm the exception or what... I've got 30 days to refund it which I'm considering since I primarily wanted to play it with my bro since he's in another country and also with other people, but maybe there is some solution to this.

Does it work fine for anyone else out of the box?
Post edited March 24, 2019 by colazex
avatar
sifaaa: играйте на battle.net не в классическую версию :)
https://www.gog.com/forum/diablo/run_diablo_1_gog_no_classic_in_window_and_play_on_battlenet
Видео: https://youtu.be/ivHzD9SdCrg

Или можете попробовать запустить классическую версию в оконном режиме
Видео: https://youtu.be/QQ71nq10vO8
avatar
colazex: Hi, so I followed your steps but I encountered two problems... first I don't have bncache.dat in my root folder and second is that when I went to add he lines to the registry it was in binary format soo it wasn't as simple as adding a line I think.. I tried maybe going to the D1 registry folder and adding it there but it was already identical to what you suggested soo...

Thanks for the suggestion fellas, I'm at a loss here though. SP is fine and dandy but I was really hyped to play it online for once. I think they made this re-release really sloppy for such a classic game but I don't know if I'm the exception or what... I've got 30 days to refund it which I'm considering since I primarily wanted to play it with my bro since he's in another country and also with other people, but maybe there is some solution to this.

Does it work fine for anyone else out of the box?
Покажите что у вас в реестре
HKEY_CURRENT_USER\Software\Battle.net\Configuration\Battle.net gateways

Если не было файла bncache.dat , наверно он не создавался , судя по имен это какой-то кэш
avatar
colazex: Hi, it seems it's not so much the problem around the wrapper as it is around getting the game to run with no CD. I've tried now plenty of no-cd loaders (just not the ones that change registry entries since I kinda don't trust those) and patches but none seem to do the job. it still keeps asking me for a CD and for reasons I can't explain mounting a virtual drive is impossible on my system atm so that's out the window. It only seems to be asking me for a CD after I install a wrapper that should fix the freeze.
Well, for me, there is no freeze if I use the wrapper that I linked instead of the one packed with GOG release.

I don't know what "loaders" are you using, but what I'm using is simply a modified storm.dll for patch 1.09. There's no need to change anything in the registry at all.
avatar
colazex: Hi, it seems it's not so much the problem around the wrapper as it is around getting the game to run with no CD. I've tried now plenty of no-cd loaders (just not the ones that change registry entries since I kinda don't trust those) and patches but none seem to do the job. it still keeps asking me for a CD and for reasons I can't explain mounting a virtual drive is impossible on my system atm so that's out the window. It only seems to be asking me for a CD after I install a wrapper that should fix the freeze.
avatar
Realpsojed: Well, for me, there is no freeze if I use the wrapper that I linked instead of the one packed with GOG release.

I don't know what "loaders" are you using, but what I'm using is simply a modified storm.dll for patch 1.09. There's no need to change anything in the registry at all.
чего вы добились модифицированным storm.dll?

каждый для себя сам решает, что ему использовать...
модифицированные файлы, какие-то измененные файлы, что-бы не просил диск
или использовать то, что купил :) (все файлы оригинальные) и средствами OS добиться результата
avatar
colazex: Hi, it seems it's not so much the problem around the wrapper as it is around getting the game to run with no CD. I've tried now plenty of no-cd loaders (just not the ones that change registry entries since I kinda don't trust those) and patches but none seem to do the job. it still keeps asking me for a CD and for reasons I can't explain mounting a virtual drive is impossible on my system atm so that's out the window. It only seems to be asking me for a CD after I install a wrapper that should fix the freeze.
avatar
Realpsojed: Well, for me, there is no freeze if I use the wrapper that I linked instead of the one packed with GOG release.

I don't know what "loaders" are you using, but what I'm using is simply a modified storm.dll for patch 1.09. There's no need to change anything in the registry at all.
I searched around a bit and found what you mentioned so now the game works like a charm with the wrapper.

I'll mark it as answered since my original question did get answered, but I'm unable to connect to any gateway on battlenet for some reason. Are the servers down if you know?
avatar
colazex: Hi, so I followed your steps but I encountered two problems... first I don't have bncache.dat in my root folder and second is that when I went to add he lines to the registry it was in binary format soo it wasn't as simple as adding a line I think.. I tried maybe going to the D1 registry folder and adding it there but it was already identical to what you suggested soo...

Thanks for the suggestion fellas, I'm at a loss here though. SP is fine and dandy but I was really hyped to play it online for once. I think they made this re-release really sloppy for such a classic game but I don't know if I'm the exception or what... I've got 30 days to refund it which I'm considering since I primarily wanted to play it with my bro since he's in another country and also with other people, but maybe there is some solution to this.

Does it work fine for anyone else out of the box?
avatar
sifaaa: Покажите что у вас в реестре
HKEY_CURRENT_USER\Software\Battle.net\Configuration\Battle.net gateways

Если не было файла bncache.dat , наверно он не создавался , судя по имен это какой-то кэш
Hi, it seems using a modified storm.dll got rid of the CD restriction and to my surprise the registry entries you mentioned are now the same you had in the video (not binary anymore) so I can edit them same as you, which I did by adding

connect-forever.classic.blizzard.com
8
Global

and copying the three files in the DX folder. I tried to connect to battlenet in Classic and Redux Diable but it says it's unable to connect on all gateways including global. Maybe servers are down? Regardless thank you for your help, Other poster helped with Classic but now I have to look into why battlenet wont start haha.
Post edited March 25, 2019 by colazex
Also I have one more question if someone can provide on a side note. I noticed I don't have any "Europe" gateways, do I have to add them manually then? Every single one I try says "Connecting to fastest server" and then a message pops up saying I'm unable to connect to Battlenet. I tried everything you said (#sifaaa) with the new version in windowed mode and with the old wrapper and storm.dll but no success.

The gateways I have are

FSGS
BRODWARS
BATTLE NET
IP LAN PARTY.01
IP PRIVADO
GLOBAL D1

but none work thus far.

EDIT: Nevermind, I'm checking the FAQ and it got my answers covered I think... Thanks for all the help guys!

EDIT: I'm kind of confused, the FAQ answers

"Make sure to run the newly released "GOG Diablo" version. The old classic version is not supported by Battle.net anymore."

Yet the launcher says that Classic is the one that only supports battlenet. If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?
Post edited March 25, 2019 by colazex
avatar
colazex: Also I have one more question if someone can provide on a side note. I noticed I don't have any "Europe" gateways, do I have to add them manually then? Every single one I try says "Connecting to fastest server" and then a message pops up saying I'm unable to connect to Battlenet. I tried everything you said (#sifaaa) with the new version in windowed mode and with the old wrapper and storm.dll but no success.

The gateways I have are

FSGS
BRODWARS
BATTLE NET
IP LAN PARTY.01
IP PRIVADO
GLOBAL D1

but none work thus far.

EDIT: Nevermind, I'm checking the FAQ and it got my answers covered I think... Thanks for all the help guys!

EDIT: I'm kind of confused, the FAQ answers

"Make sure to run the newly released "GOG Diablo" version. The old classic version is not supported by Battle.net anymore."

Yet the launcher says that Classic is the one that only supports battlenet. If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?
только что проверил, успешно подключаюсь.
в чем у вас проблема?
"If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?" - перефразируйте пожалуйста
avatar
colazex: EDIT: I'm kind of confused, the FAQ answers

"Make sure to run the newly released "GOG Diablo" version. The old classic version is not supported by Battle.net anymore."

Yet the launcher says that Classic is the one that only supports battlenet. If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?
So, there's classic = original Diablo from Diablo CDs, then, there's GOG version, which has "classic" and DX.

Original Diablo from CD can go up to patch 1.09b and cannot connect to the Global gateway.
GOG version "classic" also shows up as patch 1.09b, however it's actually some kind of 1.09b v2 or other, and it CAN connect to Global gateway.
GOG version DX is also patch 1.09b, but is missing the battle.net option, and to make it work with battle net, it needs copying of files (either you copy files from the GOG "classic" version to GOG DX folder to add battle.net to GOG DX - OR - you copy files from GOG DX folder to GOG "classic" to have GOG DX wrapper functionality on the GOG "classic" version.)
avatar
colazex: Also I have one more question if someone can provide on a side note. I noticed I don't have any "Europe" gateways, do I have to add them manually then? Every single one I try says "Connecting to fastest server" and then a message pops up saying I'm unable to connect to Battlenet. I tried everything you said (#sifaaa) with the new version in windowed mode and with the old wrapper and storm.dll but no success.

The gateways I have are

FSGS
BRODWARS
BATTLE NET
IP LAN PARTY.01
IP PRIVADO
GLOBAL D1

but none work thus far.

EDIT: Nevermind, I'm checking the FAQ and it got my answers covered I think... Thanks for all the help guys!

EDIT: I'm kind of confused, the FAQ answers

"Make sure to run the newly released "GOG Diablo" version. The old classic version is not supported by Battle.net anymore."

Yet the launcher says that Classic is the one that only supports battlenet. If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?
avatar
sifaaa: только что проверил, успешно подключаюсь.
в чем у вас проблема?
"If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?" - перефразируйте пожалуйста
Ok, so when I start Classic Diablo (or copy files to DX folder and start new version with BattleNet) and try to connect to any gateway it says "Connecting to fastest server" and then after short time it says "Unable to connect to Battle Net". I tried all gateways and even the "connect-forever.classic.blizzard.com/8/Global" which was "Global" under gateways but it gave me the same message. I'm not sure what's wrong if servers are not down, I'll try maybe reinstalling with administrative privileges on? I heard installing in Program Files is not best choice, maybe it's worth a try since servers are working you say..
avatar
colazex: EDIT: I'm kind of confused, the FAQ answers

"Make sure to run the newly released "GOG Diablo" version. The old classic version is not supported by Battle.net anymore."

Yet the launcher says that Classic is the one that only supports battlenet. If we didn't copy and edit the reg files like #sifaaa suggested we wouldn't even be able to have the option in the new version, so what is the deal then?
avatar
Realpsojed: So, there's classic = original Diablo from Diablo CDs, then, there's GOG version, which has "classic" and DX.

Original Diablo from CD can go up to patch 1.09b and cannot connect to the Global gateway.
GOG version "classic" also shows up as patch 1.09b, however it's actually some kind of 1.09b v2 or other, and it CAN connect to Global gateway.
GOG version DX is also patch 1.09b, but is missing the battle.net option, and to make it work with battle net, it needs copying of files (either you copy files from the GOG "classic" version to GOG DX folder to add battle.net to GOG DX - OR - you copy files from GOG DX folder to GOG "classic" to have GOG DX wrapper functionality on the GOG "classic" version.)
Ah I see. Ok thanks for clearing that up! It makes my situation all the more confusing though. There must've something went wrong with installation or something.. If global works normally for others, maybe my OS blocked something during installing and it wont let me connect to battle net at all? Hmm..
Post edited March 25, 2019 by colazex
Guys thanks for all the help, I have to go to sleep now for tomorrow so if thread dies and I don't solve this problem I'll try making a last attempt at making new thread and seeing if anyone has solutions I haven't maybe tried yet. For now I'm doing reinstall of GoG Galaxy on new partition with Diablo and we'll see from there...


Cheers and good night!