World Of Warcraft Howto/Support UPDATED 11/10/05! (old)

[d13f00l]

Confirmed. Reiser4, black screen
loopback on my reiser4, ext3, works.

Wine doesn't output any errors though on reiser

[d13f00l]

Weird. Nevermind. It only partially copied, I ran out of space on my block device. It worked then, I made the device larger and it gives me a black screen again, ext3 or not. Must have been dumb luck.[/code]

[ikataii]

Possibly confirmed? With WoW on ext3 and FAT32, I still get the error. wine is installed to a reiser partition, though, but running a local copy on ext3 doesn't fix it either.

[mopomi]

Changing the permissions (chmod a-w) on the root of the WoW tree on the reiserfs partition does not fix it, so it's not some weird file overwrite problem. I'll muck around some more. . .

Some other things I've found: I have one addon that I use, FlagRSP. Its saved variables were somehow destroyed on both the Linux and Windows partition. The default settings on my Windows partition were also destroyed. I have a feeling that there was some kind of a hot fix that mucked up things pretty bad. I believe the previous links to discussions about monitors blacking out or turning off are related. I'm guessing that Blizzard implemented some sort of a hot fix that maybe was designed to shut off or change power management or some such, and it caused problems with wine users specifically because there are no working implementations of that junk (as far as I know--I'm somewhat in the dark here as I've been away from coding for far too long)

This can't explain the fact that I can run the game from an NTFS partition and not from a reiserfs partition, however, so maybe something else is still the problem.

[makzu]

I just installed a fresh copy of WoW on my machine, with a nice, clean ~/.wine directory. Then I upgraded it. And then I spent an hour or so playing the game, killing boars. Fun!

The most vexing problem I ran into was the black screen problem. I don't know if this is the same as everyone else's, but my screen would go to solid black (while still playing background music) just after I typed my name and password in. Hitting esc twice would exit the program.

Here's how I fixed that problem: I deleted the WDB and WTF folders in my WoW installation directory, and restarted WoW. I lost my (few, at that time) settings, but it worked reasonably well after that. I have the "mouse bug" where I can only click on NPCs and enemies and whatnot if there's sky behind them, but I'm recompiling Wine right now with a patch mentioned on the wiki to see if that fixes it.

Hope this helps you!

[ikataii]

Confirmation and love! Wiping out my WDB and WTF folders fixed it up in a right jiffy. Now I just have to get back to fixing up my UI addons and all will be well.

[ikataii]

New madness: I went to modify some stuff in my settings via the in-game setup, and it bugged out. I tried clearing out the Account subfolder of WTF and deleting large amounts of the Config.wtf file. Neither had favorable results. Just deleting the WTF folder fixed it again, though.

[d13f00l]

Deleting the WDB and WTF folders has no effect for me

[Fenster]

Is anyone else getting entire machine lockups while playing World of Warcraft?

I'm getting the type 2 xorg lockup while playing the game. It can happen right after I log in, it can happen after six hours of play, but it will happen eventually. The frequency of lockups has risen exponentially in the past month - I got three last night inside of an hour, having to hard reboot my PC each time. Its pretty damm frustrating, and I've had to go back to Windows to play WoW.

This is using Cedega.

I'll post as much system info as I can once I get home.

[mopomi]

Is this black screen bug happening for everybody, just people who have WoW installed on a native (to linux) filesystem, or some even smaller section?

System stats:

Suse 9.3 x86_64
Athlon 64 3700+
2 GB RAM
laptop
CVSwine
(patched to work around mouse click bug; same results with latest packaged release, but of course mouse click bug is there when the system does work.)

Works:
wine /windows/Program\ Files/World\ of\ Warcraft/WoW.exe -opengl -nosound -windowed

(NTFS partition, not writable from Linux; this only works somewhat--the flagRSP addon has weird problems that cropped up at the same time--lose saved variables. I tried removing the addon, but that didn't fix the problem. Also tried removing the WTF and WDB dirs, but didn't fix it either.)

Does not work:
wine /slacker/games/World\ of\ Warcraft/WoW.exe -opengl -nosound -windowed

(Reiserfs3 partition, writable from Linux)

[d13f00l]

Hrm. I'll try running it off my NTFS drive via wine.

CEDEGA also locks my computer up totally within an hour of play, I can't even SSH in, and my temps are low and ram memtests fine so the problem isn't hardware.

[d13f00l]

Yeah. Running it on a NTFS partition works. Maybe I'll copy it to my reiser and see if it still works.
Regardless, it's slow as heck for whatever reason, ~10fps on my gf4mx athlon 2200. It doesn't seem to be locking up my computer like cedega does, but cedega runs much faster.

Under windows, it runs at 35-50 usually, under cedega -opengl, it used to run even better than windows when the game first came out, but the opengl renderer seems to have slowed down massively on my card since back then.

I really hope blizzard ports it over to linux natively. Maybe then they could work a bit more on their OGL renderer. Also, it's odd, but Wine/Cedega also give me lighting options on my card. I can turn on vertex shaders, and when I walk past lights and stuff my skin lights up, windows doesn't do that for some reason. Huh.

