Need help interpreting event log

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well,  good old Simcity 4 is now giving me event entries I've never seen before.  The last one gave me a crash to the desk top, which is not unusual for this game, but I don't understand what the log is telling me.  Please have a look at this and see if you can help out.

[code]
fixme:system:SystemParametersInfoW Unimplemented action: 94 (SPI_GETMOUSETRAILS)
fixme:win:EnumDisplayDevicesW ((null),0,0x32efd8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32ef04,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32f5bc,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32f2e4,0x00000000), stub!
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16
fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.
Please configure the application to use double buffering (1 back buffer) if possible.
fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats
fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer
fixme:mixer:ALSA_MixerInit No master control found on USB Device 0x46d:0x8ad, disabling mixer
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x21aa58,0x21ae80): stub
fixme:d3d_surface:IWineD3DSurfaceImpl_BltZ (0x1d97bb8): Unsupp depthstencil blit
fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers.
fixme:d3d_surface:IWineD3DBaseSurfaceImpl_Blt Can't handle WINEDDBLT_ASYNC flag right now.
fixme:d3d_surface:IWineD3DSurfaceImpl_BltZ (0x1d12a0): Unsupp depthstencil blit
fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers.
fixme:d3d_surface:surface_load_location Unimplemented location SFLAG_INSYSMEM for depth/stencil buffers.
fixme:d3d_surface:IWineD3DSurfaceImpl_Unmap Depth Stencil buffer locking is not implemented
fixme:win:EnumDisplayDevicesW ((null),0,0x32f538,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32f538,0x00000000), stub!
fixme:imm:ImmGetOpenStatus (0x12fb00): semi-stub
fixme:imm:ImmReleaseContext (0x20020, 0x12fb00): stub
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x1
fixme:advapi:RegisterEventSourceA ((null)," "): stub
fixme:advapi:RegisterEventSourceW (L"",L" "): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000060,0x61e6cc,0x63b98a): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x00000060,0x128280,0x63b98a): stub
err:eventlog:ReportEventW L"6"
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
fixme:advapi:RegisterEventSourceA ((null)," "): stub
fixme:advapi:RegisterEventSourceW (L"",L" "): stub
fixme:advapi:ReportEventA (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x000002cc,0x61e6cc,0x63ba2a): stub
fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000000,(nil),0x0001,0x000002cc,0x128280,0x63ba2a): stub
err:eventlog:ReportEventW L"7"
fixme:advapi:DeregisterEventSource (0xcafe4242) stub
[/code]

I am particularly interested in the err:eventlog lines.  Is there an EventLog?  If so, where?







[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux