native user32 dll
michael.cardenas at lindows.com
Mon May 6 08:50:08 CDT 2002
Why would address space separation break the native user dll? Shouldn't
wine's address space handling be the same as windows? Maybe there's
something I'm not understanding...
On Sat, May 04, 2002 at 11:48:12PM +0200, Ulrich Weigand wrote:
> > > and I was wondering if it's still true.
> > yes, and it will likely remain so
> > native user32 requires lots of bits from native
> > kernel (which are no longer available because of
> > adress space separation)
> From what I recall, the core problem was that shared DLL
> segments no longer worked after address space separation,
> and user heavily relies on those to implement its cross-
> process activities (like messages etc.).
> 32-bit PE shared section were fixed in the meantime and
> should work again, I gather, but 16-bit NE shared segments
> still do not work. Unfortunately, all the real work is
> done in the 16-bit user (32-bit user32 is just a wrapper
> layer), so this is probably a show-stopper.
> (Maybe it would be possible to run only a single task
> with native user. But I haven't tried in a long time,
> and it's probably broken for some reason or other ...)
> Dr. Ulrich Weigand
> weigand at informatik.uni-erlangen.de
lead windows compatibility engineer
"Be the change you want to see in the world"
More information about the wine-devel