Click to See Complete Forum and Search --> : Half Life Multiplayer w/Winex


Mayor McCheese
12-02-2002, 08:45 PM
I can run half life fine with WineX in single player mode, but if I try to play it multiplayer (by starting a lan game or joining one) it simply freezes as soon as the "loading" screen comes up. I've been working on this for the better half of a week and I'm all out of ideas; avenues I've already investigated include:

- I use an Nvidia card, and the Nvidia drivers are installed correctly, with no misc mesa files leftover (the nvidia check script says im clear as well, and all my other opengl programs run fine). I've also tried two different Nvidia cards (a TNT2 and a Geforce4)

- I've tried several different versions of winex, including the cvs 200, 220, 221, and ive tried installing it manually and with the getwinex scripts. They have varying degrees of success but none get past the loading screen in multiplayer

- I've tried half life 1.0, 1.1.0.8 and 1.1.1.0; 1.0 doesnt load anything, bnut 1.1.0.8 and 1.1.1.0 can run single player fine, they just freeze on the loading screen of any multiplayer game.

Any help would be greatly appreciated, suggestions or possible ideas to try, 'cuz I'm at a dead end.

Mayor McCheese
12-02-2002, 08:58 PM
Oh, I've also tried running winex with the debugmsg +all option .... I don't see any obvious errors, but there's so much output it would take a long time to go through it all. Any pointers on how to approach this aspect would be helpful too

Icarus
12-02-2002, 10:34 PM
Try running it with +err instead of +all...all is way too much to comprehend and slows it down...

You also need the latest patches to play multiplayer online...which I see you have

Mayor McCheese
12-03-2002, 12:17 AM
using the +err flag outputs nothing winex doesnt typically output

Mayor McCheese
12-03-2002, 12:20 AM
This is the output when I run winex (and kill it after it freezes):

# winex221 --winver winxp hl.exe -- hl.exe -console
err:midi:OSS_MidiInit ioctl on midi info for device 0 failed.
err:win32:_EnterSysLevel (0x40c649a8, level 2): Holding 0x40d0400c, level 3. Exp
ect deadlock!
fixme:font:GetCharABCWidthsW (0864,0000,00ff,0x41dc1d1c), returns slightly bogus
values.
fixme:font:GetCharABCWidthsW (086c,0000,00ff,0x41dc2da4), returns slightly bogus
values.
fixme:font:GetCharABCWidthsW (0874,0000,00ff,0x41dc3e2c), returns slightly bogus
values.
fixme:font:GetCharABCWidthsW (087c,0000,00ff,0x41dc4eb4), returns slightly bogus
values.
fixme:reg:RegFlushKey (68): stub
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40220690)->(00000000,00000008
)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40220690)->(00000000,00000013
)
wine: Unhandled exception, starting debugger...
err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134658088 132"
) (2)
Read the Wine Developers Guide on how to set up winedbg or another debugger
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40220690)->(00000000,00000008
)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x40220690)->(00010021,00000013
)
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (10021), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (3004a), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (10061), stub!
fixme:dc:LockWindowUpdate (0), stub!
fixme:dc:LockWindowUpdate (1006c), stub!
fixme:dc:LockWindowUpdate (0), stub!
/usr/bin/winex221: line 258: 1062 Killed /usr/lib/winex221/bin
/wine "$@"

Icarus
12-03-2002, 04:12 PM
Well, first you shouldn't run anything in wine as root...bad idea, infect your Linux machine with a Windows virus become amussing...because then they work ;)

Second, try launching half-life using win98 emu...

$ winex221 --winver win98 hl.exe -- hl.exe -console

Then you can always run the +all debugmsg and run it to a file...

$ winex221 --winver win98 hl.exe -- hl.exe -console >> half.log

and then grep the file for all the errors...

$ more half.log|grep err