Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!spool.mu.edu!samsung!olivea!oliveb!amdahl!JUTS!duts!kls30
From: kls30@duts.ccc.amdahl.com (Kent L Shephard)
Newsgroups: comp.sys.next
Subject: SCSI Problem
Summary: Why can't I get an internal or external drive to work.
Message-ID: <6e9B02XX05CB01@JUTS.ccc.amdahl.com>
Date: 21 Feb 91 15:28:54 GMT
Sender: netnews@ccc.amdahl.com
Reply-To: kls30@DUTS.ccc.amdahl.com (Kent L. SHephard)
Distribution: na
Organization: Amdahl Corporation, Sunnyvale CA
Lines: 33

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

I boot the machine running all the diagnostics and I get error code #65
which is a SCSI error.  I try to use builddisk and I get the message that
it can't find the device.   I tried an external drive and the same thing
happened.

Always the same thing scsimodes can't find the device.

If I have the Wren internally I get  ec #65 but if I have a Quantum I
don't get the error code on boot.

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.

For the record I'm using a NeXT 50 pin SCSI cable internally and a generic
SCSI cable externally.

All this happens no matter what I have the device as (0-7).  I know that
#7 is reserved for the mother board but I tried this just to see if I could
get a conflict on the bus - nothing.

Help!!!  Help!!!   Help!!!  Help!!!  I NEED HELP!!!!!!!!!!

                         KeNT
--
/*  -The opinions expressed are my own, not my employers.    */
/*      For I can only express my own opinions.              */
/*                                                           */
/*   Kent L. Shephard  : email - kls30@DUTS.ccc.amdahl.com   */


Brought to you by Super Global Mega Corp .com