[prg]

Is this black screen bug happening for everybody, just people who have WoW installed on a native (to linux) filesystem, or some even smaller section?

System stats:

Suse 9.3 x86_64
Athlon 64 3700+
2 GB RAM
laptop
CVSwine
(patched to work around mouse click bug; same results with latest packaged release, but of course mouse click bug is there when the system does work.)

Gentoo 2005.1
Athlon 64 3500+
2GB RAM
gf 6800 gt with 6629 drivers
wine 20050930 with patches

wine WoW.exe -opengl works fine on a writable ext3 partition
i don't use any addons
fps is ok i think, but i can't compare as i don't have win on this machine
shaders work, but not the hardware cursor

[mopomi]

Stupid me. I forgot my video card:

nVidia GF 440 go, with 64 MB RAM

[mooninite]

The black screen after you try to login is caused by something weird...

Make your WDB directory read-only and try to login. WoW is trying to create a "Survey.mpq" file on my system and when I deleted that file, made WDB read-only, it started WoW just fine.

I'm using XFS for the filesystem here.

[GoldDog]

The black screen after you try to login is caused by something weird...

Make your WDB directory read-only and try to login. WoW is trying to create a "Survey.mpq" file on my system and when I deleted that file, made WDB read-only, it started WoW just fine.

I'm using XFS for the filesystem here.

Confirmed. By making WDB read-only, the black/blank screen goes away. But neither of the patches fixed the mouse-bug. Both of them give me this error:

Code: Select all

err:virtual:map_image Image was mapped at 0x7f240000: standard load address for a Win32 program (0x00400000) not available
err:virtual:map_image Do you have exec-shield or prelink active?
wine: could not load L"D:\\Program Files\\World of Warcraft\\WoW.exe" as Win32 binary

EDIT: Was able to bypass this error by running WINE from /home/[user]/wine/loader with the command:
./wine /path/to/World/of/warcraft/WoW.exe -opengl

But the mouse-bug is still there.

[prg]

Confirmed. By making WDB read-only, the black/blank screen goes away. But neither of the patches fixed the mouse-bug.

there are two?

what wine version are you using?

[GoldDog]

Confirmed. By making WDB read-only, the black/blank screen goes away. But neither of the patches fixed the mouse-bug.

there are two?

Yes.

First there is yours:

hi, it is working for me without the mouse bug
i'm on amd64, wine 20050930

here's what i've done:

wine-mmap-wowhack.patch
Code:

--- libs/wine/mmap.c
+++ libs/wine/mmap.c
@@ -161,6 +161,26 @@

#endif /* (__svr4__ || __NetBSD__) && !MAP_TRYFIXED */

+static void *get_anon_mmap_null_address(size_t size)
+{
+ static int got_override = 0;
+ static void *low_alloc_ptr = NULL;
+ void * current_low_alloc_ptr;
+
+ if (!got_override)
+ {
+ low_alloc_ptr = (void*)0x10000000;
+ got_override = 1;
+ //printf("gaak!\n");
+ }
+
+ current_low_alloc_ptr = low_alloc_ptr;
+
+ if (low_alloc_ptr)
+ low_alloc_ptr += size;
+
+ return current_low_alloc_ptr;
+}

/***********************************************************************
* wine_anon_mmap
@@ -209,6 +229,9 @@
return start;
#endif
}
+ if ((start == NULL) && !(flags & MAP_FIXED))
+ start = get_anon_mmap_null_address(size);
+
return mmap( start, size, prot, flags, fdzero, 0 );
#else
return (void *)-1;

(thanks to shamus13 who posted a link to http://lists.transgaming.org/pipermail/ ... 00259.html)

wine-preloader-wowhack.patch
Code:

--- loader/preloader.c
+++ loader/preloader.c
@@ -110,7 +110,7 @@
{
{ (void *)0x00000000, 0x00110000 }, /* DOS area */
{ (void *)0x80000000, 0x01000000 }, /* shared heap */
- { (void *)0x00110000, 0x1fef0000 }, /* PE exe range (may be set with WINEPRELOADRESERVE), defaults to 512mb */
+ { (void *)0x10000000, 0x00f00000 }, /* PE exe range (may be set with WINEPRELOADRESERVE), defaults to 512mb */
{ 0, 0 } /* end of list */
};

(how) could that be done with WINEPRELOADRESERVE?

and no, i do not understand what these changes actually do.

hth,
prg

And there is also one posted by "Polynomial-C"

Hi,

seems to work flawlessly on my sister's computer...
Anyway I had to hack the patch into the sources myself as the quoted patch was somehow corrupted so the patch-program refused to apply it to the sources...
To spare this to others, here is a link to the patch I created:
http://polynomial-c.homelinux.net/pub/g ... ixes.patch
I hope it helps

Cheers
Poly

what wine version are you using?

WINE20050930

[prg]

