http://bugs.winehq.org/show_bug.cgi?id=14970 chris ahrendt <celticht32(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #15582|0 |1 is obsolete| | Attachment #15640|0 |1 is obsolete| | Attachment #15641|0 |1 is obsolete| | --- Comment #19 from chris ahrendt <celticht32(a)aol.com> 2008-08-25 18:44:43 --- Created an attachment (id=15643) --> (http://bugs.winehq.org/attachment.cgi?id=15643) here is a log with nothing pointing to d3d10 nor the ATI drivers I do not see anywhere in here where this points to a ATI driver issue and believe your anti-ATI bias from the development list has bled over to this. There is nothing in this log to point to an ATI failure. the winmm is not the ATI I do not see the usual ATI issues within this log. The Check Texture error earlier in the log is not this problem and had another bug opened and then closed as a dupe against the Age of conan issues. If you look there is a section at the end 0022:fixme:dbghelp:dump_system_info fill in CPU vendorID and feature set 0022:err:d3d:IWineD3DDeviceImpl_Reset Cannot change the back buffer format yet 0022:err:d3d:IWineD3DDeviceImpl_Reset What do do about a changed auto depth stencil parameter? 0034:err:ntdll:RtlpWaitForCriticalSection section 0x60b921c0 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0034, blocked by 0022, retrying (60 sec) 0022:fixme:winmm:MMDRV_Exit Closing while ll-driver open 0022:fixme:winmm:MMDRV_Exit Closing while ll-driver open the winmm error is not caused by ATI... it should not close while leaving the driver open. the critical section could be caused by the ATI or could be caused by another multi-media device... it just depends on where it is in the call.. keep the Bias out of the bug list -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.