> > 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 ...) Bye, Ulrich -- Dr. Ulrich Weigand [EMAIL PROTECTED]
