http://bugs.winehq.org/show_bug.cgi?id=20866
--- Comment #18 from Juan Lang juan_lang@yahoo.com 2009-12-03 17:44:10 --- (In reply to comment #17)
Isn't it possible (and worth) to try to solve the problem with the 1.0.1 version, since, although a rather old version, it is the last stable release?
It's possible, but much for difficult for us since we don't have access to the program ourselves. At best we'd just be guessing. Without access to the program, what's more likely to happen is that the bug just doesn't get fixed, except perhaps accidentally.
What's really helpful for us is if you could: 1. Open a bug about the problems with the latest version, and flag that it's a regression. 2. If at all possible, perform a regression test to find out what broke between 1.0.1 and 1.1.33. Regression testing is described here: http://wiki.winehq.org/RegressionTesting
This process is a little time consuming, and it might be intimidating, but pinpointing exactly which patch breaks your program goes a long way to helping us find out what's causing the problem.