Ok it does not help programs where people have not done at least the min foot work for the application. Min foot work is having at least tested to what 2 versions of wine the fault happens between and that latest version is tested and still fails. ie like 0.9.60 and 0.9.61 as the two version no more than 1 version number apart. The test results in the appdb are useful. Now even better is if a person is prepared to take on a full regression hunt and find what patch causes its failure. http://wiki.winehq.org/RegressionTesting With the exact patch a really good bug report can be put in and a rollback patch created to keep application working until developers solve the issue. Working application comes down to how much user support we have for it too.
