http://bugs.winehq.org/show_bug.cgi?id=32762
Bug #: 32762 Summary: Worms Forts Under Siege crashes and freezes my DVD-ROM drive (WTF?) Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: muzerakascooby@gmail.com Classification: Unclassified
Created attachment 43242 --> http://bugs.winehq.org/attachment.cgi?id=43242 backtrace of crash
This is a really weird issue, which I'm going to try to investigate further because it's so odd. I've installed Worms Forts Under Siege on my laptop, a Thinkpad T410 with a Panasonic UJ892 DVD drive. After manually fixing the already-reported issue with the 64-bit system and the copy protection driver (SafeDisc v4.00.000 according to ProtectionID), when I attempt to run it now, it displays a small white square in the middle of the screen for a good few minutes, then crashes with a page fault on write with a standard backtrace, attached. What's weird is what happens next - despite the program cleanly exiting and nothing (according to lsof) using the filesystem or hardware device, the disc drive then completely freezes. You can unmount it, but after that, you can't remount it, you can't eject it (with eject or with the button), it stays spun-up forever, and if you manually eject it it doesn't detect that the disc has been removed/replaced and doesn't spin up when you reinsert the disc. The only way to get it back AFAICT is to eject the whole drive from the bay and reinsert, or presumably to reboot.
I don't know which part of this, if any, is a wine bug, and which (surely partially) is a driver/hardware/possibly BIOS bug (does the BIOS have any hand in things?), but I thought it'd be best to report it just in case. I'm going to try using someone else's drive (I have many friends with different models of ThinkPad, the bays all hopefully being compatible) to see if it exists there. On my 32-bit desktop, the game runs fine on all three drives past the point where it would have crashed here (but crashes shortly afterwards anyway with presumably a different bug).
Incidentally, running wine in Win9x mode causes the copy protection system to detect a debugger; running it in Win2k mode causes the program to silently exit; XP and above cause as described.