HP3000-L Archives

December 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Aaron Christopher Finney <[log in to unmask]>
Reply To:
Aaron Christopher Finney <[log in to unmask]>
Date:
Tue, 1 Dec 1998 01:29:58 -0800
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (38 lines)
On Tue, 1 Dec 1998, Melvin R Rees wrote:

> According to the HP configuration guide, the Lanic must be in slot #1
> of the expansion cage.  I know the lanic is very sensitive to the card
> slot since I have one also.
>
> Try to move it.
>
> Rgds
> Mel Rees
> [log in to unmask]


A manual...a manual...my kingdom for a manual...

When the system came to me, it was a working pull that hadn't been touched
(internally) since the move, and the lanic card is in slot #5. Frank
McConnell gave me the idea of switching the SQE test signal on the
transceiver, which didn't do anything different. However, since I had to
use another transciever which had dip switches to control the SQE signal,
I decided to play with them all to see what happened. And guess what?
Switching the link beat signal off (which, IIRC, makes the transciever
think it's connected to another functioning device on the network) fixed
the problem. It now tries to warmboot without any conplaints at all, and
then proceeds to time out on the device identification. I have a couple of
HP-IB cables coming in the next week or so, and I'll let everyone know how
it goes when I get to hook up the drives. The one that was damaged in
transit "only fell in the grass", according to the transporter, but has
severe enough case damage that I'm a little worried about it. Will update
soon...

Sincere thanks to everyone who helped me get this far.


Cheers,

Aaron

ATOM RSS1 RSS2