If anyone has any feedback, I'd love to hear it, I'm trying to transition from our appdb page to here where more people will be able to directly add knowledge. If it works out (it will) I plan on simply referring the appDB to here, and all will be well. Enjoy!

--Toxicity999 22:33, 28 February 2007 (EST)

This should probably be a sub-page of Linux. Meaning it should located at Linux/Wine. If you don't know how to move it, I'll be happy to help. :].--Sky 22:07, 28 February 2007 (EST)
PS, use ~~~~ to sign your talk edits. :)
You're completely right there, I had meant to do that, actually. It's getting quite late here for me to be doing something requiring thinking, heh. On it now. Toxicity999 22:27, 28 February 2007 (EST)
Nice work Toxicity... if I'm correct, you *might* be the person who had started a Wiki for WoW Winers elsewhere. If so, it was me who dropped by suggesting you move the information here, 'coz you had some good info just that we know having stuff spread out amongst lots of different sites hasn't been too useful in the past. Congratulations, and welcome nonetheless. I'm a little brainfried this afternoon, but the content looks good. We'll coperate and work on the layout and stuff later. My *only* thought is that we shouldn't necessarily have this as a sub-page of Linux, however as I don't have a Solaris, BSD etc. to test on, I'm not quite sure what we should do. Normal 23:00, 28 February 2007 (EST)
Yep, that was me, Thanks for the idea there, I had been thinking about it, but had no idea how well the community here would take to something like that around here, or how many winers used wowwiki. and to your second part, this information is pretty generic. For now though, until we get some OS specific information we could for example make a /BSD/Wine page redirecting here, and so on. There is however some Linux specific things here, such as the software audio mixing (I think?). I has it was the page Wine before, but was pointed here, which given my current content made sense, we'll redirect and split it up as need be.
--Toxicity999 15:06, 1 March 2007 (EST)
Is anyone following this yet? Could really use some refining.
--Toxicity999 09:21, 3 March 2007 (EST)
Hi, I just registered. I have been trying to keep the Ubuntu community WoW/Wine howto up to date for the past few monts. I feel that I can contribute to this guide too, by making it a little easier to read, as I think that an average new person to Wine and Linux might find the content and layout of this document to be a bit intimidating at the moment. It's got pretty much all the info in there, that most people need to get WoW running in Wine, I just think that it could use a little cleanup, as you say yourself. I intend to get to work on doing this as soon as I can. --sammi

You guys are doing a great job, at AppDB it was kind of techy and we had a lot of non geeky people confused and asking tons of questions. I'm confident that by the next major patch we'll have this refined well enough for there to be far fewer questions. After that major patch comes out, you should check out the comments on the (soon to be) 2.1 page for WoW at appDB, where users will post questions, and get answers, since I obviously can't cover all of that, you guys adding some of that wherever need would be great. I had planned to actually skim through ALL the old versions comments and add what applied but wow... way too much work, in all honestly =P, also, feel free to merge this with the Ubuntu one, or keep them identical, whatever, there's probably some nice information there that's slightly Ubuntu specific (My distro too!) which might fit better under somehting like Linux/Wine/Ubuntu or (more sense than Ubuntu and wine as there wouldn't be much general WoW info for ubuntu, just for wine under ubuntu, get what I mean?) then link to that here. It does get kind of messy having a 3rd level here, but whatever works. I might need to host that icon I have up elsewhere, for some reason they don't allow SVGs here (Lame!), and this is on my friends gprime server, he hopefully has a ton of bandwidth as he has such a popular site and such, but still I feel a little bad, at least I didn't directly embed the image heh. --Toxicity999 17:04, 6 March 2007 (EST)

I've just asked the admins, via irc:// about the SVG issue. Hopefully we may get a solution where we can host an image here Normal 16:13, 7 March 2007 (EST)

Doing great work here, sammi. Normal 16:27, 7 March 2007 (EST)

