> -----Original Message-----
> From: Andreas Mohr [mailto:andi@rhlx01.fht-esslingen.de]
> Sent: Wednesday, July 10, 2002 2:03 PM
> To: Medland, Bill
> Cc: Wine devel (E-mail)
> Subject: Re: Any advice on how to debug this?
>
>
> On Wed, Jul 10, 2002 at 01:11:59PM -0700, Medland, Bill wrote:
> > > -----Original Message-----
> > > From: Alexandre Julliard [mailto:julliard@winehq.com]
> > >
> > > That's a common problem with Win9x dlls. It cannot be
> completely fixed
> > > because we don't control the layout of our address space;
> there are
> > > some hacks that could be done in the loader to make it
> less likely to
> > > happen, but I'm not convinced it is worth the trouble. Our efforts
> > > would probably be better spent making sure the builtin
> versions of the
> > > offending dlls work properly.
> > >
> > > --
> > > Alexandre Julliard
> > > julliard(a)winehq.com
> > >
> > Thanks Alexandre. I guess the lesson is to use NT dlls
> wherever possible.
> No way. Wine still has lots of problems with NT DLLs, since
> they are...
> NT DLLs ;)
> Wine's support for NT API is too damn incomplete, so you'll
> have more luck
> with Win9x DLLs in most cases.
> Or just choose to not use *any* Windows DLLs. Might help.
But that means I would have to fix yet more of the bugs in comctl32.dll.so
;-(
Actually what I was doing was trying to run the native comctl32 to see if it
corrected the visual bugs so that I would know that it was within that dll.
I'll see what I can do about fixing them in a bit.
Bill