My thoughts on Slackware, life and everything

Installing Diablo 3 on Slackware Linux

Linux Today News has a headline “How to Install Diablo 3 on Linux” which points to the following article on SoftPedia: .

I smiled for a bit, because I already have Diablo 3 running on my Slackware desktop for a few weeks now. And it did not take “PlayOnLinux” to do this.

  1. Install my wine  1.5.x and wine_gecko 1.5 packages. I have applied patches specifically to make the Diablo 3 installer work. Do not use my wine 1.4 package – that is the “stable” release which can probably play Diablo but can not install it.
  2. Run “winecfg” and configure wine to behave like a Windows 7 OS.
  3. Download the winetricks script, copy it to your /usr/local/bin directory and make it executable.
  4. Run “winetricks vcrun2008” in order to install the MS Visual C++ 2008 runtime  This will prevent application crashes when starting Diablo 3.
  5. Download the Diablo 3 setup from your Battle.Net account (assuming you already have an account and a Diablo 3 license). If you have a Diablo3 DVD then you mount that of course
  6. Run the setup using this example command (you may have downloaded another localization than enGB): “wine Diablo-III-Setup-enGB.exe” (if you have the DVD then you run the setup from the mounted directory).
  7. The setup will download about 8 GB of installation files and will then start the actual installation process.
  8. Once the installation has finished, you’ll see the big button “Play”. Click it to start the game.
  9. The game has been installed as a menu entry as well: below a top-level menu called “Wine”.

If you want to install Diablo into its own wine prefix (meaning it will get its own toplevel directory and thus cannot influence the functionality of other Windows programs you may have installed) then you need to add something like “WINEPREFIX=$HOME/.wine-diablo3/” in front of the above winedcfg and wine commands (you are free to pick any directory you like, mine is just an example); or just run “export WINEPREFIX=$HOME/.wine-diablo3/” once before starting the first wine command. The desktop menu entries which are created by the Diablo setup will automatically be configured to also use a custom wine prefix.

Using the wine-1.5.5 which I patched and packaged I could install Diablo 3 and play for hours without a single glitch. Well done wine developers!

Very good troubleshooting information about running Diablo 3 on Linux using wine can be found in the Diablo 3 appdb page on winehq.

Cheers, Eric


  1. Janis

    i have to note that something is wrong with your wine build: after installing i get error:
    wine: ‘~/.wine’ is a 64-bit installation, it cannot be used with a 32-bit wineserver.
    the same result i get if i use your build script o my system…

  2. alienbob

    Nothing wrong with my wine package. It just does not contain a 64-bit wine (i.e. a version of wine which can run 64-bit Windows programs).
    Did you have someone else’s wine package installed before mine, which did also contain wine64?
    The solution is to re-create a 32-bit wineprefix directory using this command:

    $ WINEARCH=win32 winecfg

    See also


  3. Janis

    clear, i used (your?) wine build script which contains building 64 bit wine;

    WINEARCH=win32 winecfg actually means re-installing everything already there as all the .reg files will be gone after that.

  4. alienbob

    You may be confusing the fact that I built wine to run on a 64-bit Slackware… but the wine binaries are still 32-bit binaries. The version of wine which my SlackBuild creates can only run 32-bit Windows programs.
    You can compile wine differently on a x86_64 platform, and then you will get “wine64” which is able to run 64-bit Windows programs. This version of wine allows 64-bit Windows programs to call 32-bit Windows programs and vice versa.
    See . I have been wanting to try this for my x86_64 package but have not gotten around to actually do it, mostly because of reports of instabilities and the fact that there are not so many purely 64-bit WIndows programs yet.

    And yes, running “WINEARCH=win32 winecfg” will require that you delete your existing .wine directory.
    That is why I suggested the alternative approach in my main article, to define a different WINEPREFIX and give each Windows program you want to run its own “.wine” directory.


  5. Janis

    I can provide wine build script i use if there is interest

  6. Markus Rinne

    Any recommendations which graphics card to get for playing Diablo on Slackware?

  7. Willy Sudiarto Raharjo

    IMHO, i would pick NVidia because the have better support in Linux and their 3D Driver really is a charm 🙂

  8. Noah

    for the patch, if I’m on slackware64, do I need too make the system multilib, so I can install the 32bit wine package? if not, Do I install the 32bit package as is? or do I try and install the 64bit package?

  9. Noah

    and for clarification, I’m on slackware 13.37, not -current , if that influences your answer.

  10. alienbob

    Hi Noah

    If you want to run Diablo (which is 32-bit Windows software) you have to upgrade a slackware64 system to multilib first.
    Then you install my wine package (the one in the “pkg64” directory). Don’t forget to also install my OpenAL package, wine depends on that.

    Note that my Wine for slackware64 is still only supporting 32-bit Windows programs! I.e. I did not compile “wine64” for 64-bit Slackware. The wine64 program still has issues according to the developers, and there is just too few 64-bit Windows programs to care about this anyway.


  11. Noah

    Thanks Alien!
    One quick question, will the openAL package that is on the main slackbuild repository work?
    Or will I need to for sure use the one in your own repository?

  12. Dmitry

    Hello, Eric!

    I do all like u write in your manual, but get error in start menu when start game. Error message – Game have new update, press “OK” to start game automatic update. Then game close and start launcher where I see message what I have latest version game client. Start game see error… start next loop.
    Before I read u article, I try wine 15.9, but have same error.
    U can help me?


    p.s.Sorry for my bad english.

  13. Peter

    OOPs… so I need multilib system?

  14. Kainã

    sorry if I’m bringing to surface some too old topic, but, I’m tryng to do your step-by-step and the installer crashes when it is about to begin the download. I would like to give more information but i don’t know how. I’m on slackware 64, multlib, using your latests wine and wine-genko packages… so… what’s going wrong? Is the new agent? Thank’s

  15. alienbob

    Diablo’s installer changed, and Linux clients on Wine got banned at one time, so I decided not to have a further look at Diablo.

    I am afraid I will not be able to help you.


  16. Xerxes Lins

    Many thanks for providing such information. I’m installing the game right now. But not only that. All other information contained on this site help me a lot to use Slackware at home. Things like multilib, pipelight among others. Without your help I would not have been able to do cool things with Slackware. Thanks a lot.

  17. slackwar

    Did not get the package to run got stuck at the qt error
    This application failed to start because it could not find or load the Qt platforum plugin “windows”.

    irc lead to this bug tracker:

    git clone git:// wine-git20160228
    git clone wine-staging
    cd wine-git20160228
    ../wine-staging/patches/ DESTDIR=. –all
    cd ..
    tar cfpj wine-git20160228.tar.bz2 wine-git20160228

    Then edit the VERSION in the slackbuild to git20160228 and run it.
    VERSION=git20160228 ./wine.SlackBuild

    (thanks to dave)

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