View previous topic :: View next topic |
Author |
Message |
teidon Apprentice
Joined: 22 Apr 2005 Posts: 195 Location: Finland
|
Posted: Sun Apr 24, 2005 4:18 pm Post subject: |
|
|
Here's a way how I installed and patched wine. WoW works fine and this is also newbie friendly way of doing it as there's no need to mess with cvs.
1. Get the try6 patch from somewhere.
2. Open 2 terminal programs and "su" to root in both of them.
3. Type this to one of the terminals, but don't execute it yet (note that that directory doesn't exist until you do emerge wine and the source has been unpacked, so copy+pasteing this might be a good idea. Remember to change "/location/to/try6-patch" to the correct one): cd /var/tmp/portage/wine-20050310-r1/work/wine-20050310/ && patch -p0 < /location/to/try6-patch
4. In the other terminal do "ACCEPT_KEYWORDS=~x86 emerge =wine-20050310-r1" and after it says ">>> Source unpacked." execute the line in the other terminal.
5. Now just sit back and wait until wine has been emerged.
Incase emerging went well and there were no errors during patching you now have a wine which can run WoW (atleast it's working for me). |
|
Back to top |
|
|
meinbobo n00b
Joined: 13 Apr 2005 Posts: 17
|
Posted: Sun Apr 24, 2005 5:27 pm Post subject: |
|
|
50 bonus points to teidon - those directions were just what i needed - thanks |
|
Back to top |
|
|
DrewMadMax n00b
Joined: 29 Sep 2002 Posts: 43
|
Posted: Sun Apr 24, 2005 10:43 pm Post subject: opengl32 error |
|
|
I've been having this problem for awhile, and haven't seen anything that really seems to address it (I could have just overlooked it). I copied my WoW install over from my windows drive, and whenever I try to run it, I get the following error:
Code: | ~/.wine/drive_c/Program Files/World of Warcraft $ wine WoW.exe
err:module:import_dll Library OPENGL32.dll (which is needed by L"C:\\Program Files\\World of Warcraft\\WoW.exe") not found
err:module:import_dll Library GLU32.dll (which is needed by L"C:\\Program Files\\World of Warcraft\\WoW.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\World of Warcraft\\WoW.exe" failed, status c0000135 |
I'm running wine-20050419 with the fb6 patch from the first page of this thread. I have tried copying opengl32.dll and glu32.dll from my windows xp install, but WoW crashes with the following output from winedbg:
Code: | ~/.wine/drive_c/Program Files/World of Warcraft $ wine WoW.exe
wine: Unhandled exception (thread 0009), starting debugger...
WineDbg starting on pid 0x8
Couldn't initiate DbgHelp
Unhandled exception: unimplemented function KERNEL32.dll.IsWow64Process called in 32-bit code (0x55727c8c).
In 32 bit mode.
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:005b
EIP:55727c8c ESP:55c1fbd0 EBP:55c1fc28 EFLAGS:00000216( - 00 - IAP1)
EAX:5eda22da EBX:55751b84 ECX:5ed09ec5 EDX:5eda2576
ESI:55c1fbd0 EDI:00000001
Stack dump:
0x55c1fbd0: 80000100 00000001 00000000 5ed09ec5
0x55c1fbe0: 00000002 5eda2576 5eda22da 5edac720
0x55c1fbf0: 00000001 55c1fc10 5571c9eb 558f0000
0x55c1fc00: 00000000 00000020 55751b84 55a8bcf0
0x55c1fc10: 55c1fc24 5571ca65 5edac720 55727c4d
0x55c1fc20: 00000002 55a8bcf0 55c1fd80 5ed09ec5
Backtrace:
=>1 0x55727c8c in NTDLL (+0x17c8c) (0x55c1fc28)
2 0x5ed09ec5 (0x55c1fd80)
3 0x5ed0a366 (0x55c1fd8c)
4 0x55727c12 in NTDLL (+0x17c12) (0x55c1fda4)
5 0x5572ab0a in NTDLL (+0x1ab0a) (0x55c1fe24)
6 0x5572aba1 in NTDLL (+0x1aba1) (0x55c1fe44)
7 0x5572b0cf in NTDLL (+0x1b0cf) (0x55c1ff24)
8 0x55a782be (0x55c1fff4)
9 0x5558e601 (0x00000000)
0x55727c8c: subl $4,%esp
Modules:
Module Address Debug info Name (25 modules)
PE 0x10000000-10000000 Deferred DIVXDECODER
PE 0x55710000-5575b000 --none-- NTDLL
PE 0x55a30000-55a30000 Deferred KERNEL32
PE 0x55c30000-55c30000 Deferred MSVCRT
PE 0x55c90000-55c90000 Deferred COMCTL32
PE 0x55d50000-55d50000 Deferred USER32
PE 0x55e60000-55e60000 Deferred GDI32
PE 0x55ee0000-55ee0000 Deferred ADVAPI32
PE 0x55f20000-55f20000 Deferred SHELL32
PE 0x55fd0000-55fd0000 Deferred SHLWAPI
PE 0x56020000-56020000 Deferred OLE32
PE 0x56090000-56090000 Deferred RPCRT4
PE 0x560c0000-560c0000 Deferred IPHLPAPI
PE 0x560e0000-560e0000 Deferred WSOCK32
PE 0x56100000-56100000 Deferred WS2_32
PE 0x56150000-56150000 Deferred DDRAW
PE 0x56290000-56290000 Deferred IMM32
PE 0x562b0000-562b0000 Deferred WINMM
PE 0x56320000-56320000 Deferred FMOD
PE 0x563c0000-563c0000 Deferred MSACM32
PE 0x563e0000-563e0000 Deferred WININET
PE 0x56410000-56410000 Deferred MPR
PE 0x56520000-56520000 Deferred X11DRV
PE 0x5ed00000-5ed00000 Deferred OPENGL32
PE 0x68b20000-68b20000 Deferred GLU32
Threads:
process tid prio (all id:s are in hex)
00000008 (D) C:\Program Files\World of Warcraft\WoW.exe
00000009 0 <==
WineDbg terminated on pid 0x8 |
I'm getting pretty frustrated which means I could have easily overlooked something simple at this point. I'm running a 64-bit gentoo install. If you need any other info, let me know.
Thanks ahead of time for your help.
- D
Edit: I'm going to try going back to the 20050310 version of wine with the patch and see if that works.. I'll update in a bit.
Edit2: Well, version 0310 has the same problems. Yay. _________________ "True Knowledge Exists in Realizing Your Own Ignorance"
Last edited by DrewMadMax on Sun Apr 24, 2005 11:33 pm; edited 1 time in total |
|
Back to top |
|
|
PrometheusDrake n00b
Joined: 29 Jan 2005 Posts: 18
|
Posted: Sun Apr 24, 2005 11:03 pm Post subject: |
|
|
I've just followed teidon's method. Emerged and patched "on the fly". I still get the same error from WoW. Error 132 (0x85100084). After snooping around the technical board a little, I'm starting to wonder if it might have to do with me trying to run it from a mounted FAT32-disk. Anyone had a problem with running it like that? Gonna try to copy it over to the Ext3-partition soon (Once I get some leasure time, hopefully before next weekend ), and let you know how it goes.
--wh |
|
Back to top |
|
|
discomfitor l33t
Joined: 21 Feb 2003 Posts: 927 Location: None
|
Posted: Mon Apr 25, 2005 12:08 am Post subject: |
|
|
DrewMadMax: You can't use native dlls for opengl stuff. Are you sure you're building wine with opengl enabled? _________________ There is no substitute for experience.
Imperfection indicates a lack of effort. |
|
Back to top |
|
|
Septor Apprentice
Joined: 01 Sep 2004 Posts: 150
|
Posted: Mon Apr 25, 2005 3:09 am Post subject: |
|
|
PrometheusDrake wrote: | I've just followed teidon's method. Emerged and patched "on the fly". I still get the same error from WoW. Error 132 (0x85100084). After snooping around the technical board a little, I'm starting to wonder if it might have to do with me trying to run it from a mounted FAT32-disk. Anyone had a problem with running it like that? Gonna try to copy it over to the Ext3-partition soon (Once I get some leasure time, hopefully before next weekend ), and let you know how it goes.
--wh |
I run it with no problems on a Fat32 partition (so I can dual boot and share the files, which works just fine). I have successfully used both 20050310 and 20050419 (~x86 keyword) with thte try6 patch... I wouldn't recommend the CVS version because you can't be sure it is in a stable state when you check it out.
I just noticed the following in your log:
Code: |
fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 16 to 32
|
are you sure you have the following lines in your wtf/Config.wtf and are using "-opengl":
Code: |
SET gxColorBits "24"
SET gxDepthBits "24"
|
|
|
Back to top |
|
|
PrometheusDrake n00b
Joined: 29 Jan 2005 Posts: 18
|
Posted: Mon Apr 25, 2005 6:06 am Post subject: |
|
|
Yup, just doublechecked. |
|
Back to top |
|
|
Septor Apprentice
Joined: 01 Sep 2004 Posts: 150
|
Posted: Mon Apr 25, 2005 7:15 am Post subject: |
|
|
Is your Xserver running in 16bit color mode by any chance?
My xorg.conf for my nVidia machine has the following screen section. Yours should be similar with the exception of the resolutions and maybe the string names. Most importantly note the DefaultDepth is 24. If you are still having troubles after checking this, post your /var/log/Xorg.0.log
Code: |
Section "Screen"
# The Identifier, Device and Monitor lines must be present
Identifier "Screen 1"
Device "NVAGP"
Monitor "Generic Monitor"
# The favoured Depth and/or Bpp may be specified here
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
|
Edit: I just re-read your old post and saw that you indeed are using DefaultDepth 16... change that to 24, restart X and you should be ready to play! |
|
Back to top |
|
|
teidon Apprentice
Joined: 22 Apr 2005 Posts: 195 Location: Finland
|
Posted: Mon Apr 25, 2005 8:17 am Post subject: |
|
|
PrometheusDrake, I noticed that there were "err:opengl:wglCreatePbufferARB blah blah" in the output of wine and also the patch didn't ably cleanly but there were some trouble patching opengl32/wgl_ext.c. If those same errors happened with the emerged and "patched on the fly" wine-20050310, those maybe the source of your problem (the patch has something to do with Pbuffer... not that I have any clue what it is and what it does ). Make sure that the patch file isn't broken, I didn't get any errors when I patched.
Also, have you tried to use "clean" wine configs and c_drive? Try to rename .wine (located in your home directory) to something else, and then run wine without parameters and it will create a new .wine from default files. Then try to run WoW, and if it still not working you can get rid of the new .wine and rename the older one back to .wine. I just tested and the clean .wine works with WoW - no changes needed to get WoW working.
For future reference for all those reading this: If some program/game isn't working with wine even if it should work, try to use clean .wine directory. Over time you do some changes to the config files, add some dll's to c_drive/windows/system, maybe override some dlls, etc etc and some of those changes may break something. That happened for me when I tried to get WoW's 1.4 patch to work with wine. Did everything as were told, tried different versions of wine and it just didn't work. Then tried it with clean .wine directory, installed Firefox and Mozilla ActiveX controller to it (because the patch won't work without them) and 1.4 patch worked without any issues. |
|
Back to top |
|
|
PrometheusDrake n00b
Joined: 29 Jan 2005 Posts: 18
|
Posted: Mon Apr 25, 2005 11:56 am Post subject: |
|
|
Septor: heh, waddaya know... Somehow overlooked that little something... The default was 16. I'll try when I get home tonight, and let you know if it works.
Teidon: That error did not occur during the emerge. Everything apparently went smooth. |
|
Back to top |
|
|
ackward Apprentice
Joined: 06 Sep 2002 Posts: 192
|
Posted: Mon Apr 25, 2005 1:07 pm Post subject: |
|
|
teidon wrote: | Here's a way how I installed and patched wine. WoW works fine and this is also newbie friendly way of doing it as there's no need to mess with cvs.
1. Get the try6 patch from somewhere.
2. Open 2 terminal programs and "su" to root in both of them.
3. Type this to one of the terminals, but don't execute it yet (note that that directory doesn't exist until you do emerge wine and the source has been unpacked, so copy+pasteing this might be a good idea. Remember to change "/location/to/try6-patch" to the correct one): cd /var/tmp/portage/wine-20050310-r1/work/wine-20050310/ && patch -p0 < /location/to/try6-patch
4. In the other terminal do "ACCEPT_KEYWORDS=~x86 emerge =wine-20050310-r1" and after it says ">>> Source unpacked." execute the line in the other terminal.
5. Now just sit back and wait until wine has been emerged.
Incase emerging went well and there were no errors during patching you now have a wine which can run WoW (atleast it's working for me). |
I though I was using a dirty hack to patch ebuilds but you beat me
What I usually do:
1. Get the patch from somewhere.
2. emerge wine and when it says "source unpacked" and begin the checkings, press "ctrl+z" sleeping the proccess.
3. patch
4. Resume with "fg" the sleeped/blocked process. |
|
Back to top |
|
|
teidon Apprentice
Joined: 22 Apr 2005 Posts: 195 Location: Finland
|
Posted: Mon Apr 25, 2005 3:09 pm Post subject: |
|
|
ackward: Guess you can do it that way too. I didn't know about fg... I'm a Linux newbie
Couple comments on the Darckness's guide on the first post:
- The minimap problem has been fixed some time ago, so I guess those parts of the guide could be removed as it's no-ones problem anymore (WoW doesn't work anymore with the earlier versions of wine and cedega where minimap were still problem).
Quote: | Here's another performance fix which I find to be extremely effective:
In your wine config file, set
Quote: | "Desktop" = "current desktop resolution"
"UseDGA" = "N"
"UseXVidMode" = "N" |
|
I tried those, but...
... Setting "Desktop" to "1280x1024" caused WoW to run in window even if I don't have windowed mode selected in WoW.
... If I set "UseXVidMode" to "N" the ingame gamma setting won't work. I guess that can be fixed with a simple script (xgamma -gamma xx && wine WoW.exe -opengl && xgamma -gamma 1)
... I didn't notice any difference in performance having "UseDGA" set to N or Y, though I didn't test it for long...
Then for those having sound issues:
There has been some sound issues even for Windows users and this little tweak has helped most (if not all) Windows users, so maybe it helps you Linux users too. I haven't had any issues with sounds but I did this little tweak when I first heard about it. Add this line to WTF/Config.wtf:
Quote: | SET SoundBufferSize "200" |
You can try bigger values but don't change to something overly big, because that's the sound buffers length in milliseconds. If you set it to for example 1000, all the sounds will be played 1sec after the event (spell casting, weapon hit...) happened. I tryed to set it to 20 and the sounds messed pretty much completely. Other thing is that I use OSS with wine (I have ALSA + OSS emulation), but I didn't notice any difference using ALSA instead after a quick test. |
|
Back to top |
|
|
PrometheusDrake n00b
Joined: 29 Jan 2005 Posts: 18
|
Posted: Mon Apr 25, 2005 5:41 pm Post subject: |
|
|
It works! Set the Deafult Depth to 24, started WoW.exe, and she runs. Now I just have to fix an unrelated xfce4-problem to make it run higher than 800x600...
Thanks a bunch for all the help, people. |
|
Back to top |
|
|
MurlocDundee n00b
Joined: 26 Mar 2005 Posts: 2
|
Posted: Mon Apr 25, 2005 10:01 pm Post subject: |
|
|
Blork Hello everyone, my respect to Darckness. Don t stop the good work.
I am following this thread since 1 month and I m very pleased with the support that it brings to us Wine users.
I feel that s the moment to post something about my own experience in running WoW with Wine. I will not go through each step of the installation instructions i did , i just stick to the CVS howto and it went fine. I used the CVS 2 days ago..
MurlocDundee, realm : Garona location : France |
|
Back to top |
|
|
Lucky B Apprentice
Joined: 01 Apr 2005 Posts: 235 Location: Florida
|
Posted: Tue Apr 26, 2005 1:43 am Post subject: |
|
|
cleanest way to apply the patch is the following:
Code: |
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild fetch
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild unpack
cd `portageq envvar PORTAGE_TMPDIR`/portage/wine-20050419/work/wine-20050419/
patch -p0 < /location/to/try6-patch
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild merge
|
Voila!
EDIT: See below, Septor gave me a great idea =P _________________ We are Dyslexic of Borg. Fusistance is retile. Your ass will be laminated.
Last edited by Lucky B on Tue Apr 26, 2005 2:16 am; edited 2 times in total |
|
Back to top |
|
|
Septor Apprentice
Joined: 01 Sep 2004 Posts: 150
|
Posted: Tue Apr 26, 2005 2:06 am Post subject: |
|
|
Lucky B wrote: | cleanest way to apply the patch is the following:
Code: |
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild fetch
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild unpack
cd `portageq envvar PORTAGE_TMPDIR`/portage/wine-20050419/work/wine-20050419/
patch -p0 < /location/to/try6-patch
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild compile
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild preinst
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild install
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild postinst
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild qmerge
|
Voila!
I am actually pretty sure preinst and postinst are unnecesary. |
or just:
Code: |
build `portageq portdir`/app-emulation/wine/wine-20050419.ebuild unpack
cd `portageq envvar PORTAGE_TMPDIR`/portage/wine-20050419/work/wine-20050419/
patch -p0 < /location/to/try6-patch
ebuild `portageq portdir`/app-emulation/wine/wine-20050419.ebuild merge
|
This should work and should be equivalent to the above... personally though I'd recommend adding patches to new ebuild in your portage overlay directory. |
|
Back to top |
|
|
Lucky B Apprentice
Joined: 01 Apr 2005 Posts: 235 Location: Florida
|
Posted: Tue Apr 26, 2005 2:15 am Post subject: |
|
|
ooo, merge works too, 10x easier, never tried : _________________ We are Dyslexic of Borg. Fusistance is retile. Your ass will be laminated. |
|
Back to top |
|
|
SDraconis n00b
Joined: 20 Apr 2005 Posts: 53
|
Posted: Tue Apr 26, 2005 5:36 am Post subject: |
|
|
I am having problems still with getting the game going. Unfortunately, my issue is not with the patch at all, as I have a patched copy that I pulled from Windows. I can get past the login screen and past the character screen. My problem occurs when I try to enter the world. I can get up to the point where I can actually see the area my character is in, and then the game totally freezes. I uninstalled, cleaned/updated my Wine from CVS and reapplied Try6 this morning, and then recompiled. Before this recompile, I was getting a similar result, except that sometimes I was actually able to get my character to move a little before WoW crashed with an error #132. Also before the recompile, WoW would sometimes freeze up my entire system to the point where I would have to hard reboot. My current situation has two scenarios: either it freezes when my character health bar still says "Unknown identity" or just after it loads in my name, but still freezes before my character model can actually be seen. Either way, it will just sit there and suck up 100% of a CPU until I Ctrl+C in the xterm I started it from.
Background:
-ATI card using ati-drivers from Portage
-Wine from CVS with Try6
-Using filter_ext for fixing the OpenGL corruption on ATI cards
Output to console:
Code: | Warning: could not find DOS drive for current working directory '/home/sdraconis', starting in the Windows directory.
fixme:opengl:query_function_pbuffer gl_version is: "1.3.4893 (X4.3.0-8.10.19)"
fixme:opengl:query_function_pbuffer glx_exts is: "GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_import_context GLX_ARB_get_proc_address GLX_ARB_multisample "
fixme:opengl:query_function_pbuffer gl_version is: "1.3.4893 (X4.3.0-8.10.19)"
fixme:opengl:query_function_pbuffer glx_exts is: "GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_import_context GLX_ARB_get_proc_address GLX_ARB_multisample "
err:shell:SHGetFolderPathW Failed to create directory 'L"C:\\windows\\profiles\\sdraconis\\Temporary Internet Files"'.
err:shell:SHGetFolderPathW Failed to create directory 'L"C:\\windows\\profiles\\sdraconis\\History"'.
err:shell:SHGetFolderPathW Failed to create directory 'L"C:\\windows\\profiles\\sdraconis\\Cookies"'.
fixme:advapi:SetSecurityInfo stub
fixme:powrprof:DllMain (0x4c400000, 1, (nil)) not fully implemented
fixme:ntdll:NtPowerInformation semi-stub: SystemPowerCapabilities
fixme:powrprof:DllMain (0x4c400000, 0, (nil)) not fully implemented
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bf6c0,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bf4dc,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bfa7c,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bfa7c,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bf9e4,0x00000000), stub!
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bf9d8,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bf1ec,0x00000000), stub!
fixme:system:SystemParametersInfoW Unimplemented action: 112 (SPI_GETMOUSESPEED)
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:sync:CreateIoCompletionPort (0xffffffff, (nil), 00000000, 00000000): stub.
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB
fixme:wininet:InternetSetOptionW Option 6 STUB
fixme:wininet:InternetSetOptionW Option 45 STUB
fixme:imm:ImmGetContext (0x10022): stub
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bea54,0x00000000), stub!
fixme:user:EnumDisplayDevicesA ((nil),0,0x406bea94,0x00000000), stub!
fixme:opengl:wglGetPixelFormatAttribivARB unsupported 2003 WGL Attribute
fixme:opengl:wglGetPixelFormatAttribivARB unsupported 2003 WGL Attribute
[This repeats for awhile]
fixme:opengl:wglGetPixelFormatAttribivARB unsupported 2003 WGL Attribute
fixme:opengl:wglGetPixelFormatAttribivARB unsupported 2003 WGL Attribute
err:ntdll:RtlpWaitForCriticalSection section 0x4fcfd50c "?" wait timed out in thread 0014, blocked by 0009, retrying (60 sec) |
That last line appears just as the loading bar is finishing and right before the world loads and freezes.
If there's anything else I can post that might be helpful (config file, etc.) let me know.
Update: I'm able to get in game the last couple tries and move around for a couple minutes before it freezes. Still freezes every time though... |
|
Back to top |
|
|
Septor Apprentice
Joined: 01 Sep 2004 Posts: 150
|
Posted: Tue Apr 26, 2005 6:53 am Post subject: |
|
|
You don't need you use my filter_ext library if you are using the ati-driver 8.12.10 package (which I highly recommend to all fglrx driver users). What extensions were you filtering anyways? The try6 patch allows you to filter extensions with a wine registry entry, so you don't need the filter_ext even if you did want to exclude extensions.
I get a lockup and/or crash after about 20-30 minutes of play with Wine+try6 patch. Cedega works much longer, but eventually seems to crash as well. Framerates are pretty bad with the ATI fglrx driver, but I don't have an nVidia card to compare, so it could just be that WoW is slow in Wine/Cedega. I have a Radeon 9800XT and WoW is really smooth in WinXP with all settings on max.
One thing you might want to try is to use the try2 and fixwow patches instead of try6... I think I had more success with those when running for a long time.... I'll try those again tonight probably. |
|
Back to top |
|
|
SDraconis n00b
Joined: 20 Apr 2005 Posts: 53
|
Posted: Tue Apr 26, 2005 7:07 am Post subject: |
|
|
Septor wrote: | What extensions were you filtering anyways? |
GL_ARB_vertex_buffer_object, as stated on the first post of this thread. It makes a huge difference.
Septor wrote: | The try6 patch allows you to filter extensions with a wine registry entry, so you don't need the filter_ext even if you did want to exclude extensions. |
What reg entry in which file would I change?
Septor wrote: |
I get a lockup and/or crash after about 20-30 minutes of play with Wine+try6 patch. Cedega works much longer, but eventually seems to crash as well. |
Mine is closer to 3-5 minutes before crash, and Cedega isn't worth it for something that still crashes anyway.
Septor wrote: | Framerates are pretty bad with the ATI fglrx driver, but I don't have an nVidia card to compare, so it could just be that WoW is slow in Wine/Cedega. I have a Radeon 9800XT and WoW is really smooth in WinXP with all settings on max. |
Yeah, same with me and my Radeon 9700. No lag issues in XP, except back when I did dual monitors in the summer, and then barely noticable.
Septor wrote: | One thing you might want to try is to use the try2 and fixwow patches instead of try6... I think I had more success with those when running for a long time.... I'll try those again tonight probably. |
I will give that a shot, but I suppose it means sticking with filter_ext. Oh well, whatever gets me playing WoW with less fear of a random freeze. |
|
Back to top |
|
|
discomfitor l33t
Joined: 21 Feb 2003 Posts: 927 Location: None
|
Posted: Tue Apr 26, 2005 8:02 am Post subject: |
|
|
teidon: Those performance fixes basically force WoW to run in a big window. WoW thinks it's running fullscreen though, and I find this to be very beneficial if you're like me and switch between applications/desktops frequently. No more minimizing WoW!
SDraconis: What kernel do you use? If it isn't ck-sources, try ck-sources. It's my patchset of choice for gaming, and is extremely well made to boot. Also try using wine 20050310. I remember getting that problem back in the days when wine didn't work with WoW, so it could be your version somehow.
Septor: What kernel are YOU using? I recommend ck-sources to you as well if you aren't using them. As with above, which wine version are you using? _________________ There is no substitute for experience.
Imperfection indicates a lack of effort. |
|
Back to top |
|
|
Lifetech n00b
Joined: 17 Mar 2005 Posts: 4
|
Posted: Tue Apr 26, 2005 11:02 am Post subject: |
|
|
Darckness wrote: |
EDIT: Woohoo! I have once again beaten TG in my (free) support of WoW. |
sorry to break the party I installed it the same day on cedega, just followed some instructions on the TG forum.
No problems @ all. No fixed needed from TG.
that're critics on you're work though! seen superb howto's from you, keep it up |
|
Back to top |
|
|
Septor Apprentice
Joined: 01 Sep 2004 Posts: 150
|
Posted: Tue Apr 26, 2005 4:06 pm Post subject: |
|
|
Darckness:
I am currently using gentoo-dev-sources-2.6.11-r6 with the ati-drivers-8.12.10 video drivers. For wine I was using 20050310 with try6 (hacked an ebuild for myself) but am now using wine 20050419 with try6 patch (again, made an ebuild for myself... I love ebuids ).
I run WoW in fullscreen mode with XrandR=Y and XVidMode=Y and DGA is disabled in my xorg.conf (since it is broken/not recommended with the ATI binary driver). Using wineoss driver with ALSA OSS emulation in kernel (using winealsa driver seems to cause crashes more often). Also I "renice 19 wine-preloader" to fix audio skipping in my WoW start script.
SDrakonis:
Download this file: http://bugs.winehq.org/attachment.cgi?id=827&action=view and run winereg on it to disable the vertex buffer object extension. As I said previously though, this extension is not bugged in the ati-driver 8.12.10 ebuild, so I recommend you upgrade so you don't need to disable the extension.
For those intested the wine patch bug log is at: http://bugs.winehq.org/show_bug.cgi?id=2814 |
|
Back to top |
|
|
Jamal n00b
Joined: 20 Apr 2004 Posts: 44
|
Posted: Tue Apr 26, 2005 4:53 pm Post subject: |
|
|
Hi, I'm using cvscedega and have nearly the same Error:
Code: | bash-2.05b$ cvscedega WoW.exe
fixme:keyboard:X11DRV_KEYBOARD_DetectLayout Your keyboard layout was not found!
Using closest match instead (German keyboard layout without dead keys) for scanc ode mapping.
Please define your layout in windows/x11drv/keyboard.c and submit them
to us for inclusion into future Wine releases.
See the Wine User Guide, chapter "Keyboard" for more information.
fixme:win32:PE_CreateModule Security directory ignored
fixme:win32:PE_CreateModule Load Configuration directory ignored
fixme:ver:GetVersionExA OSVERSIONINFOA is too large (possibly OSVERSIONINFOEXA)
fixme:system:EnumDisplayDevicesA ((nil),0,0xb7b00098,0x00000000), stub!
fixme:system:EnumDisplayDevicesA ((nil),0,0xb7affeb4,0x00000000), stub!
fixme:system:EnumDisplayDevicesA ((nil),0,0xb7b00454,0x00000000), stub!
fixme:system:EnumDisplayDevicesA ((nil),0,0xb7b00454,0x00000000), stub!
fixme:system:SystemParametersInfoA Unknown action: 113
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(9,(nil)): stub!
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
fixme:system:EnumDisplayDevicesA ((nil),0,0xb7affbc4,0x00000000), stub!
fixme:system:SystemParametersInfoA Unknown action: 112
fixme:imm:ImmAssociateContext (0x00010021, 0x00000000): stub
fixme:system:SystemParametersInfoA Unknown action: 113
fixme:dsound:DirectSoundCreate8 Check wcaps
fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0xb7b8f3cc,00010021,2):stub
mmtime pid=18013 tid=18013
fixme:dsound:DirectSoundCreate8 Check wcaps
fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0xb7b903b8,00010021,2):stub
fixme:win32:CreateIoCompletionPort (ffffffff, 0000, 00000000, 00000000): stub.
fixme:winsock:WS_bind Setting WS_SO_REUSEADDR on socket before we binding it
fixme:imm:ImmAssociateContext (0x00010021, 0x00000000): stub
fixme:wininet:InternetSetOptionW STUB (0xb7bc6024, 0x00000002, 0xb7b0074c, 4)
fixme:wininet:InternetSetOptionW STUB (0xb7bc6024, 0x00000006, 0xb7b0074c, 4)
fixme:imm:ImmAssociateContext (0x00010021, 0x00000000): stub
fixme:imm:ImmAssociateContext (0x00010021, 0x00000000): stub
fixme:imm:ImmGetContext (0x00010021): stub
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
err:ddraw:Direct3DDevice9_DestroyContext destroying context while in scene
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
err:x11drv:X11DRV_DDHAL_CreateSurface created multiple primary surfaces
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
err:ddraw:Direct3DDevice9_DestroyContext destroying context while in scene
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
err:x11drv:X11DRV_DDHAL_CreateSurface created multiple primary surfaces
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
err:ddraw:Direct3DDevice9_DestroyContext destroying context while in scene
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
err:x11drv:X11DRV_DDHAL_CreateSurface created multiple primary surfaces
fixme:ddraw:Direct3DDevice9_CreateQuery (0xb7b8854c)->(8,0xaf9b7aa4): stub!
fixme:ddraw:Direct3DDevice9_ShowCursor (0xb7b8854c)->(0): stub
fixme:ddraw:D3D_GL_update_render_states unsupported render state 161 (MULTISAMPL EANTIALIAS), value=0x00000001
fixme:ddraw:D3D_GL_update_render_states unsupported render state 162 (MULTISAMPL EMASK), value=0xffffffff
fixme:ddraw:Direct3DDevice9_SetStreamSource offset=25216
err:x11drv:error_handler GLXBadLargeRequest error (161) for X request 143 minor 2 serial 24978 from thread 0x00000002
X Error of failed request: GLXBadLargeRequest
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 2 (X_GLXRenderLarge)
Serial number of failed request: 24978
Current serial number in output stream: 24985 |
I'm using an ATI Card (ATI Radeon 8500) and 2.6.11 kernel
Can anybody help me with this fault? |
|
Back to top |
|
|
DrewMadMax n00b
Joined: 29 Sep 2002 Posts: 43
|
Posted: Tue Apr 26, 2005 10:41 pm Post subject: |
|
|
Darckness:
Yeah, I was running wine with opengl enabled. I even tried re-emerging it like so:
Quote: | USE="opengl" emerge wine |
but still no joy. Where is wine supposed to find those dlls? The only ones I have listed after doing a locate (yes, I have run updatedb just beforehand) are the ones in my XP mount, and an opengl32.dll included as part of cedega.
Thanks,
--D _________________ "True Knowledge Exists in Realizing Your Own Ignorance" |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|