> I'd like to see all 16-bit interfaces replaced by 32-bit

Yes, indeed. And the first place for IBM to start is to get its
driver development team to recognize that using an obsolete version
of Microsoft C and MASM to make 16-bit OS/2 device drivers is not
a very efficient nor flexible environment to create the complex drivers
required for such things as MMPM and such.
   OS/2 doesn't just need native software in order to run more
efficiently and with more flexibility than Windows; it also needs
native device drivers, and you're not going to see improved performance
there over Windows when OS/2 programmers are using the exact same
tools (actually, older versions of the same tools) and working within
the same Intel segmentation constraints as Windows programmers.
   But try to tell that to the IBM Device Driver Team, which apparently is
comprised of folks who have spent altogether too much time using, and
getting too comfy with, MSC 6.0 and MASM 5.1 and far/near pointers, and
have yet to jump onto the 32-bit bandwagon like OS/2 customers want

--- Maximus/2 2.01wb