Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!pequod.cso.uiuc.edu!dorner
From: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Newsgroups: comp.sys.mac.comm
Subject: Re: Telnet...TCP or NCSA ???
Message-ID: <1990Oct3.213141.22323@ux1.cso.uiuc.edu>
Date: 3 Oct 90 21:31:41 GMT
References: <13794@slice.ooc.uva.nl> <4730@crystal9.UUCP>
Sender: news@ux1.cso.uiuc.edu (News)
Reply-To: dorner@pequod.cso.uiuc.edu (Steve Dorner)
Distribution: comp
Organization: University of Illinois at Urbana-Champaign
Lines: 19

In article <4730@crystal9.UUCP> derosa@motcid.UUCP (John DeRosa) writes:
>MacTCP - This feature is, at a simplistic level, a convienence for
>       the macintosh user. The advantage is that the addition of newer
>	MacTCP friendly programs will be easier as they all find their
>	network information in a common spot.

Well, not only do they find their network information in a common spot,
but you can run them AT THE SAME TIME.  I can, for example, run Eudora
(a MacTCP mail package that I like for some strange reason :-)) and NCSA
Telnet MacTCP at the same time, because they both use MacTCP.

This is not possible with the non-MacTCP version of NCSA Telnet or tn3270
or MacIP; with the non-MacTCP versions, it's ONE TCP/IP application at a time.
This is a major inconvenience.

The flip side is, you do have to pay money to Apple for MacTCP.
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu  UUCP: uunet!uiucuxc!uiuc.edu!s-dorner