Howto: WOW with Wine (help.ubuntu.com/community/WorldofWarcraft)

[Darth Buh]

I came across a new one this morning. I don't remember installing anything, I've got Wine 1.1.18.

Terminal output is as follows:

***@HubbyPC:~/.wine/drive_c/Program Files/World of Warcraft$ wine Wow.exe -opengl
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:advapi:RegisterEventSourceW ((null),L"Bonjour Service"): stub
fixme:winsock:WS_setsockopt Unknown IPPROTO_IP optname 0x00000013
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WS_setsockopt Unknown level: 0x00000029
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {f689d7c8-6f1f-436b-8a53-e54fe351c322}: stub
fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 159 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x21
Serial number of failed request: 146
Current serial number in output stream: 147
Locking assertion failure. Backtrace:
#0 /usr/lib32/libxcb-xlib.so.0 [0x7e94b7c7]
#1 /usr/lib32/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0x7e94b96e]
#2 /usr/lib32/libX11.so.6 [0x7ea49619]
#3 /usr/lib32/libX11.so.6(XESetCloseDisplay+0x44) [0x7ea2b294]
#4 /usr/lib32/libGL.so.1 [0x7e9b4f69]
#5 [0x7d22f9d8]
***@HubbyPC:~/.wine/drive_c/Program Files/World of Warcraft$ fixme:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request: stub

I can't really find anything solid about why this happened, or how to fix it.. any ideas?

DB

[_the_new_guy_]

Hi, I have the same problem asPaulzy & Kuculcan, what do I do?

[t.rei]

I don't know if it helps any of you guys, but I have a story of success.

Playing wow and using teamspeak on my ubuntu-System (Jaunty) now.

Absolutely fresh install of Ubuntu (had some remains of old experiments I could not find messing up my mouse)

I got wine from winehq repos:
http://winehq.org/download/deb (how to do that, explained step by step with pictures )

All I did to the WoW (copies from an installation vom Vista) was to edit the config.wtf file in: ~/.wine/drive_c/Programme/World of Warcraft/WTF/ (On english systems I believe its "Program Files")

SET gxAPI "OpenGL"

And then I created a launcher for Wow on my desktop (or run it from shell):

wine /home/username/.wine/drive_c/Programme/World\ of\ Warcraft/Wow.exe -opengl

I need to turn off "key repeat" under System -> Settings -> Keyboard Settings to "not twitch".

As for teamspeak: I need to start that using aoss.
aoss teamspeak - I don't think I did much else, but this error-search pre-clean-install messed up my memory of what I might have done to wine. *ponders* No, I do believe that worked "Out of the box".

Good luck to you all.

*edit* Not using aoss for teamspeak anymore! I run the windows teamspeak client using wine now, since sound is much much better that way.

[Yuka]

I'm having a problem when WoW is loading (if it loads at all):

World of WarCraft (build 9551)



Exe:      C:\Program Files\World of Warcraft\WoW.exe

Time:     Apr  6, 2009 12:50:13.050 AM

User:     yuka

Computer: lime



This application has encountered a critical error:



ERROR #131 (0x85100083) File Corrupt

Program:	C:\Program Files\World of Warcraft\WoW.exe

File:	DBFilesClient\Achievement.dbc




WoWBuild: 9551

Settings: 

SET gxApi "opengl"

SET Sound_SoundOutputSystem "1"

SET Sound_SoundBufferSize "150"
-and so on...-

Ubuntu 8.04, kernel 2.6.24-23-generic, Ati Driver 9.1 (fglrx, Radeon 4850), Athlon64X2, nF4SLI.

Hope you guys figure it out for/with me, cause that error ain't a corrupted file at all; I've copied the files through WinXP->Linux via IFS Drives mount, the "cp -frv" way and Nautilus way in GNOME with the same result.

Esop!

[waxor]

I too am having this same issue with the 'corrupt' Achievements.dbc. I noticed that some people talked about it very far back in this thread, but no one mentioned a fix that worked.

I have a fresh install of Ubuntu. I am running Wow.exe from a partition that is shared with windows, so I know the file is not actually corrupt. There is not much useful output in the terminal. I am starting wine with "wine WoW.exe -opengl".

Anyone?

[sirthorn]

I too am having this same issue with the 'corrupt' Achievements.dbc. I noticed that some people talked about it very far back in this thread, but no one mentioned a fix that worked.

Reinstall WoW within Wine. It solved the problem for me, and I now install every patch from within Wine just to make sure this problem doesn't happen to me again.

I still wonder why it installs differently within Windows, because this solution sucks.

Oh, and big tip: save your patch files before you wipe WoW so you don't have to download them again.

[waxor]

Thanks, I will give that a shot.

[t.rei]

Hey all - I just wanted to say that besides the still existant key-repeat problem, I now am running the windows-teamseak client. The sound-performance is alot better than the linux-native one using aoss.

[zami]

Version Mismatch Error Fix

For this error

WoW
This application has encountered a critical error:
ERROR #121  (0x85100079) Version Mismatch
Program: C:\Program Files\World of Warcraft\WoW.exe
DBFilesClient\Startup_Strings.dbc has wrong number of colums (found 19, expected 11)

Press OK to terminate the application.
OK

Look in your World of Warcraft directory, and if you have both
WoW.exe
and
Wow.exe (notice the lower case "w")

backup
WoW.exe (perhaps just renaming it WoWbackup.exe)
and rename
Wow.exe to WoW.exe

At this point I *think* one of the following renames WoW.exe to Wow.exe
A) the Blizzard Full Client Downloader program
B) the file repair tool
C) the Wrath of the Lich King expansion itself

And if you've copied files from another directory (such as a Windows directory after failing miserably to get the Full Client Downloader to run properly in Wine, or copied files from an already updated machine to save time, etc) you will end up with BOTH similarily named executable files. Launcher.exe points to the dud, until you rename your files as outlined above.

-zami

[hikaricore]

That does't make sense Wow.exe shouldn't exist.