SH> COM/IP lets your dialup applications use virtual modems.  If
 SH> one is using dialup applications, that is a great idea.  If
 SH> one is using ADSL, one starts looking for different solutions.

COM/IP should still work perfectly fine... is it not, afterall, nothing
more than a shim that packages the data within telnet protocol packets?? a
shim doesn't care what kind of line it is riding on as long as it can
emulate a modem for the bbs side and pack/unpack the data in telnet packets
for tcp/ip transfer... that tcp/ip packets may be further carried within
atm packets is of no concern...

 MS>> BEING A `Win 2K' USER IS IN NO WAY PREVENTING THE USE OF
 MS>> `MS-Kermit' AS WELL.  Please, give the pre- emptive style a try

 SH> It prevents the use of Win2K in EVERY WAY if the Win2K user is
 SH> using ADSL or Cable to access the Internet.

how so?

 MS>> next time!  People "migrating" toward `Win 32' would
only hesitate
 MS>> less to make the switch if you didn't scare them away!  :>

 SH> I really doubt that someone who is migrating to Win2K will be
 SH> deterred by the absence of an ability to run a 16Bit DOS
 SH> application.

i really doubt that there are any, these days, who are migrating to w2k...
there are probably more trying to get to nt4 but even that is very limited
now that m$ is not providing /all/ the necessary bug fixes and security
updates for it that are necessary... m$ is forcing everyone to the XP
series...

)\/(ark