http://bugs.winehq.org/show_bug.cgi?id=20265
--- Comment #17 from Wylda wylda@volny.cz 2010-05-11 08:19:13 --- (In reply to comment #16)
Please ref: Comment #10 and f/b results.
Hi Howie, unfortunately i did not understand what you want to say by comment #10. Probably because english is not my native.
I have not been able to do regression testing yet because when I went to set the bisect good/bad I found i could not return wine to 'good' status.
You mean you had all "git bisect bad"? Than you did not pickup the GOOD commit correctly or you should do "make distclean" in-between each bisection.
After a LOT of testing, I found that making TR4W work (circumvention) consists of two parts. In terms of bz2 source, wine 1.0 must be used.
All the versions mentioned in comment #15 are from bz2 and not from git. So with 1.0 i fulfilled your suggestion, but it didn't help.
env WINEPREFIX="/home/howie/.wine" wine "C:\Program Files\TR4W\tr4w.exe" /CQ-M/CQM.CFG
For what reason i should do env WINEPREFIX wine PATH\tr4w.exe /CQ-M/CQM.CFG ??
How's that differs from: cd ~/.wine/drive_c/Program\ Files/TR4W wine tr4w.exe /CQ-M/CQM.CFG
Anyway, none of these work for me. Also i'm unsure, whether you are reporting the same issue as comment #0 or you are trying to pinpoint another issue.
What do mean by "f/b"?