[Wine] Fedora Core 4 system lockup with wine 200506.. - 0.9.1

[Adam Gibson]

System specs:
Fedora Core 4
2.6.13-1.1532_FC4smp
ATI Radeon 9200 SE
P4 2.4Ghz (hyperthreading)
xorg 6.8.2
Aureal Semiconductor Vortex 2 sound card
Intel 82801EB chipset

wine-20050524 FC3 rpm works just fine on my FC4 system.  But any 
versions after that lockup my system when running wine.  For the 200506 
- 200510 versions of wine I have compiled them from scratch so I assumed 
it was something I was doing wrong.  I have been waiting for an official 
RPM from winehq to make sure that the problem still exists and now that 
0.9.x RPMs for FC4 are available I have now verified that the lockups 
still persist.

Interestingly I remember seeing someone in a discussion forum with the 
same problem I do and interestingly he had the same video card (ATI 
9200se).  I can not seem to find a link for that anymore though.

If I run wine it says creating configuration directory ... for the first 
time but after a few seconds my system locks up(keyboard does not 
respond(caps, etc)).  The I have tried using the xorg ATI driver and the 
proprietary ati drivers and even running the non SMP kernel(I have a P4 
hyperthreading CPU) but I still get the same lockups.

The old 20050524 version of wine works without locking up my system.

The .wine config directory does seem to be created:

[user at host ~]$ ls -al .wine
total 312
drwxrwxr-x    4 agibson agibson   4096 Nov  9 17:38 .
drwx--x--x  148 agibson agibson  32768 Nov 11 15:42 ..
drwxrwxr-x    2 agibson agibson   4096 Sep  6 09:44 dosdevices
drwxrwxr-x   11 agibson agibson   4096 Nov  9 15:14 drive_c
-rw-rw-r--    1 agibson agibson 225409 Nov  9 17:28 system.reg
-rw-rw-r--    1 agibson agibson   1470 Nov  9 17:28 userdef.reg
-rw-rw-r--    1 agibson agibson   6816 Nov  9 17:38 user.reg
[user at host ~]$ ls -al .wine/dosdevices/
total 68
drwxrwxr-x  2 agibson agibson 4096 Sep  6 09:44 .
drwxrwxr-x  4 agibson agibson 4096 Nov  9 17:38 ..
lrwxrwxrwx  1 agibson agibson   13 Sep  6 09:41 a: -> /media/floppy
lrwxrwxrwx  1 agibson agibson    8 Sep  6 09:41 a:: -> /dev/fd0
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:41 c: -> ../drive_c
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:41 com1 -> /dev/ttyS0
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:41 com2 -> /dev/ttyS1
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:41 com3 -> /dev/ttyS2
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:41 com4 -> /dev/ttyS3
lrwxrwxrwx  1 agibson agibson   12 Sep  6 09:43 d: -> /media/cdrom
lrwxrwxrwx  1 agibson agibson   10 Sep  6 09:44 d:: -> /dev/cdrom
lrwxrwxrwx  1 agibson agibson    8 Sep  6 09:41 lpt1 -> /dev/lp0
lrwxrwxrwx  1 agibson agibson    4 Sep  6 09:41 x: -> /tmp
lrwxrwxrwx  1 agibson agibson   13 Sep  6 09:42 y: -> /home/agibson
lrwxrwxrwx  1 agibson agibson    1 Sep  6 09:41 z: -> /

Anyone have any ideas that could track down the cause of the lockups? 
You can't really debug much when the whole system locks up.  I have to 
hit the reset button to get things running again.  I have not 
experienced any other lockup issues running any other apps with this 
system for the past year.