jjmckenzie wrote:
> On Thu, May 26, 2011 at 1:49 PM, The Grim Ræper
> <wineforum-user@xxxxxxxxxx> wrote:
>
> > Again, it cacks out after the welcome and update screens show up.
> >
> >
> > Code:
> >
> > calvinps@smokebox ~ $ wine "C:\Program Files\Steam\Steam.exe"
> > fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
> > fixme:urlmon:CoInternetSetFeatureEnabled 5, 0x00000002, 1, stub
> > fixme:urlmon:CoInternetSetFeatureEnabled 10, 0x00000002, 1, stub
> > fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
> > fixme:toolhelp:Heap32ListFirst : stub
> > err:ole:CoGetClassObject class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
> > err:ole:CoGetClassObject no class object {77f10cf0-3db5-4966-b520-b7c54fd35ed6} could be created for context 0x1
> > fixme:wbemprox:wbem_locator_ConnectServer 0x1a2fb8, L"ROOT\\CIMV2", (null), (null), (null), 0x00000080, (null), (nil), 0x421c150)
> > fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used
> > err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 968
> > fixme:d3d:check_fbo_compat Format WINED3DFMT_R32_FLOAT with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
> > err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 968
> > fixme:d3d:check_fbo_compat Format WINED3DFMT_R32G32_FLOAT with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
> > err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 968
> > fixme:d3d:check_fbo_compat Format WINED3DFMT_R16_FLOAT with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
> > err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 968
> > fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_FLOAT with rendertarget flag is not supported as FBO color attachment, and no fallback specified.
> > fixme:d3d:check_filter Error during filtering test for format 822d, returning no filtering
> > fixme:d3d:check_filter Error during filtering test for format 822f, returning no filtering
> > fixme:win:EnumDisplayDevicesW ((null),0,0x32ce24,0x00000000), stub!
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub
> > fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:advapi:RegisterTraceGuidsW (0x38f5320, 0x3f4b738, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x3f23b24, (null), (null), 0x3f4b750,)
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETSTATE): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=3): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=1): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=0): stub
> > fixme:appbar:handle_appbarmessage SHAppBarMessage(ABM_GETAUTOHIDEBAR, hwnd=(nil), edge=2): stub
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> > fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
> >
> >
> Need to know what you mean by 'cacks out after the welcome and update
> screens show up'. Does the program stop responding, do you get a
> blank screen, or does the program terminate?
>
> Thank you.
It just quits after it finishes loading. I can't seem to gather why :?
