http://bugs.winehq.org/show_bug.cgi?id=20643
Erik erikmm@xs4all.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |erikmm@xs4all.nl
--- Comment #6 from Erik erikmm@xs4all.nl 2009-11-12 05:55:56 --- I see this behaviour as well but after the patch.It seems that the patch consists of a new version of Launcher.exe that not only tries but succeeds in changing directory permissions of the WoW directory from drwxr-xr-x into d---r-x---, which makes the directory completely inaccessible. This makes it impossible for the launcher tot start WoW,exe. Rumors are that this is intended by Blizzard to avoid multiboxing (which simply can be avoided by starting multiple instances of WoW.exe). A quick and (very) dirty workaround is to restore the permissions by hand while Launcher.exe is still active. Strangely when running the program from an NTFS partition directory permissions are left alone or restored properly... This behaviour is seen in all Wine versions 1.1.13-1.1.32.
Funny thing is: people running WoW on native Windows platform are reporting exactly the same problem. I'm not convinced this is really a Wine bug...it seems to me that Blizzard's developers could use some education..:-)
Best regards, Erik