Well, we're really taking off, I've noticed tons of people on AppDB reference the work here =] Glad I could get things rolling, we had a lto of the information back on AppDB just poorly organized, but then you should of seen what was there before me kind of just add-to-the-end information since WoW was released =/ Toxicity999 22:04, 8 March 2007 (EST)

Following this guide got me up and running but I had to go a step farther and disable fast writes on my radeon 9800 to get it running as well as it did in windows. I wanted to bring it up here before adding to the article because it's not wine specific. I have the procedure outlined here: Vehement 14:48, 15 June 2007 (UTC)

  • Question: Is it necessary to modify the registry value concerning the amount of video ram on your video card in Wine? I know Cedega requires it, but this guide mentions nothing about it. Utahcarol 15:57, 15 August 2007 (UTC)

FPS improvements Edit

Although I agree with your removal of the nVidia section you did, I'm of the opinion that the UseFastTLS should stay, as it's not mentioned anywhere else in the article. I suspect that we should rename the FPS improvement section, and under that have an nVidia solution, as well as an ATI solution. This would then cover nVidia registry hack, and ATI xorg.conf setting. Normal 16:27, 7 March 2007 (EST)

The "UseFastTLS" fix is still there. I didn't remove it, I just moved to troubleshooting. I think it belongs there as not all users need this fix. --sammi 17:14, 7 March 2007 (EST)
But is this an ATI specific fix? Not all users need the nVidia fix, for they aren't using nVidia cards.Normal 17:18, 7 March 2007 (EST)
Oh, and my apologies. It appears Firefox won't search those text boxes, hence I thought it had been removed, not moved.Normal 17:19, 7 March 2007 (EST)
The Registry setting is actually for ATi graphical issues, but gives a general speed boost to both ATi and nVidia users, hence its neutrality. --Toxicity999 21:31, 8 March 2007 (EST)

Using wine 0.9.33 and nvidia drivers 9755, I have actually found this registry hack to decrease my performance (this is after a lot of testing). In areas where my fps is terrible anyway, the decrease is not noticeable but, in places where I'm normally pegged at 30fps with the hack, I'm more like 40-45 without it. It should be explained how to test to see if the registry hack is really an improvement. -- Vorasis 19:56, 27 March 2007 (EDT)

Sounds promising, unfortunately removing the registry hack resulted in near lockup for me, such was the decrease in performance. wine 0.932 with nVidia 9755 drivers.

Desktop Icon Edit

The SVG icon information contains platform specific, or at least distro specific, information. I think this needs revising. Normal 16:24, 7 March 2007 (EST)

Yes it does, We need at minimum a KDE how to, to compensate for my fairly one sided writing of the original document using gnome. It might be safe to assume people using the other DEs of Linux would know how to do this as I only really know of KDE and Gnome being used in the mainstream, so presumably the user got the DE, possibly compiled it htemselves, if they can do that they can set an icon, plus there are so many DEs it's hard to cover. --Toxicity999 21:34, 8 March 2007 (EST)
I'll agree it's hard to cover them all and a fairly insane idea to try to write them all ourselves. Just start off a new section, 'Desktop Integration' or similar. Fill in the KDE. Maybe someone will do a Gnome, and if I ever get around to it I'll write an XFCE.Normal 00:59, 10 April 2007 (EDT)

Page Rename/Move/Split Edit

We need to wort out a method to remove the Wine page from under the Linux header. I can foresee several ways to do this, however I suspect what'd be best is to have a top level /Wine page, and then have /Wine/Linux, /Wine/Solaris, /Wine/BSD for platform specific info, then /Wine/Ubuntu, /Wine/Debian, /Wine/Fedora, /Wine/Gentoo for the specific Linux distros. Thoughts? Normal 16:33, 7 March 2007 (EST)

