Difference between revisions of "Diablo II"

From ArchWiki
Jump to: navigation, search
m (Additional information: Fix typo.)
m (Installing: fix links)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
[[Category:Gaming]]
 +
[[Category:Wine]]
 
[[bg:Diablo II]]
 
[[bg:Diablo II]]
This page explains how to install Diablo II and play it under Archlinux. This works as of latest patch 1.13c.
+
[[ja:Diablo II]]
== Installing ==
+
This page explains how to install Diablo II and play it under Arch Linux. This works as of 2016-08-14.
  
=== Step 1 ===
+
If you already have a Diablo II installation (for example, installed under Windows on another partition), simply update that version to the latest patch (trying to log into Battle.net will start the update automatically), launch it once (to migrate your characters and the CD-Key, should it still be stored in the registry - newer versions store it next to the game's binary). You may now start playing on Arch with Wine - no additional dependencies are required for the game itself.
Install the wine package.
+
# pacman -S wine
+
  
=== Step 2 ===
+
== Installing ==
Download Diablo II and Diablo II Lord of Destruction installation files from battle.net. I downloaded them on Windows and them moved via USB stick. You can also run the downloaders directly from Arch. They will produce 2 folders: D2-1.12A-enUS and D2LOD-12.12A-enUS (locale may be different for you).
+
  
After that, go to first folder and run
+
Those packages are needed in order to run the Blizzard Downloader:
$ wine Installer.exe
+
  
Enter your product key which can be found In your battle.net account and install. After it is finished, go to the second folder and run the same command. Once both are installed, download [http://ftp.blizzard.com/pub/diablo2exp/patches/PC/LODPatch_113d.exe patch 1.13d] from the Internet as updater will not work. After that, run:
+
* {{pkg|lib32-libjpeg-turbo}} ({{pkg|libjpeg-turbo}} on i686)
$ wine LODPatch_113d.exe
+
* {{pkg|lib32-libldap}} ({{pkg|libldap}} on i686)
  
=== Step 3 ===
+
If any of those is not installed, downloaders will fail to start. You may download the standalone installers on Windows to avoid installing these.
  
Now you need to configure the graphics. Go to ~/.wine/drive_c/Program Files/Diablo II (or where ever you installed) and run:
+
Set up a working [[Wine]] environment. Download Diablo II and Diablo II Lord of Destruction installation files [https://eu.battle.net/account/management/download/ from Battle.net] - launch downloaders, pick a directory to download the installers into. Launch the Diablo II installer, enter your key. Then install Lord of Destruction (the directory will be set automatically, you'll need to enter just the key). Launch the game once and try logging into Battle.net to download the latest patch.
$ wine D2VidTst.exe
+
Click on Run Test. Once it's finished, pick whichever you want. Generally I prefer 2D even on Windows as very few modern cards support Glider. You can try 3D though and see if it lags or not.
+
  
=== Step 4 ===
+
If the installers were downloaded from Battle.net, keys are 26-character, generated for you when you've registered games on Battle.net, available on product pages for [https://eu.battle.net/account/management/classic-games.html?license=20 Diablo 2] and [https://eu.battle.net/account/management/classic-games.html?license=23 Lord of Destruction] - original keys from the CDs will work only with the installers from the CDs themselves. However, the original versions from the CDs have somewhat serious compatibility issues even with newer Windows versions (by newer, think XP), and as such are not recommended anymore.
$ winecfg
+
Then, add Game.exe and make sure it uses ALSA under the sound tab and that it is emulated as Windows XP. I didn't have to change anything as those were default for me.
+
  
== Additional information ==
+
In the past, a game CD was required to launch the game (with a rather nasty workaround for non-Windows OSes if you didn't want to use a NoCD crack, which was not exactly Battle.net-safe). They're no longer needed - in recent patches, the protection has been removed completely.
  
While the information above will work for a fresh install from the actual CD's themselves, if you are a dual boot user you most likely have Diablo II
+
== Playing ==
installed on your windows partition. If this is the case, you're more than capable of running the installation in ArchLinux, without much hassle.
+
  
You can start by mounting your windows installation to a fixed-name directory, I like to create one in /media and make sure it can be accessed by anyone.
+
If you use a desktop, you can create a shortcut. Otherwise just run:
  
$ mkdir /media/windows
 
$ chmod 777 /media/windows
 
$ mount /media/sdb2 /media/windows
 
 
Keep in mind that your drive letter will be different than documented, to locate your windows partition do the following:
 
$ fdisk -l
 
 
The output will tell you what drive is HPFS/NTFS, the smaller size will be your windows recovery partition (unless you do not have one), and the larger one will be your entire windows partition.
 
 
I also recommend using the package ntfs-3g, which will allow you to write content to your windows partition, in addition to being able to read it. This will make life much easier at one point or another.
 
 
$ pacman -S ntfs-3g
 
 
Once you have your windows partition mounted you may wish to copy your Diablo II directory to a location on the Linux partition, and choose not to mount windows at all, this is perfectly fine and does not cause any problems, make sure you know whether or not your installation is in a x64 bit folder or a x86 bit folder.
 
 
$ cp -dpR /media/windows/Program Files/Diablo II /home/username/Desktop
 
$ cp -dpR /media/windows/Program files (x86)/Diablo II /home/username/Desktop
 
 
Once you have successfully decided how to gain access to your content, you will need to have a Diablo II play disc for either classic, if you play classic, or expansion, if you play expansion. If you do not have the actual disc, and use a ISO I recommend mounting it using fuseiso.
 
 
$ mkdir /media/diablo
 
$ chmod 777 /media/diablo
 
$ pacman -S fuseiso
 
 
Make sure you do the above commands as root, and when you mount the actual ISO do it as a regular user, this will ensure the game is mounted with the proper permissions.
 
 
$ fuseiso /location/of/diablo.iso /media/diablo
 
 
{{Note|you will need to run winecfg as a regular user, and set up the mounted ISO location under "Drives". I choose drive "S:" and configured it as a CD-ROM mount to {{ic|/media/diablo}}.}}
 
 
You may also have issues running the D2VidTst, noticing that you have no available video displays, if this is the case you must take note to run Diablo II's "Game.exe" with the window extension, other wise it will crash. WineHQ noted this as a coding error on behalf of Blizzard.
 
 
$ wine /media/windows/Program Files/Diablo II/Game.exe -w
 
$ wine /media/windows/Program Files x(86)/Diablo II/Game.exe -w
 
 
On a additional note, use of a "NO-CD" crack will result in a ban on Battle.net, and if you do not wish to be restricted from realm play, should invest in finding a ISO you can mount locally.
 
 
And on a final note, this is a Windows game and you will notice that you will generate many notifications about missing fonts, this can be corrected by creating a symlink between the wine fonts directory, and the windows directory.
 
 
$ ln -s /media/windows/Windows/Fonts /usr/share/wine/fonts
 
 
If you do not want to mount the Windows partition as mentioned before, copy the windows Fonts directory into the Diablo II folder you have on the Linux partition, and create the symlink between wine and that directory.
 
 
== Playing ==
 
If you use a desktop, you can create a shortcut. Otherwise just run:
 
 
  $ wine ~/.wine/drive_c/Program\ Files/Diablo\ II/Game.exe
 
  $ wine ~/.wine/drive_c/Program\ Files/Diablo\ II/Game.exe
Warning: Don't append the argument -opengl , because it was left unfinished by the developers and may cause extra problems for you!
 
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
 
=== Error "ACCESS_VIOLATION" on start===
 
=== Error "ACCESS_VIOLATION" on start===
Try setting dsoundhw=Emulation. This can be done by starting winetricks "Select the default wineprefix"and then choose "Change settings" and check the box in front of "dsoundhw=Emulation".
 
Another thing to try is to add "-w" at the end of the command line. It will launch the game in windowed mode but it should work where fullscreen doesn't.
 
  
=== Only starts in windowed mode ===
+
Try setting {{ic|1=dsoundhw=Emulation}}. This can be done by starting winetricks ''Select the default wineprefix'' and then choose ''Change settings'' and check the box in front of ''dsoundhw=Emulation''.
Try running D2VidTst.exe in the game folder and then select 3dfxGlide.
+
Another thing to try is to add {{ic|-w}} at the end of the command line. It will launch the game in windowed mode but it should work where fullscreen does not.
If the game still doesn't start in fullscreen place the glide3x.dll into the game folder from this website http://www.svenswrapper.de/english/downloads.html. It is extra written for running Diablo2 with glide.
+
 
+
[[Category:Gaming]]
+
[[Category:Wine]]
+

Latest revision as of 06:47, 22 August 2016

This page explains how to install Diablo II and play it under Arch Linux. This works as of 2016-08-14.

If you already have a Diablo II installation (for example, installed under Windows on another partition), simply update that version to the latest patch (trying to log into Battle.net will start the update automatically), launch it once (to migrate your characters and the CD-Key, should it still be stored in the registry - newer versions store it next to the game's binary). You may now start playing on Arch with Wine - no additional dependencies are required for the game itself.

Installing

Those packages are needed in order to run the Blizzard Downloader:

If any of those is not installed, downloaders will fail to start. You may download the standalone installers on Windows to avoid installing these.

Set up a working Wine environment. Download Diablo II and Diablo II Lord of Destruction installation files from Battle.net - launch downloaders, pick a directory to download the installers into. Launch the Diablo II installer, enter your key. Then install Lord of Destruction (the directory will be set automatically, you'll need to enter just the key). Launch the game once and try logging into Battle.net to download the latest patch.

If the installers were downloaded from Battle.net, keys are 26-character, generated for you when you've registered games on Battle.net, available on product pages for Diablo 2 and Lord of Destruction - original keys from the CDs will work only with the installers from the CDs themselves. However, the original versions from the CDs have somewhat serious compatibility issues even with newer Windows versions (by newer, think XP), and as such are not recommended anymore.

In the past, a game CD was required to launch the game (with a rather nasty workaround for non-Windows OSes if you didn't want to use a NoCD crack, which was not exactly Battle.net-safe). They're no longer needed - in recent patches, the protection has been removed completely.

Playing

If you use a desktop, you can create a shortcut. Otherwise just run:

$ wine ~/.wine/drive_c/Program\ Files/Diablo\ II/Game.exe

Troubleshooting

Error "ACCESS_VIOLATION" on start

Try setting dsoundhw=Emulation. This can be done by starting winetricks Select the default wineprefix and then choose Change settings and check the box in front of dsoundhw=Emulation. Another thing to try is to add -w at the end of the command line. It will launch the game in windowed mode but it should work where fullscreen does not.