Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!rutgers!mit-eddie!bloom-beacon!eru!luth!sunic!mcsun!ukc!mucs!craven!dente
From: dente@craven.ee.man.ac.uk (Colin Dente)
Newsgroups: comp.sys.apollo
Subject: Re:  AT Ethernet card diagnostic
Message-ID: <1470@m1.cs.man.ac.uk>
Date: 19 Jul 90 10:33:58 GMT
References: <9007182125.AA08879@richter.mit.edu>
Sender: news@cs.man.ac.uk
Organization: Manchester Computer Centre, University of Manchester UK
Lines: 21

In article <9007182125.AA08879@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
>Ether card diagnostics are now part of DEX, the mnemonic debuggers diagnostic
>executive program. Shut down your node, type RE to reset the system, type
>EX DEX to run the exec (if it asks for a password, try "service"), type run
><name> where <name> is the diagnostic you want.

One additional point: The ether diagnostic requires another machine to be
running the same diagnostic in slave mode - so if you've only got one ether
card - you are, to put it mildly, shafted.  The other ethernet card can
certainly be either another AT bus one, or a VME, but I'm not sure if you
can use the COM-ECMB multibus board (I've only got a multibus in a cranky
old DSP-80A, and I don't let it talk to the ethernet any more.)

Colin


--
 Colin Dente                      | JANET: dente@uk.ac.man.ee.els
 Dept. of Electrical Engineering  | ARPA:  dente@els.ee.man.ac.uk 
 University of Manchester, UK     | UUCP:  ...!ukc!man.ee.els!dente 
                 ... I am the one you warned me of ...