It's laid out like this because Linux had all this information before. Are there guides for all those distros? --Amro 16:46, 7 March 2007 (EST)
Not as of yet. Some of the current content is platform neutral, others is OS specific, others is OS distro specific. I'd like to future-proof the wine page as soon as practically possible. Normal 16:53, 7 March 2007 (EST)
As far as I know there are only distro specific guides for Ubuntu and Gentoo, and I think we should leave them alone on their own wikis. We should link to them in stead of doubling the amount of wikis to maintain for each distro. Personally I think we should try to make this howto as distro agnostic as possibly. Keep to the command line and not make references to anything specific to one distro. This should be a broad howto that any person running any distro should be able to use. --sammi 17:10, 7 March 2007 (EST)
Keeping it distro agnostic is fine, to a large degree. I can also appreciate that when there's a well maintained, offsite resource for a specific distro, unless the author/s of that document wish to move the information here, we should just link to it. My main problem at the moment, is that the Wine info is OS specific. Using the 'current format', we'd have to create Solarisx86/Wine and BSD/Wine pages, then duplicate a wad of info from Linux/Wine over there. Normal 17:21, 7 March 2007 (EST)
As I explained earlier along, we can easily split as more OS Specific information surfaces, very easily. But for now WoW wiki's 'nix and the like's info si tucked away in the Linux corner, until we need to expand, leave it at that. Toxicity999 21:43, 8 March 2007 (EST)

Wine WoW hacks/patches Edit

There's a number of various Wine hacks/patches floating around on the interwebs for various 'fixes' that aren't in the main tree. Some I've seen have improved the audio (removing the glitchiness at least under ALSA), removing the hardware cursor in D3D mode, enabling AntiAliasing to some degree. I'd like to think that, if Wine themselves can't host these hacks/patches, we may be able to do so here. Thoughts?Normal 17:25, 7 March 2007 (EST)

That was part of my vision, actually, at AppDB it was hard to keep track of all of that, if you have any patches that are relevant to .32 (at time of writing) please do post them. I would say make a super sub section of "Compiling Wine" Under "installing Wine" for now. Later, as it expands we can allude to somewhere else perhaps... Toxicity999 21:47, 8 March 2007 (EST)

SVG Icon Edit

I've submitted a server request for SVG uploads. Normal 17:34, 7 March 2007 (EST)

Thanks! That's very helpful. I'm sure my friend can handle the BW that pumps through, but still better here than there. Toxicity999 21:36, 8 March 2007 (EST)
I don't know if you noticed that in the "Gnome menu icon" section, that I added, there is a link to this file on I haven't asked them how they feel about hosting this file, but for now using them works. sammi 18:34, 11 March 2007 (EDT)

Wine Versions Edit

I'd like to see some information on what various problems you would expect with different versions of wine, as well as what the 'reccommended' version of wine to use for WoW would be.MajinBlayze 20:00, 8 March 2007 (EST)

Except for super rare cases the latest is normally best, I havent seen any *major* WoW Regression in a ages; If the problem ever arrises we're sure to get on it. And normally theres no reason for someone to be using an old snapshot, with software constantly changing it's crazy to stay in the old, unless there's regression. Toxicity999 21:41, 8 March 2007 (EST)
I beleive that the problems I was having is related to conflicts in my xorg setup. I will post details (this weekend maybe) when I get more time to play with it. --MajinBlayze 17:54, 22 March 2007 (EDT)

Gecko/ActiveX in the troubleshooting section Edit

Why, under the ActiveX sub section, does it say to select no on prompt of installing the Gecko ActiveX controls? As Far as I know this works fine... Changing it to read yes for now, if I somehow missed something please comment and change it back. Toxicity999 21:51, 8 March 2007 (EST)

I copied that from the Ubuntu guide. I know Gecko works fine, but that little stub is old and it didn't say anything about Gecko, it only made references to ActiveX that I didn't know what to make of. I just added it, letting somone else worry about it validity. That special someone was you :)
Thanks for making that correction- sammi 18:34, 11 March 2007 (EDT)
it was probably from.. .27 I think it was when the Sourceforge download of the engine was broken.
--Toxicity999 23:41, 11 March 2007 (EDT)


