Hello Bob!

17 Jan 03 13:41, Bob Jones wrote to All 16-bit (DOS) Max users:

 BJ> Since I plan to take the code forward with support for long file
 BJ> names, etc., would anyone object to removing the 16-bit (DOS and OS/2)
 BJ> compiled versions from future development?

I still run DOS and OS/2 flavors here on different nodes of a Netware 3.x
LAN here.  I did not advance to Max 3.x because it dropped support for a
couple of 2.x features I really liked, while the new features were not that
inspiring and were of the type would introduce some new issues for existing
maintenance utilities in use here.

I was also concerned that there was no updated MSGAPI.DLL in the Y2K-fix
distributions from Scott when they came out.  While it is possible that no
modifications were required for the 16-bit targets, I'm guessing that Scott
just blew past them as "no longer required/supported" himself. 
At least that's the logic I used when I deleted the old MSGAPI.DLL to keep
myself from accidentally hitting the messagebases with something that
depended on the older version.  It was always easier to remember how to
tack that "p" on the end of the DOS exe name than to properly
mangle the "386"/"32" derivatives in my head while
banging away at the commandline. :)

Point being that, as someone who's probably operating further back in Max
history than most you'll encounter and finicky enough to stay put in
backrevs without a compelling reason to upgrade, 16-bit versions are still
not a requirement for me and, in fact, I've taken extra steps to prevent
myself from accidentally using them. :)

.\\ike

--- GoldED 2.50+