http://bugs.winehq.org/show_bug.cgi?id=16162
--- Comment #3 from Austin English austinenglish@gmail.com 2008-11-23 13:28:24 --- (In reply to comment #2)
It doesn't output anything but that, and setting WINEDEBUG=+all or adding own debugging output to the code (even empty ERR lines) causes a page fault instead. Also, using a debugger causes some other crashes at some other points depending on exact usage, usually a stack overflow or a privileged instruction.
I seem to remember that in the past (a year or two ago) the game managed to start and draw the menu screen once before hanging with timeout in WaitFor-something.
A regression test would help here: http://wiki.winehq.org/RegressionTesting