


Code: Select all
fixme:advapi:SetSecurityInfo stub
fixme:powrprof:DllMain (0x59600000, 1, (nil)) not fully implemented
fixme:ntdll:NtPowerInformation Unimplemented NtPowerInformation action: 11
fixme:powrprof:DllMain (0x59600000, 0, (nil)) not fully implemented
fixme:win:EnumDisplayDevicesW ((null),0,0x55beeee0,0x00000000), stub!
fixme:d3d:IWineD3DImpl_GetDeviceCaps Caps support for directx9 is nonexistent at the moment!
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef44c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef6ec,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef6ec,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef654,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef640,0x00000000), stub!
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed?
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:win:EnumDisplayDevicesW ((null),0,0x55bef15c,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 INTERNET_OPTION_SEND/RECEIVE_TIMEOUT not supported on protocol 4
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB
fixme:wgl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need glXSelectEvent/GLX_DAMAGED work)
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed?
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:win:EnumDisplayDevicesW ((null),0,0x55bec7bc,0x00000000), stub!
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed?
fixme:wgl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need glXSelectEvent/GLX_DAMAGED work)
fixme:wgl:wglQueryPbufferARB unsupported WGL_PBUFFER_LOST_ARB (need glXSelectEvent/GLX_DAMAGED work)
fixme:imm:ImmAssociateContextEx (0x50024, (nil), 16): stub
err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed?
Well I cheated a bit as I use vmware to apply patch from Windows virtual machine as patch crashed both on wine and cedega (might have been some permissions issue non related to wine/cedega). Anyway now WoW runs fine with cedega...(will try wine later today). Many addons crashed, some even froze, I recommended to clean your Interface folder.urbanomad wrote:anyone having problems with the new WoW patch? (the one that downloads)
jstiles wrote: The dev team did isolate and fix one problem with the Updater today, where it would say "Preparing to update" at 1%, then immediately say that the patch is corrupt. This was a legitimate, honest-to-goodness bug, introduced in 1.11, and the fix for it is in final testing right now. We will be shipping this fix very soon.
Applying the update on a separate computer is a good workaround. I'm glad you mentioned that, because I hadn't considered it but it ought to work for most users... that is, if you have a second computer at your disposal
This particular bug is not related to CRC errors at all, though.
I'm running a 32 bit world - see the profileblk_jack wrote:The one thing that might be making a huge difference between tbacav and I is that even though I have a 64bit processor, my entire system is 32bit. That and I'm running a lower kernel, and lower versions of GCC+Glibc.
Code: Select all
SET gxApi "opengl"
SET gxWindow "1"
SET specular "0"
SET ffx "0"
SET pixelShaders "0"
SET movie "0"Well mine worked just prior to this and it still runs Frozen Throne just fine so I'm pretty sure it's a patch issue not my computer issue.Toadicus wrote:Game is running just fine for me, on both of my computers. One's running Gentoo ~x86, the other's running Ubuntu Dapper (32 bit), and I haven't run into any troubles of any kind. If anything, it's running better now. A friend of mine is running it in Gentoo ~amd64, and I just got done with a raid with him, so it's not a 64-bit issue, necessarily.