BenV's notes

World of Warcraft’s new 64 client under Wine64

by on Feb.03, 2012, under Software

With the release of patch 4.3.2 the still biggest MMORPG they finally decided to go the 64 bit route.
Through the forums a 64 bit client can be downloaded and placed next to the normal one, with a bunch of warnings and stuff that doesn’t yet work obviously. Yay.

Before you can run the 64 bit client you obviously first need to let your wow patch it’s way to the 4.3.2 patch.
In wine 1.4-rc1 (32 bit) this looked a bit like this:

World of Warcraft patcher

World of Warcraft patcher

In the meanwhile I compiled the 64 bit version of wine. Much the same as the 32 bit version, except it has no access to 32 bit libraries.
Oh yeah, you have to tell configure to enable 64 bit: ./configure –enable-win64. That was hard.
Compilation takes a while for wine, so while it’s patching and compiling and stuff you can get some coffee 🙂

After compiling and installing wine64 on my 64 bit slackware-current installation (as opposed to my 32 bit chroot where I usually run World of Paycraft) I gave it a try:

benv@janeman:~> cd /storage/wow
benv@janeman:/storage/wow> wget -q http://us.media.battle.net.edgesuite.net/downloads/wow-installers/live/WoWLive-64-Win-15211.zip
benv@janeman:/storage/wow> unzip WoWLive-64-Win-15211.zip
benv@janeman:/storage/wow> wine Wow-64.exe
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 2
fixme:heap:HeapSetInformation 0x454000 0 0x29fce0 4
fixme:process:GetLogicalProcessorInformation (0x29f260,0x29fa70): stub
fixme:process:GetLogicalProcessorInformation (0x8db570,0x8dbd80): stub
fixme:process:GetLogicalProcessorInformation (0x8db570,0x8dbd80): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:process:GetLogicalProcessorInformation (0xa4db60,0xa4e370): stub
fixme:process:GetLogicalProcessorInformation (0x29e940,0x29f150): stub
fixme:process:GetLogicalProcessorInformation (0x29e940,0x29f150): stub
archive Data/Cache/SoundCache-1.MPQ opened
archive Data/Cache/SoundCache-2.MPQ opened
archive Data/Cache/SoundCache-3.MPQ opened
# yadieyada much more garbage

It took a considerable time (way longer than my 32 bit wine) but at some point the login screen finally appeared!
(I already went through the user agreements by adding SET readEULA “1” to their WTF/Config.wtf) 😉

To show you it runs under wine I ticked ‘windowed’ mode in the options and stretched the window a bit … which made the login screen look very weird.
Apparently it detects my second monitor and tries to ‘fix’ the aspect ratio by adding black borders. Really useful in a windowed mode. (if you enable virtual desktop in wine and set it to a proper resolution it doesn’t do this. .. but why do it anyway, it runs fine in fullscreen mode with instant switches between desktops anyway).

World of Warcraft 64 bit under wine64

World of Warcraft 64 bit under wine64

After entering my login details and hitting enter on the character selection screen (which didn’t show my weapon enchants oddly enough), the loading screen appeared. Hopeful the bar went from left to …. almost the right end … almost there …. … SAAAAaaayy.
Giving it another 5 minutes didn’t help, and in fact, writing this post certainly took longer than that but it still seems stuck there.
Feh. Seems like Blizzard still needs to fix that.

World of Warcraft 64 bit loading screen

World of Warcraft 64 bit loading screen


Turning off addons or trying other characters didn’t make a difference, stuck there on that position.
Wine didn’t show any real error either, it’s last lines:

archive data\enGB\agreements.mpq opened
fixme:heap:HeapSetInformation 0x15f42000 0 0x29dd70 4
fixme:ntdll:NtFlushInstructionCache 0xffffffffffffffff 0x8d1000 9291
fixme:seh:RtlAddFunctionTable 0x8d6000 45 8d0000: stub
^C
^Z
[1]+ Stopped wine Wow-64.exe
benv@janeman:/storage/wow:148>kill -9 %1

Oh well, maybe next patch it’ll work 🙂




:, , , , ,

Leave a Reply

You must be logged in to post a comment.