No, it isn’t World of Warcraft 64 (it’s only at version 5 at the time of writing). WoW64 allows you to run 32- and 64-bit applications on a 64-bit WINE prefix (well, not exactly, WoW64 is for windows, and WINE adopted it). While it may not be as fun as World of Warcraft 64 would be, it’s definitely much more useful (and heck, it might even help you run it, so don’t get all disappointed! XD).
Alright, so joking aside, you’ll, of course, need a 64-bit OS to run it (if you have a 32-bit OS on a 64-bit processor, it won’t work). So, first of all, run this in a terminal:
wine wmic os get osarchitecture
If you see “64-bit” (which is what will happen if you use Arch Linux… if you installed the “wine” package), then you can skip this tutorial! If not, then if you have ubuntu, run this in a terminal:
sudo add-apt-repository ppa:ubuntu-wine/ppa sudo apt-get update sudo apt-get install wine1.7
If WINE has been updated (say to version 1.8 or 1.9 or something… you can check this at http://www.winehq.org/ … look at “Latest Releases” “Development” … at the time of writing, it’s 1.7.10), install wine1.8 or 1.9 or whatever the new version is, instead of wine1.7.
Once that’s done, you will need to create a new WINE prefix. To do this, simply run this in a terminal:
WINEPREFIX=new/wine/prefix/path winecfg
For example, if I wanted to have my 64-bit WINE prefix at ~/.wine-64 (~ is the home directory), I would run this:
WINEPREFIX=~/.wine-64 winecfg
You have to realize that every time you want to run something using that WINE prefix, you’ll always need to prefix the command with WINEPREFIX=~/.wine-64 (or wherever you put your WINE prefix). For that reason, I simply renamed my old 32-bit prefix to ~/.wine-old, then created my new 64-bit one at ~/.wine (which is the default path for the prefix). That way, I don’t have to prefix each command with that (unless I want to access my old 32-bit one).
