Retail expansion and all updates.
Everything gameplay-wise in Singleplayer, using the installer downloaded from Battle.net.
What does not
What was not tested
- Full-screen mode
To install this game on Mountain Lion, I used Wineskin and followed these steps: 1. Open Wineskin Winery, install the Wine 1.4 engine (WS8Wine1.4) 2. Create a New Blank Wrapper using this engine, call it Diablo II. 3. When it's created the wrapper, click "Show In Finder" and then double click the Diablo II icon. 4. It will ask you for an installation executable. Navigate to the one downloaded from battlenet and run it. 5. After it has run, it will try and find the game executable. In my experience it finds the wrong one. The right one is "/Program Files/Diablo II/Diablo II.exe" assuming you left the settings as default in the installation. 6. You'll probably want to install the expansion as well. There should be an option to install more software. If not, and you've quit the application, you'll need to run its Wineskin application again. Right-click on the Diablo 2 icon in Finder and click show package contents (if you can't find the Diablo 2 icon, it's in /Users//Applications/Wineskin/). In here, double-click the Wineskin icon and then click Install Software. 7. Before you run the game, in Wineskin, click Advanced. Under the Configuration tab, make sure the Windows EXE points to /Program Files/Diablo II/Diablo II.exe. In "EXE Flags" put "-w". 8. Click "Set Screen Options" down the bottom. Select "Override" in the top right to override Wine's control of the screen settings, and make sure "Rootless (windowed)" is selected. 9. You should be able to run the game now. This was done with Wineskin version 2.5.6.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|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|
|Show||Linux Mint 19 Cinnamon||Feb 14 2019||4.1-staging||Yes||Yes||Yes||Gold||Crypto Logiq|
|Show||Fedora 28 x86_64||Sep 30 2018||3.16-staging||Yes||Yes||Yes||Gold||Kiiro Yakumo|
|Show||Ubuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)||Oct 27 2018||3.0.3||Yes||Yes||No||Platinum||Jaroslav Smutek|
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: