wine users - Apr 2001 - directx problems methinks

im trying to run worms world party with wine cvs 04/13/01
after manually instaling by installing on a windows machine then copying 
acorss to my machine (it uses installshield which crashes under wine), the 
game launches

it is really really horribly flickery, and quite slow. its a directdraw 
game, but as far as i can tell its not making any attempt to change to the 
resolution it wants. im pretty sure the game is in 8bit colout, btu when i 
run x in 8bit colour, wine looks really messed up.

anyway, i can get to the menu system (ignoreing the epillepsy-inducing 
flickering). teh problem is, i cant actually click on anything. the mouse 
moves around the window fine, but none of the buttons respond. this is 
quite a problem as the game doesnt have keyboard input for the menu so i 
cant actually start playing.

ive tried with dga, without dga, with mousegrab and without, in a desktop 
and without, etc etc etc but nothing makes a difference

i get a few errrors when the game starts up - 

chuzwuzza:/usr/local/wine/Team17/Worms\ World\ Party# wine wwp.exe
Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel 
(0x4036db38)->(00000168,00000011)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel 
(0x4036db38)->(00000168,00000011)
fixme:dsound:IDirectSoundImpl_SetCooperativeLevel 
(0x43dc8a18,00000168,2):stub
err:local:LOCAL_GetBlock not enough space in GDI heap 021f for 1048 bytes
fixme:gdi:GetObjectType Magic 113d not implemented
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device 
VNETBIOS
fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device NWLINK

then it says "fixme:gdi:GetObjectType Magic 113d not implemented"
about a
million times, interspersed with the odd directsound stuffup.


any help is greatly appreciated

 -- Michael Pearce

Michael Pearce <chuzwuzza@ematic.com> wrote:
> im trying to run worms world party with wine cvs 04/13/01
> after manually instaling by installing on a windows machine then copying 
> acorss to my machine (it uses installshield which crashes under wine), the 
> game launches
> it is really really horribly flickery, and quite slow. its a directdraw 
> game, but as far as i can tell its not making any attempt to change to the 
> resolution it wants. im pretty sure the game is in 8bit colout, btu when i 
> run x in 8bit colour, wine looks really messed up.
> anyway, i can get to the menu system (ignoreing the epillepsy-inducing 
> flickering). teh problem is, i cant actually click on anything. the mouse 
> moves around the window fine, but none of the buttons respond. this is 
> quite a problem as the game doesnt have keyboard input for the menu so i 
> cant actually start playing.
> ive tried with dga, without dga, with mousegrab and without, in a desktop 
> and without, etc etc etc but nothing makes a difference
> i get a few errrors when the game starts up - 
> chuzwuzza:/usr/local/wine/Team17/Worms\ World\ Party# wine wwp.exe
> Could not stat /mnt/fd0 (No such file or directory), ignoring drive A:
> fixme:ddraw:Main_DirectDraw_SetCooperativeLevel 
> (0x4036db38)->(00000168,00000011)
> fixme:ddraw:Main_DirectDraw_SetCooperativeLevel 
> (0x4036db38)->(00000168,00000011)
> fixme:dsound:IDirectSoundImpl_SetCooperativeLevel 
> (0x43dc8a18,00000168,2):stub
> err:local:LOCAL_GetBlock not enough space in GDI heap 021f for 1048 bytes
> fixme:gdi:GetObjectType Magic 113d not implemented
Ouch. You're running out of GDI heap.
No wonder you've got graphics problems like hell.

Try to debug why the program uses so much GDI space.

Andreas Mohr