Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!aramis.rutgers.edu!athos.rutgers.edu!hedrick From: hedrick@athos.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.appletalk Subject: Re: Help With RU-CAP! Message-ID: Date: 27 Oct 90 06:08:03 GMT References: <1990Oct26.170431.13614@rodan.acs.syr.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 28 To: srvarma@rodan.acs.syr.edu The new version of CAP is just like the old one, but gives your Suns the option to use Ethertalk on the Ethernet rather than IPtalk. This would allow Macs with Ethertalk cards to talk directly to the Sun rather than through the KBox. Of course Macs on Localtalk would still need to go through the Kbox. The Kbox would have to be reconfigured so that its Ethernet side speaks Ethertalk rather than IPTalk. Access to laserprinters is unchanged. It's the same software. It just uses Ethertalk instead of IPtalk, i.e. the format of the packet headers on the Ethernet is different. I haven't tried Etherprint. If it does what I think (make the LW an Ethertalk host) then you would be able to talk from the Sun to the LW directly, without needing a KBox. Of course if you have any Macs on the Localtalk, they'll still need the Kbox. Note that CAP currently supports only Ethertalk phase I. Thus the Macs with Ethertalk and the EtherPrint would have to be configured to use phase I. The only time this should be a problem is - if you have more than 254 hosts on one Ethernet, or on a collection of Ethernets connected by level 2 bridges (*real* bridges, not what Apple calls bridges, which are really routers) - if you are running software that only supports phase 2. Some commercial Unix or VMS Appletalk software is this way.