http://bugs.winehq.org/show_bug.cgi?id=22580
--- Comment #50 from joakim.tjernlund@transmode.se 2010-05-15 10:00:32 --- (In reply to comment #49)
(In reply to comment #48)
That seems like a waste of time, such things has been tired before, see http://bugs.winehq.org/show_bug.cgi?id=13687 for instance.
The main problem remains the same: tmo=0 isn't handled by Wine like Windows < Vista does. Any app that relies on the old convention will experience the 100% CPU or similar. If you really want to help, you should try my patch on all those 100% CPU bugs in bugzilla and see if that helps.
No, bug 13687 pertains to the use of native crypt32. I'm not dismissing the
Read harder, he tries with and without native crypt32
validity of this report, but, since the motivation for using native crypt32 in the first place is because of problems using Wine's implementation of crypt32, exposing defects in the builtin version not a bad thing to do.
We are way past native crypt32 or not, I have identified a bug in Wine and you don't want to fix it until someone can find an app that you approve of suffers the same fate as crypt32 does. I think the burden lies on Wine to prove that none of the 100% CPU bugs are affected by this bug.