I tried setting WINEDEBUG to +all and running the game. Without this setting, the process ran for just a few seconds before quitting. With WINEDEBUG set to +all, it ran for several hours generating loads of entries in the log. The RAM usage ran to several GB. When I came back to it after dinner WineHelper had crashed. Is there a lower level of debugging I could use which will give me the information I need without taking so long and eventually killing WineHelper? I read this page (http://www.codeweavers.com/support/docs/wine-user/x2194) but I don't know which options will give me the information I need.
