http://bugs.winehq.org/show_bug.cgi?id=11537
--- Comment #5 from Austin English austinenglish@gmail.com 2008-02-12 11:39:46 --- (In reply to comment #2)
Performing a regression test between 0.9.45 (known good) and 0.9.50 (known bad) I ran into another regression at wine-0.9.49-196-ga6dd479 which prevents testing this issue. Is there some way to get around this regression without messing up the binary search?
Can you describe the regression better? You could try resetting git to 0.9.46/7, see if they're good/bad, then use that as the known good/bad in a separate regression test. Without knowing what's wrong, it's hard to say.
It appears that the installer is largely unstable between 0.9.49 where it worked, and 0.9.50 where this bug first occurred.
Here are my results:
wine-0.9.49 good wine-0.9.49-196-ga6dd479 untestable (cannot run install shield) wine-0.9.49-235-ga0c3816 untestable (fails to copy first file with 1603) wine-0.9.50 bad
What should I do next to help out?
If this is the same regression, then you can try 'random' patches in between, or you could find the patch(es) that fix install shield using reverse regression testing: http://wiki.winehq.org/ReverseRegressionTesting
In short, describe your problem(s) more, but it doesn't look like an easy solution.