It is actually possible to enable anti-aliasing (at least on nvidia). You can force anti-aliasing with nvidia-settings and, as long as Full Screen Glow effect is not enabled in game, you will indeed get anti-aliasing using OpenGL. -- Vorasis 19:56, 27 March 2007 (EDT)

that's pretty cool, I would assume no real fps decrease as it's handled native side either, hadn't thought to try it. Feel free to add this to the wiki under the tips and such section, wherever you see fit. --Toxicity999 20:07, 28 March 2007 (EDT)

Exit hang bug in WoW version 2.1 Edit

We might want to make note that some users are experiencing application hangs when trying to exit WoW as of 2.1. This is a pretty serious issue, and something that will affect lots of users (assuming it's not just me, but then it certainly started happening with the 2.1 patch). This hang prevents saving application state, so no user settings are preserved from run to run. -Deepone 12:59, 23 May 2007 (UTC)

I'm now tracking this issue on my Fedora/WoW page at -Deepone 13:07, 23 May 2007 (UTC)
--> FIX <-- Details posted here [1] --Spinalcracker 13:23, 26 May 2007 (UTC)
Woops... seems I've just written a lot of bogus info in the wiki. I've been reading about a few people form whom the problem just fixed itself and I wrote that in the howto. I didn't check this page first. I'll try to update the howto with this fix. -sammi 10:38, 31 May 2007 (UTC)

The bug would seem to be back in wine 0.9.44. At least I have it on three PCs and two guys in my Ubuntu-Community have it. Only workaround so far is to avoid wine 0.9.44, which is not satisfying. -thom_raindog 10:38, 29 August 2007

Wine Bugzilla fix. Tested against 2.1 and 2.2, works for me. Normal 00:26, 5 September 2007 (UTC)

Comitted and tested against 2.1.3. Waiting for 2.2.2 PTR for further testing.
Commit went live with wine 0.9.46.Normal 10:48, 29 September 2007 (UTC)

Community Edit

Where is a good place (forum, mailing list) to get help with issues not listed on this wiki? --Utahcarol 13:07, 2 August 2007 (UTC)

The most obvious would be your distributions official forum. is great for Ubuntu users etc. sammi 17:38, 7 August 2007 (UTC)
Sadly, I've had no success with Utahcarol 15:10, 15 August 2007 (UTC)

WoW on POSIX illegal? Edit

I've heard of players being banned for running the World of Warcraft client on GNU/Linux using Wine. I've also heard that a reason for this is that Blizzard's anti-cheat "spyware" doesn't work on Linux since the game software doesn't have the appropriate permission to scan the system for illegal third party programs as the game client is just an unprivileged piece of software in a POSIX environment. And since this might be effectively used to suppress Blizzard's anti-cheat measures, Blizzard has prohibited the use of their service on a *NIX system. Anyone knows if this is really true? Privatekey 21:24, 8 August 2007 (UTC)

Links like this seem to say otherwise. Gmillerd 04:28, 15 August 2007 (UTC)
From my understanding, it's unsupported - not illegal. There was a period of time recently when Warden, the Blizz anti-cheat-tool, identified Wow on Wine as a nasty product, and managed to get some accounts banned. That Blizz changed Warden's behaviour, and apparently refunded time to players who were effected would seem to incidate that it's tolerated - if not supported. Vastly different from illegal. Normal 06:37, 16 August 2007 (UTC)

Problems with 2.2 PTR Audio Edit

2.2 PTR audio will not work with any Wine version earlier than Wine 0.9.45.

Losing sound upon alt-tab Edit

The way I fixed this problem (setting the game to a fullscreened windowed mode) wasn't documented in this article so I went ahead and added it since I assume this fix would work for everybody (I know it also worked for at least one other person). Feel free to edit it or take it out if you have anything else to add regarding that issue, or if maybe it doesn't work for everyone. --Pikestaff 13:57, 22 August 2007 (UTC)

I've heard it works for some, not for others. Scratching my memory, I seem to recall it's a generic Wine issue - although to be honest I seem to recall hearing it's happened occasionally under native, too - so I'd say it's cool to leave it in for now until it's confirmed somewhere that it's been solved. My 2c -> the more info, the better. Normal 08:02, 28 August 2007 (UTC)

Cleanup Edit

This article is getting seriously too long. I propose that we look at splitting it up. In line with my original position, the article should be moved out from underneath Linux, into it's own top level. Additionally, each section be moved underneath the Wine entry as sub-pages, with the Wine page itself having a brief para describing the sub-page's content. Additionally, platform/graphic/soundsystem specific information would be under the main Wine page.Normal 00:50, 22 September 2007 (UTC)

I agree. Breaking it up would make it less intimidating and more accessible for newcomers. I don't think I have enough experience with MediaWiki, to undertake this operation myself though, and we should wait for a few more opinions on the matter, as this is a very major step to take sammi 23:03, 10 October 2007 (UTC)
I am getting tired of the unbearable length of this article. I feel like just creating /Linux/Wine/Troubleshooting for the troubleshooting section and /Linux/Wine/Misc for all the extra info on the bottom of the guide sammi 12:30, 28 October 2007 (UTC)
Finally got sick of it, and seeing that no one seems to be opposing my suggestions, I've taken the liberty to just implement them. You may of course move everything from underneath /Linux/ if you see fit Normal sammi 23:14, 19 November 2007 (UTC)

Reusing Orginal Install Edit

Here is what could be stupid question: What is wrong with reusing my main install in Windows on a dual boot Linux\Windows machine? I have tested and proven that my wine can run the launcher.exe if I give it the full path to mounted windows partition.

Doing that seems obvious enough to me that I'm wonder why the Ubuntu Howto and this Howto doesn't even mention it. Perhaps there is something so fundamentally wrong with that idea that we dare not mention it less we all appear to be imbeciles. Well, I volunteer to be that imbecile. Cosmic 17:44, 17 October 2007 (UTC)

Note: While I was able to get WoW working this way, the icons didn't look right and it crashed on my after about an hour. BUT....All my addons were there and worked great, which seems to be the advantage of reusing your main install of WoW. You could play with the exact same set of addons and configs no matter which OS you're logged into.

Doesn't install method number three cover this? sammi 13:48, 16 October 2007 (UTC)
Technically no. If you read method 3 closely you'll see it talks about copying the install file from Windows to Linux. Why? Why duplicate my 5 GB install that has all the addons that I use all the time. I am asking what is wrong with pointing my wine to the files located on the windows partition? Cosmic 17:43, 17 October 2007 (UTC)
Aha. I don't see any problem with doing this as long as you have read and write access to the Windows partition. I've tried to add some info on this to method 3, as I think that both of these methods are in very close family sammi 00:15, 22 October 2007 (UTC)

Graphical Problems Edit

I found some weird graphical problem playing WoW in Wine under Linux on a Nvidia Geforce 8500GT. Distant ground textures do not have a fog effect on them, so they do not look distant. Objects like trees or buildings are fogged out correctly when they are distant. The problem could be "solved" by disabling the "Enable all Shaders" option in the Graphics-Menu. But the 2.3.0-version of the game does not have this option any more. You can reach the same effect by adding SET pixelShaders "0" to your But this, well, disables all pixel shader effects (ground and water reflections, full screen glow, death glow). I would like to have these options on, because the game looks very more nice with them. Maybe someone has a better solution. Agebel 20:16, 16 November 2007 (UTC)

Yah, I've been wondering about that too. Trying to get some info together so I can post on Tech Support and see what they think. I'm inclined to think there's a bug in their renderer as people were complaining about various graphical issues when this build went up on the PTR last week. Water being non-transparent and so forth. If your setup can handle it, try running in directx mode for a few minutes to see how it compares.
You may want to chime in on the AppDB and see what's up on the Wine end. [2] --User:Kaydeethree/Sig 20:32, 16 November 2007 (UTC)
I tried the direct3d mode and it does not have that problem. I enabled all graphical options and played a little around. Everything seems to work fine and I cound not find any disadvantages in comparison with opengl. - ok, I found one, the game does not run any more in direct3d-mode - I will write a report to the AppDB about that. Agebel 09:46, 18 November 2007 (UTC)
I posted it in the AppDB and some people said there, that it is a problem within the nvidia-driver. But does everyone with a nvidia-card have that problem?Agebel 20:09, 21 November 2007 (UTC)
These graphical glitches are indeed a problem with recent nVidia drivers, and are even cross platform. When WoW is set to OpenGL under both Windows or Wine, the same problem occurs with the fog not being correctly rendered for distant objects when pixel shaders are enabled. I cannot recall which version of the nVidia drivers I was using in Windows, but I can say that the bug persisted in many driver versions and misled me to believe the issue was with Blizzard. More recently however, I updated from the restricted nVidia driver in the Ubuntu Gutsy repositories (100.14.19 I believe) to the current Linux 32 bit beta drivers (169.04) and the issue went away. I am able to use GLSL (shaders turned on), I have excellent framerates on my 8800GTX, on par with those under Windows. I routinely push 30-60 FPS in major cities and 100+ in other areas at 1900x1200. The issue seems to be a bug in nVidia's OpenGL driver code in a wide range of driver versions. --Divideoverflow 21:20, 10 December 2007 (UTC)
The newest regular driver (169.07) does also solve the problem. All shader effects enabled and distant terrain looks fine :) Agebel 20:49, 26 December 2007 (UTC)
I added this to the troubleshooting article. Maybe someone could check the orthography on that part ;)Agebel 08:12, 17 January 2008 (UTC)

