Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewse!jlc2
From: jlc2@cbnewse.att.com (john.chmielewski)
Newsgroups: comp.sys.next
Subject: SCSI Problem
Message-ID: <1991Feb21.183711.23994@cbnewse.att.com>
Date: 21 Feb 91 18:37:11 GMT
Organization: AT&T Bell Laboratories
Lines: 29


kls30@duts.ccc.amdahl.com (Kent L Shephard) writes:

>Well here's the deal.  I connected a Wren III to my cube internally and
>the cube doesn't even see the disk.

>[stuff deleted]

>Just for the hell of it while in the ROM monitor I tried the command
>bsd - to boot from the SCSI device to see what would happen.  It came
>back with the message that the SCSI bus was hung.  The exact same thing
>happens when there is no drive connected.

I've seen the same kind of problem when a Wren 4 was first attached to
the cube.  The problem was that the 50 pin SCSI flat ribbon cable was
connected upside down.  You should check to make sure that you do not
have the same problem.  When you look at a Wren 4 drive from the rear
(power connector on the right), pin 1 of the SCSI connector is on the
right.  I believe the same is also true for the Wren 3, however, if
you don't have a copy of the drive specs, you can download a copy,
including pinouts, from:
	SEAGATE TECHNOLOGY, INC.
	Technical Support Bulletin Board
	408/438-8771  [300-9600 HST, MNP 3/5, N-8-1]

Hope this helps.

	     			-jlc-
			jlc@alien.att.com


Brought to you by Super Global Mega Corp .com