Polynomial-C put this patch in a file and put it up for download, it is the same as the patch i posted here, it just seems that the whitespace got messed up when i posted it

20050930 is the version it should be working with, so other system specs?

[mopomi]

The black screen after you try to login is caused by something weird...

Make your WDB directory read-only and try to login. WoW is trying to create a "Survey.mpq" file on my system and when I deleted that file, made WDB read-only, it started WoW just fine.

I'm using XFS for the filesystem here.

Works* by simply making the WDB dir unwritable (don't have to delete the Survey.mpq, which also exists on the NTFS partition). I don't get it. . . This is reiserfs3.

*My addon acts very strange, but I'm not sure this is the same problem. . .

No mouse bug with the patch posted here. Still a bit slow FPS wise, but that might be because I'm trying to run it at 1920x1200. /grin

[GoldDog]

Polynomial-C put this patch in a file and put it up for download, it is the same as the patch i posted here, it just seems that the whitespace got messed up when i posted it

20050930 is the version it should be working with, so other system specs?

(grrr.... I just finished writing this entire post and then FireFox crashed (prob 'cus I'm on a Windows comp atm, lol. So this post is somewhat smaller and more compact).

Anywayyyyyyyys,

As I mentioned in my last post, by making the WDB directory unwritable, solved my "black/bank screen" problem. But nothing has yet fixed the "mouse-bug" problem.

I have tried those 2 patches and applying them to the "~/wine/libs/wine/mmap.c" and the "~/wine/loader/preloader.c" files (using "patch mmap.c /path/to/somefile.patch" and same for preloader.c) before compiling WINE20050930 (which I "tar -zxvf wine-20050930.tar.gz" in my home directory, thus creating a folder called "wine-20050930" which I renamed to "wine" to help keep things nice and tidy). After patching them, I do "./configure", "make depend && make" and then as root "make install". I have seen people mention using "emerge wine" but I do not know what that is (I'm somewhat of a WINE newbie, but I can make my way around), and that may be my problem, for all I know.

And again, as I mentioned in my other post, after compiling WINE with the applied patches, and then trying to run WINE on WoW, it gives me the error:

Code: Select all

err:virtual:map_image Image was mapped at 0x7f240000: standard load address for a Win32 program (0x00400000) not available 
err:virtual:map_image Do you have exec-shield or prelink active? 
wine: could not load L"D:\\Program Files\\World of Warcraft\\WoW.exe" as Win32 binary 

But if I run wine from the ~/wine/loader directory, using the command "./wine /path/to/WoW.exe -opengl" then that error (above) goes away. But I have no idea what that does or why that would make any difference. But even at that, the mouse-bug is still there.


My computer is:

AMD Athlon 2.4Ghz
512MB of memory
NVIDIA GeForce FX 5200 (was last updated, about... hmm... 3 months ago)
Fedora Core 3 (with all the latest updates installed)

Please help

[prg]

I have tried those 2 patches and applying them to the "~/wine/libs/wine/mmap.c" and the "~/wine/loader/preloader.c" files (using "patch mmap.c /path/to/somefile.patch" and same for preloader.c) before compiling WINE20050930 (which I "tar -zxvf wine-20050930.tar.gz" in my home directory, thus creating a folder called "wine-20050930" which I renamed to "wine" to help keep things nice and tidy). After patching them, I do "./configure", "make depend && make" and then as root "make install". I have seen people mention using "emerge wine" but I do not know what that is (I'm somewhat of a WINE newbie, but I can make my way around), and that may be my problem, for all I know.

have you had a look into the patched files to make sure that the changes show up there? what did the patch program say?
emerge has nothing to do with wine, it's the package management program for gentoo, like rpm or apt for other distros, just that it compiles stuff from source so patches can be applied automatically

if you try to run wow with the unpatched wine from any directory, does that not give this error?

[GoldDog]

have you had a look into the patched files to make sure that the changes show up there?

No. I don't know what to look for.

what did the patch program say?

Code: Select all

patching file mmap.c
Hunk #1 succeeded at 161 with fuzz 1.
Hunk #2 succeeded at 229 with fuzz 1.

Code: Select all

patching file preloader.c
Hunk #1 succeeded at 110 with fuzz 2.

if you try to run wow with the unpatched wine from any directory, does that not give this error?

It does not give me that "exec-shield"/"prelink active" error, when WINE has not been patched. It only gives me that error after it has been patched.

[prg]

that "succeeded" looks good, so the patches really get applied

have a look at http://www.fedorafaq.org/fc2/#wine
looks like that exec-shield causes problems with wine on fedora core

[GoldDog]

that "succeeded" looks good, so the patches really get applied

have a look at http://www.fedorafaq.org/fc2/#wine
looks like that exec-shield causes problems with wine on fedora core

Right. I have gone to that exact site before, and I have tried the "setarch i386 wine WoW.exe -opengl" and that gives me the exact same error. But I have not tried the "more complex" version on that site ( http://www.fedorafaq.org/fc2/#wine ), yet. I'll give that a try and post again.