Retail expansion and all updates.
What does not
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Manjaro Linux 20.1||Sep 15 2020||5.16||Yes||Yes||No||Platinum||Ragnar|
|Show||Ubuntu 20.04 "Focal" (+ variants like Kubuntu)||Oct 08 2020||5.0.2||Yes||Yes||No||Platinum||johsjo|
|Show||LUbuntu 20.04||Sep 10 2020||5.0.2||Yes||Yes||Yes||Bronze||no|
|Show||MX Linux - 17.1||Jun 16 2019||4.10-staging||Yes||Yes||No||Platinum||Oliwer Ejderbrand|
|Show||Fedora 30 x86_64||Jun 07 2019||4.9-staging||Yes||Yes||No||Silver||Brice|
|Bug #||Description||Status||Resolution||Other apps affected|
|1631||Sound underruns occur in directsound||CLOSED||FIXED||View|
|2367||DII: Lord of Destruction Install Fails w/ CVS and 20040615||CLOSED||FIXED||View|
|2726||Missing "Programs" entry in registry - Diablo II Expansion install fails...(WINE 20050211)||CLOSED||FIXED||View|
|3997||New modal dialogs are behind main window||CLOSED||FIXED||View|
|4445||CPU usage causes Diablo II game to lose sync with self||CLOSED||FIXED||View|
|5015||Diablo 2 doesn(t launch after update to v1.11||CLOSED||FIXED||View|
|5683||"False color" effects in text backgrounds and objects (Diablo II LoD)||CLOSED||FIXED||View|
|5732||preloader and mmaping seem seriously broken on FreeBSD||CLOSED||ABANDONED||View|
|6185||Diablo II Movies Crash||CLOSED||FIXED||View|
|8530||Diablo ][ TCP/IP, Overlay map, and Speech/Talk/Text.||CLOSED||INVALID||View|
|9699||Diablo 2 LoD crash||CLOSED||FIXED||View|
|12962||Diablo 2: left-control ignored after mouse click||CLOSED||FIXED||View|
|14305||DII: Lord of Destruction Install Fails w/ CVS and 20040615||CLOSED||ABANDONED||View|
|14348||Diablo 2: Unhandled Exception code c0000005||CLOSED||ABANDONED||View|
|14404||Diablo LOD/Starcraft, no sound with ALSA||CLOSED||FIXED||View|
|14456||Diablo II hangs when it loses focus||REOPENED||View|
|14679||Diablo II Installer from Blizzard account download doesnt work.||CLOSED||FIXED||View|
|14992||Diablo 2 crash introduced in 1.1.3||CLOSED||FIXED||View|
|16958||Exiting Diablo II running in windowed mode, resets xrandr display setup||CLOSED||ABANDONED||View|
|17406||Lord of the Rings Online fails to connect to the Internet if WINE 1.1.14 is built with -O3||CLOSED||FIXED||View|
|17421||Diablo2 fails to run when Wine is compiled with -march=amdfam10||CLOSED||DUPLICATE||View|
|17503||Diablo 2 refuses to detect D3D device||CLOSED||FIXED||View|
|20362||Diablo II: X11 mouse pointer shows over fullscreen window||NEW||View|
|20506||Diablo 2 Slow down||CLOSED||WORKSFORME||View|
|21516||Diablo 2 hangs if becomes inactive||CLOSED||DUPLICATE||View|
|27028||Touchpad mouse cursor flickers when moved, jumps back towards original position when released||CLOSED||FIXED||View|
|27156||Bioshock demo: mouse jumps around menu||CLOSED||FIXED||View|
|27908||Diablo 2 - sound doesn't work||CLOSED||FIXED||View|
|28520||Surface flips ignore vsync flags in ddraw (Claw, Diablo II, Imperium Galactica II, Incoming, Panzer General II, Unreal)||CLOSED||FIXED||View|
|28770||Diablo 2 - sound works in menu, stops after starting game||CLOSED||FIXED||View|
|29464||Diablo II Unhandled exception: Access_violation (c0000005)||CLOSED||INVALID||View|
|29786||[Diablo II] Software Rasterizer broken||CLOSED||INVALID||View|
|29787||[Diablo II] Flickering colors with software renderer||CLOSED||DUPLICATE||View|
|30867||Page fault / null pointer exception in ConvertPixelFormatGLXtoWGL when virtual desktop is enabled||CLOSED||ABANDONED||View|
|44838||Diablo 2 graphics became glitchy starting with Wine Version 3.2||UNCONFIRMED||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.
As of 1.12, it is possible to play without using a CD.
The following is an excerpt from the patch changelog:
For users that originally performed a "Full Installation" and wish to run without the CD, all ".mpq" files should be copied from the Diablo 2 CDs to the Diablo 2 directory. Most users will only need to copy D2Music.mpq from the Diablo 2 Play CD and/or D2xMusic.mpq from the Lord of Destruction CD.
Anyone who did not perform a "Full Installation" will need to re-install from CD again to ultimateÂly play without the CD. In this case, a "Full Installation" is required, followed by file copy step noted above.
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: