Retail expansion and all updates.
Everything works fine. Without any problem.
Completed game on normal difficulty in single player without any crash neither issue.
Also played multiplayer on local network.
What does not
What was not tested
Multiplayer on Battle.net
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Ubuntu 17.04 "Zesty" amd64 (+ variants like Kubuntu)||Aug 09 2017||2.0.2||Yes||Yes||Platinum||Dmitri Smirnov|
|Show||Rosa Desktop Fresh R6 (2014.1)||Jan 26 2017||2.0||Yes||Yes||Platinum||Giovanni Mariani|
|Show||Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu)||Feb 03 2014||1.7.11||Yes||Yes||Gold||Ian|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Jan 26 2014||1.7.11||N/A||Yes||Gold||Thor|
|Show||openSUSE 13.1||Jan 20 2014||1.7.11||N/A||Yes||Gold||an anonymous user|
|Bug #||Description||Status||Resolution||Other apps affected|
|14456||Diablo II hangs when it loses focus||REOPENED||View|
|20362||Diablo II: X11 mouse pointer shows over fullscreen window||NEW||View|
|28520||Surface flips ignore vsync flags in ddraw (Claw, Diablo II, Imperium Galactica II, Incoming, Panzer General II, Unreal)||NEW||View|
Copy Protection Final Word
Patch 1.12 from Blizzard disables the CD check.
If you ever get "Please insert disc", this is NOT a problem with detecting the CD. The protection system is probably still built into the game even though the CD check itself is disabled. Make sure you use version 1.12 or later. If you get this problem after having this version installed, you are likely suffering from a buggy video driver as this is the only known (and proven possible) cause at this point.
DO NOT USE NOCD PATCHES - They are pointless, and won't fix the real problem.
for wine versions 1.12 and earlier:
you need a native mshtml.dll and wininet.dll from ie6sp1 in ~/.wine/drive_c/system32
dont forget to set them as native in winecfg
If you own a legitimate copy of Diablo II, you can register it on battle.net with the serial key, and get a link to an installer (about 1.4GB).
This installer has less issues than the CD version, and is the recommended way to install Diablo II. It works flawlessly (Platinum) from begining to end.
Window managers often have the alt key bound to certain features, especially the alt-click. This is not a wine bug. If you have problems with the alt key in any way do not report it. Fix your window manager. I'm not going to list steps for every one because there are too many possibilites. Figure out yourself or ask in a help forum (here is okay... but be warned all I use is TWM). If you are desperate, turn off window manager managed windows in winecfg.
Go into KDE Control Center, expand Desktop, click window behavior, then click window actions tab. You can turn off the alt-combos. If you want to make window specific settings, click on window specific settings under window behavior on the side.
The option to change the key binding is in System Menu -> Preferences Menu -> Windows.
If your game is suffering from a slight delay in sound, then try following these steps:
Running Diablo 2 under Wine
by Jesse Allen the3dfxdude at gmail com
minor updates by Jasmine Iwanek
Last updated 2008-07-11 - wine-1.0.0/1.1.1
Before you get started
This HOWTO only lists information specific to this app. Please keep comments and test reports brief. Please don't post copies of wine logs here! If you have trouble, see other ways of getting help.
Wine+Diablo 2 Status
Generally perfect for Linux users since wine 0.9.12. FreeBSD kernel 6.2 might work, but copy protection will likely be broken.
It's recommended to not use these versions of software because they break the game's copy protection:
Additionally, FreeBSD kernels less than 6.2 might not work with current versions of wine at all.
Installing the Game
Launch winecfg to perform the following tasks:
It helps to add a device node symlink,
so do the following. If your cd-rom drive letter in winecfg is d: and
the corresponding device node to your mount point is /dev/hdc then run
$ ln -s /dev/hdc ~/.wine/dosdevices/d\:\:
Note, you *must* have two colons! You can tell what your device node is in /etc/fstab or viewing your boot-log.
For running the multi-disk install, it helps to run the install using the drive letter and to not switch your shell to the
cdrom's path. For example:
~/.wine/drive_c$ wine "D:\setup.exe" (where D: is the assigned letter of your CD drive).
If you run while having a current working directory of /mnt/cdrom, for example, then you will lock the drive and you won't be able to eject the disk.
If during the game's install the progress bar stops, the game is probably prompting you for the next disc, but the dialog is under the installer's window. For full install, the order is Install Disc, Play Disc, then Cinematics Disc. Just swap discs and hit enter when the progress stops.
Running and Playing Diablo 2
Do not use the '-opengl' switch to run the game. Blizzard never completed OpenGL support so they removed it, but left the switch in. All you see when you run it is a badly initialized DDraw mode.
If you use the window option "-w", the game will drop to ddraw mode no matter what.
Do not use virtual desktop with the game! It's not designed to be windowed like that! It still thinks it's full-screen!
If you have missing in-game speech, animation, videos, or crashes between acts, these problems are typically from using a modified executable. Install your game properly.
Make sure you have the correct ports open. Open outbound and inbound, TCP and UDP, port 6112 and 4000. More on Network Ports
If you are going to play a direct TCP/IP game and the game tells you that it could not detect a valid address, make sure about things:
When running the game in Windowed mode (-w switch), if the DIablo II window loses focus, the game freezes. To unfreeze the game press Alt+Enter. So far this has been tested in:
I order to correct this issue Wine must run Diablo II from inside Diablo's installation directory. Here is an example: