http://bugs.winehq.org/show_bug.cgi?id=20265
--- Comment #18 from Howie Hoyt n4af@pvrc.org 2010-05-11 08:41:36 --- f/b = feedback Comment #10 stipulates that you must *both* use wine-1.0 (specifically below 1.0.166) AND (initially) start TR4W via the technique I outlined, whereby you start tr4w WITH the specific directory of your CFG file. With Wine1.0, this should bring TR4W up but it will fail when you enter data to log. Exit TR4W, return the startup to point to just the tr4w.exe (as normal) and all should work...
You can either do the above from terminal mode or modify the tr4w wine icon (right click) then properties.
Testing on Ubuntu 10.4, Linux Mint 8 (Ubuntu 9.10), PCLinuxOS 2010, and Mepis8.5 (KDE 4.3) all worked for me.
a) wine 1.0 b) --one time start WITH directory of cfg--
All was then ok. I could re-boot, and start TR4W normally.
I think all the problems in this bug are different symptoms, depending on your actual level of Wine 1.0 ?
73, Howie