Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!bellcore!ulysses!ucbvax!blue.rutgers.edu!JOSEPH
From: JOSEPH@BLUE.RUTGERS.EDU (Seymour)
Newsgroups: mod.protocols.appletalk
Subject: Birth of a Seagate
Message-ID: <12189944316.50.JOSEPH@BLUE.RUTGERS.EDU>
Date: Tue, 11-Mar-86 17:44:02 EST
Article-I.D.: BLUE.12189944316.50.JOSEPH
Posted: Tue Mar 11 17:44:02 1986
Date-Received: Thu, 13-Mar-86 00:04:29 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-applebus@c.cs.cmu.edu

Rutgers university is currently trying to bring up our seagate box.

We have customized all the software by putting our network addresses
in it, compiled it, downloaded it to the gateway and run it.  The
gateway gives us the hello banner message and responds to "s" status
requests.  The Ethernet side of the gateway seems to be working,
packets come and go, but the Appletalk side just sits there.  The
Apple PEEK diagnostic sees no packets on the network and the "s"
status request shows an ever growing number of Appletalk packets
"deferred."

From looking through the code it looks like the Appletalk board thinks
it is constantly getting collisions when trying to send data.  Has
anyone else run into this one?  Can anyone give me any quick tests to
do to see what is wrong.  We have the program TESTSCC but no
documentation for it or datasheets on the chip to tell us what to do
or what to expect as output.

Any help would be appreciated.

			Thanks
			Seymour Joseph
-------