http://bugs.winehq.org/show_bug.cgi?id=2398
------- Additional Comments From phil@ldex.terica.net 2006-28-04 10:10 ------- Is there any reason why the new code (that worked for me and others) and the old approach cannot co-exist, with the mode being defined per-application as part of the command line (or as a registry switch)? Even if this were simply a short term, ugly hack, it would be better than the current 'non-existant' fix(es) being discussed. (#31 - did not get an explanation as to why this might not be workable)
This, at least, would get us something usable whilst the 'proper' solution is thrashed out. It's rather frustrating to see such a large issue remain unsolved for such a long period of time. It's more frustrating to realise that, if the wine development team need to do this kind of thing again in the future, all users will be in exactly the same position again. That concerns me no end and must dent the enthusiasm of any developer hoping to use Wine to provide a linux version of their software to customers. Throwing away the working implementation wholesale, without any apparent fallback, is deeply regrettable. Having the old mode back as a 'shim' would greatly reduce the pain that this issue is causing, especially given the proximity of a 1.0 release.
For the moment, I *have* to run the old version of Wine because it is the *only one* that works for me. I cannot, though, file bug reports because they will be discounted until I can reproduce them in the current version. I cannot run any of the newer versions because, for my purposes and applications, they are broken.....and so on. (#34)
-
Wine Bugs