Installing WotLK on FC10 without networked Windows Edit

I thought I would drop by and share my success with installing WotLK on Fedora Core 10. The WotLK DVD is not as easily mounted and read in Linux as the vanilla and BC CDs, which are ISO 9660. Googling around seems to suggest the easiest way to install Wrath is to copy the DVD's contents onto a Windows share or by downloading the entire expansion via the WoW website. However, an FC10 system can install (indirectly) from the DVD if you are a sudoer, as follows. This is based on RedWagon's and init6's comments here.

# insert WotLK DVD
# open terminal
sudo umount /media/Lich\ King/ # fedora will mount the DVD here. Unmount it so we can mount it properly:
sudo mkdir /media/LichKing/ # could've probably used "Lich\ King/" there, but I dont like spaces :P
sudo mount /dev/dvd /media/LichKing/ -o unhide
mkdir /tmp/wow-wotlk # or wherever you'd like to put it... perhaps somewhere more permanent?
sudo cp -r /media/LichKing/ /tmp/wow-wotlk/
sudo chown -R soapster:soapster /tmp/wow-wotlk # replace soapster with your username
wine /tmp/wow-wotlk/LichKing/Installer.exe

If this is helpful, feel free to add it to the article. — soapster 01:49, 24 January 2009 (UTC)

The easy solution is in the Wine/Troubleshooting page. I added it, oh... thirty minutes after I got home on release night (so, 1 AM eastern). Should've gotten more attention than it did, but oh well. --k_d3 02:28, 24 January 2009 (UTC)
Heh, that's exactly it, albeit much more concise with the assumption you have a clue about linux :D Thanks for the reply, I hadn't seen Wine/Troubleshooting before! — soapster 12:16, 24 January 2009 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.