Making a system DLL unavailable (problem with COMMCTRL)

[Samuel Audet]

Hello,

Eric Pouech wrote:
> one of the things you could try (but that's risky) is to compile wine 
> twice. First time with standard option, second time with disabling 
> compilation of 16 bit part. Then use the commctrl DLL from the second 
> compilation in the first compilation. But you need to do everything by 
> hand.
> The best solution anyhow is to understand why Wine's commctrl in 16 bit 
> fails and fix it.

Thanks for the tip! I have tried something else since then.  I modified 
OWL50.DLL to look for COMMCTRL.DLL in say CRAPPY00.DLL, and that made 
the DLL unavailable all right, but it still didn't work correctly.  I 
get the same "no dialog" dialog window that is either huge, or tiny, 
depending on other options, and with 100% CPU usage.  My guess is, 
OWL50.DLL correctly detects that Wine's COMMCTRL.DLL is a stub and 
starts using its emulated controls, but fails to display them...

Anybody has some debugging experience with Wine to give me hint as to 
where I should start looking why OWL50.DLL can't display its emulated 
controls on Wine?  Thank you

later!