Xref: utzoo comp.protocols.tcp-ip:10583 comp.sys.mac.programmer:13211
Path: utzoo!attcan!uunet!dino!sharkey!umich!ox.com!sendai!rich
From: rich@sendai.sendai.ann-arbor.mi.us (K. Richard Magill)
Newsgroups: comp.protocols.tcp-ip,comp.sys.mac.programmer
Subject: Re: Mac TCP--Info??
Message-ID: <RICH.90Mar15151409@sendai.sendai.ann-arbor.mi.us>
Date: 15 Mar 90 20:14:09 GMT
References: <7990@tank.uchicago.edu> <39441@apple.Apple.COM>
Sender: rich@sendai.UUCP
Reply-To: rich@sendai.ann-arbor.mi.us
Organization: Digital Works, Ltd. - Ann Arbor, MI
Lines: 27
In-reply-to: hayes@Apple.COM's message of 13 Mar 90 04:51:08 GMT

Before you get your hopes up...

In article <39441@apple.Apple.COM> hayes@Apple.COM (Jim Hayes) writes:

   Functionally:

	   It is co-resident with other drivers, including AppleTalk,
	   so you can use AppleTalk AND MacTCP simultaneously.

This isn't quite true.  Somehow there are collisions on a number of
annoying things on my se30 with a dove ether board.  I don't know
whose fault they are, (maybe mine), but when using net at all, (even
over ether), you can't configure your printer port to do much of
anything.  Also, you really have to reconfigure and reboot if you want
to use a) macTCP things vs b) old style ncsaTelnet vs well, you get
the idea.

   Technically:

	   On LocalTalk (or Ethernet networks with no IP routing
	   capabilities), MacTCP can encapsulate TCP/IP in AppleTalk
	   packets for later decomposition at an AppleTalk/IP bridge
	   on the destination network.  (I.e. Kinetics FastPath,
	   Cayman GatorBox, etc.)

But not vice verse.  ie, appletalk in ip, a la kip, so you would still
need a gateway to do CAP.