Re: Steam can not be launched

[James McKenzie <jjmckenzie51@xxxxxxxxxxxxx>]

On 1/14/11 1:05 AM, shogun1234 wrote:
> I follow the instruction at http://appdb.winehq.org/objectManager.php?sClass=version&iId=19444 to install wine in order to play Steam. However `wine Steam.exe` throws
>
>
> Code:
>
> err:menubuilder:init_xdg error looking up the desktop directory
> fixme:process:GetLogicalProcessorInformation ((nil),0x32e49c): stub
> fixme:process:GetLogicalProcessorInformation (0x1dcfc00,0x32e49c): stub
> fixme:process:SetProcessShutdownParameters (00000100, 00000000): partial stub.
> err:ntlm:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth>= 3.0.25 is in your path.
> err:ntlm:SECUR32_initNTLMSP Usually, you can find it in the winbind package of your distribution.
> fixme:urlmon:CoInternetSetFeatureEnabled 5, 0x00000002, 1, stub
> fixme:urlmon:CoInternetSetFeatureEnabled 10, 0x00000002, 1, stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1009e, 2, 0x32d334, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1009e, 3, 0x32d338, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1009e, 4, 0x32d33c, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100a6, 2, 0x32d964, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100a6, 3, 0x32d968, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100a6, 4, 0x32d96c, 4) 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 0x1d0b80, L"ROOT\\CIMV2", (null), (null), (null), 0x00000080, (null), (nil), 0x420beb8)
> fixme:dwmapi:DwmSetWindowAttribute (0x100b2, 2, 0x32d8cc, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100b2, 3, 0x32d8d0, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100b2, 4, 0x32d8d4, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100ba, 2, 0x32d80c, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100ba, 3, 0x32d810, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100ba, 4, 0x32d814, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100c4, 2, 0x32d2e4, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100c4, 3, 0x32d2e8, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100c4, 4, 0x32d2ec, 4) stub
> fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used
> fixme:dwmapi:DwmSetWindowAttribute (0x100e0, 2, 0x32d94c, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100e0, 3, 0x32d950, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x100e0, 4, 0x32d954, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1011c, 2, 0x32d514, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1011c, 3, 0x32d518, 4) stub
> fixme:dwmapi:DwmSetWindowAttribute (0x1011c, 4, 0x32d51c, 4) stub
> fixme:process:GetLogicalProcessorInformation ((nil),0x33fc74): stub
> fixme:process:GetLogicalProcessorInformation (0x435c00,0x33fc74): stub
> fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported
>
>
>
>
> Then I search forum which comes up with this thread - http://forum.winehq.org/viewtopic.php?t=9410, which seems has problem similar to mine, suggesting http://bugs.winehq.org/show_bug.cgi?id=24096#c5 would solve the issue by rename GameOverlayRender.dll. However, after renaming the file, the Steam still fail to launch. I can only type id/ password and see it trying connecting, then fail.
I found an interesting thread on Steam game problems in the Codeweavers 
support forum (thank you Ken Thomases for one of the solutions), after 
googling on the error message above and finding nothing on MSDN or any 
other authoritative web site.  Problems with the gameoverlay.dll file 
have been discussed many times in relationship to Steam games.

For those, you can go into the Wine Configuration (winecfg) tool  
(code:  wine winecfg or just plain winecfg).  On winecfg's Applications 
tab, click Add Application.  Select the executable of the Steam game 
that's having the problem (or just type its filename, like /foobar.exe/) 
and click Open.  Select the Libraries tab of winecfg.  Type 
GameOverlayRenderer in the "New override for library" edit field, click 
the Add button, click the Edit button, select Disable, click OK, and 
click OK.  That prevents the in-game community overlay from even being 
loaded for that game.

You can apply this to the entire WinePrefix by not typing in a game name 
and then following the instructions above.  This will stop loading of 
this file for all programs in the WinePrefix.

Something else you might want to try IF this does not work is using 
winetricks and installing MDAC 2.8 (some games are strange and use a 
database access for their game data.)

James McKenzie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-users/attachments/20110120/3ea83d98/attachment.htm>