Comment 78 for bug 205895

(In reply to comment #14)
> (In reply to comment #13)
> > I just proved that this has nothing to do with ies4linux. I don't think you
> > read what I wrote.
>
> I think I missed that part as well. If you want to prove it's not an ies4linux
> problem you have to show that the problem occurs with plain Wine without native
> overrides. Alternatively, if you think something is wrong with
> RegisterWaitForSingleObjectEx(), you can write a test case for that function
> that passes on native Windows but fails on Wine.

Here is the simple method I used:

1. install current stable wine + install ies4linux == the 100% cpu bug.
2. install wine compiled without RegisterWaitForSingleObjectEx + install
ies4linux == no bug.

and
3. install wine + ie6 using winetricks == Runtime Error R6025 (pure virtual
function call)

I realize this may not satisfy your standards of proof, but steps 1 & 2 do show
that the direct causative factor in this specific case is not ies4linux, rather
it is the change in wine.

Granted, ies4linux is present, but it is a constant factor and the variable
factor is wine. Therefore, in this limited case, the change in wine can be said
to produce the bug.

I recognize you are saying there may be a deeper issue, but step 3 indicates
that there is not an easy alternative to doing what I did. Therefore, may I
suggest that looking into the bug reported by Brandon Koepke is worthwhile?

I do not have the skill to write a test case as you suggest. My personal
problem is solved; therefore, I am investing the time in responding in the hope
of clarifying this issue for others. I cannot do more than describe my
experiences in detail. I will be glad to answer more questions, if that helps.
I'll even run additional tests with different methods of installing ie6 + 128
bit encryption if someone wants to point me in the right direction. (I think
winetricks ie6 might work if I could get all the required encryption DLLs
registered, but I have not been able to do that on my own.)