-----Original Message-----<br>
From: Stefan Dösinger <stefan@codeweavers.com><br>
To: celticht32@aol.com<br>
Cc: 'Ivan Gyurdiev' <ivg231@gmail.com>; 'James Hawkins' <truiken@gmail.com>; wine-devel@winehq.org<br>
Sent: Wed, 23 Jul 2008 12:10 pm<br>
Subject: RE: EverQuest2.exe and context.c<br>
<br>
<div id="AOLMsgPart_0_a4b94410-1815-433b-9730-b35de60bdcf2" style="margin: 0px; font-family: Tahoma,Verdana,Arial,Sans-Serif; font-size: 12px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
<pre style="font-size: 9pt;"><font face="Arial, Helvetica, sans-serif">>> Ok I did a clean install.. rebuilt wine from the base 1.1.1 code put<br>
>> the above patch into the context.c and reran EverQuest2.exe I put<br>
>> export WINEDEBUG=+d3d,+sed before running and am attaching the trace.<br>
>> (If you need more just send me a message and I will retry it.<br>
>> I still get the card does not have pixel shader error (and yes the card<br>
>> has pixel shaders (its an ATI FIREGL5200)). I am attaching the log and<br>
>> the screenshot.<br>
>Don't let yourself be fooled by the pixelshader error message. It most<br>
>likely has nothing to do with pixel shaders at all. Most likely the game<br>
>does something like this:<br>
><br>
>try {<br>
> do_init_1();<br>
> do_init_2();<br>
> do_init_3();<br>
>} catch(all_stuff_that_can_go_wrong) {<br>
> /* Initialization fails. This usually means that the card doesn't have<br>
>the features<br>
> * we need<br>
> 20 */<br>
> MessageBox("NO PIXEL SHADERS!!!!! GO BUY A BETTER CARD!!11!1!!\n");<br>
>}<br>
><br>
>Of course the app isn't prepared for other things to go wrong, e.g. a Wine<br>
>bug or a driver bug, and fails to write as much details about the problem as<br>
>it can. Writing proper error paths is a pain in the ass, and so on.<br>
><br>
>wine: Unhandled page fault on read access to 0x016c6580 at address 0xa3502f<br>
>(thread 0021), starting debugger..<br>
><br>
>This line is much more suspicious. The app seems to crash somewhere, and as<br>
>far as I can see in the log long after initializing the opengl context. It<br>
>does a reset call, but the Reset call succeeds. If changing the pixel format<br>
>loading changes the behavior, it's most likely because it avoids triggering<br>
>some crash in the graphics driver(doesn't mean it is a driver bug though).<br>
<br>
<br>
</font><font face="Arial, Helvetica, sans-serif">Agree'ed, so suggestions on what to turn on to get a better idea on whats causing the page fault.. <br>
the +relay dump isn't really helping per'se I did parse it and get somewhat of a list of calls but I don't <br>
know if that would help here that is :<br>
<br>
advapi32.RegCloseKey,advapi32.RegCreateKeyW,advapi32.RegSetValueExA,Comctl32.386,comctl32.ImageList_Destroy,devenum.DllCanUnloadNow,dsound.DllCanUnloadNow ,dxdiagn.DllCanUnloadNow <br>
fixme:dsound:DllCanUnloadNow,gdi32.DeleteDC,gdi32.DeleteObject,KERNEL32.__wine_dll_unregister_16,KERNEL32.CloseHandle,KERNEL32.CreateFileA,KERNEL32.ExitProcess,KERNEL32.FlsGetValue,<br>
KERNEL32.F
lushFileBuffers,KERNEL32.FreeLibrary60b4a693,KERNEL32.GetLastError,KERNEL32.GetProcAddress,KERNEL32.GetProcessHeap,KERNEL32.GetSystemTimeAsFileTime,KERNEL32.GlobalDeleteAtom<br>
KERNEL32.GlobalFree,,KERNEL32.GlobalUnlock,KERNEL32.HeapDestroy,KERNEL32.InterlockedDecrement,KERNEL32.InterlockedExchange,KERNEL32.LocalFree,KERNEL32.OutputDebugStringA<br>
KERNEL32.QueryPerformanceCounter,KERNEL32.QueryPerformanceFrequency,KERNEL32.RaiseException,KERNEL32.ReleaseMutex,KERNEL32.SetConsoleCtrlHandler,KERNEL32.SetEvent<br>
KERNEL32.SetLastError,KERNEL32.SetStdHandle,KERNEL32.SetUnhandledExceptionFilter,KERNEL32.Sleep,KERNEL32.TlsFree,KERNEL32.TlsGetValue,KERNEL32.VirtualQuery,KERNEL32.WaitForSingleObject<br>
KERNEL32.WaitForSingleObjectEx,KERNEL32.WriteFile,midimap.DriverProc,midimap.modMessage,msacm32.drv.DriverProc,msacm32.drv.widMessage,msacm32.drv.wodMessage,ntdll.RtlAllocateHeap<br>
ntdll.RtlDecodePointer,ntdll.RtlDeleteCriticalSection,ntdll.RtlEncodePointer,ntdll.RtlFreeHeap,ole32.CoTaskMemFree,ole32.OleUninitialize,PE:DLL,quartz.DllCanUnloadNow,rpcrt4.NDRCContextBinding<br>
rpcrt4.NdrClientContextMarshall,rpcrt4.NdrClientInitializeNew,rpcrt4.NdrGetBuffer,rpcrt4.NdrSendReceive,sensapi.IsNetworkAlive,user32.CharLowerW,user32.DefWindowProcW,user32.DestroyIcon<br>
user32.DestroyWindow,user32.DispatchMessageW,user32.GetMessageW,user32.PostQuitMessage,user32.UnregisterClassW,window:proc,winealsa.drv.DriverProc,winealsa.drv.DriverProc,winealsa.drv.midMessage<br>
winealsa.drv.modMessage,winealsa.drv.mxdMessage,winealsa.drv.widMessage,winealsa.drv.wodMessage,winex11.drv.ImeDestroy<br>
<br>
I am wondering if the winex11.drv is having issues with the ATI driver when it does the destroy? The above btw is not in any particular order or such as well... <br>
Any hints where to look next? I just found the alert log in the EverQuest2.directory so I attached that as well.. maybe that will give s
ome idea of what might be going on?<br>
<br>
<br>
Chris<br>
<br>
P.s. yes I know this reply is in html I am having to use the web to post this from work as they have smtp traffic blocked where I am and havent connected to my 3g modem to get around it =D<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font></pre>
</div>
<!-- end of AOLMsgPart_0_a4b94410-1815-433b-9730-b35de60bdcf2 -->
<div id='u8CABAFAEC9965FB-1770-DBB' class='aol_ad_footer'><FONT style="color: black; font: normal 10pt ARIAL, SAN-SERIF;"><HR style="MARGIN-TOP: 10px">The Famous, the Infamous, the Lame - in your browser. <A title="http://toolbar.aol.com/tmz/download.html?NCID=aolcmp00050000000014" href="http://toolbar.aol.com/tmz/download.html?NCID=aolcmp00050000000014" target="_blank">Get the TMZ Toolbar Now</A>!</FONT> </div>