DC>> But, I may see your point!  COMMAND is 50k and CMD is 87k!

 DC>> Other than the bloat, is there really a difference?

 ml>> 16bit vs. 32bit maybe? ;)

 DC> That, and more...

 DC> I don't need to LH Switcher to make it all work.  It uses
 DC> XMS like DOS should have done years ago.

errrmmm... XMS and EMS are 16bit ways to gain access to memory above
640k... 32bit stuffs access memory in one huge pool and can generally see
all of it at once instead of having to use 64k pages (EMS) or allocate
spaces of 64k (XMS)...

once you get into the 32 bit world, all the old rules and terms get thrown
out the door...

FWIW: there is DOS capable of seeing all the memory in a box in one huge
chunk... however, many programs simply can't operate in that environment...
i've used such in attempts to pull data from a crashed NTFS formatted
XPHome system with LapLink... LapLink for DOS wouldn't operate in that
environment... i was forced to use the (old?) "standard" 16bit
ways and load the DOS NTFS driver and then use a very old serial port
transfer program called ZIP (no relation to archiving) since it would run
in much less memory than LapLink for DOS... yes, it took many hours to pull
the several hundred megs of data off that drive onto a w98se box at the
other end of the 115200bps serial cable but it worked and my client was
happy to get their data... so happy that they insisted i take $100US as
payment or they'd find a way to give it to me as a gift of some sort...

i believe the above was done with freedos and some additional memory
driver/management software... i downloaded the image from the internet and
bitcopied it to a floppy which booted directly and i then only had to add
the DOS NTFS driver... that thing consumes a /lot/ of memory...

)\/(ark