[Bug 46803] Diablo 1 GOG.com crash

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46803

Ivan <ivan88 at centrum.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ivan88 at centrum.cz

--- Comment #6 from Ivan <ivan88 at centrum.cz> ---
Classic version somewhat runs. I usually create prefix with winetricks -q
directplay vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 msxml3
ie8, but I doubt any of these is required. Anyway, set Windows version to 10,
install GOG setup.exe. Then, to get around no CD error, use mkisofs to create
ISO with DIABDAT.MPQ on it (original retail CD may work too), mount it. Then
set renderer to GDI and enable virtual desktop (e.g. winetricks ddr=gdi
vd=640x480). Launch Diablo.exe from install root (not from dx subdirectory,
that appears to be the enhanced version) and while it sometimes crashes,
usually it does not and it is possible to play.
Of course, menu options are invisible and moreover layout depends on whether
there are characters created or not, but you can learn it on Windows.

Battle.net (this mode seems unavailable in enhanced version) requires open port
6112, i.e. most people will have to set port forwarding on their
ADSL/cable/whatever modem/router. Battle.net UI is partially visible.
IPX/SPX does not seem to work. Now obviously IPX/SPX is dead, but back in the
day it was used to start effectively single player session with multiplayer
character that could be used later on Battle.net.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.