Boy am I embarassed. It turned out to be a SCSI terminater (lack of), but
I learned more about this drive and that is alway a good thing.
First of all (thanks to massie@nfka.norfolk.syr.ge.com (Gerry Massie)) I
learned that Archive has been purchased by Connor Peripherals, and one
can get info on these drives from Connor's fax-back system.
Connor Peripheral's fax back system Tel 1-800-426-6637 (1,1,1)
Second, Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]
has provided a good summary of the info available from the fax back system
(attached below).
Third, I have included a copy of my original question at the end of this
message.
Thanks to everyone who replied,
Don
---------- begin enclosure
Viper 2060S and 2150S hardware setup
Hardware setup amongst the 9 sets of jumpers includes:
SCSI ID: 3 sets of jumpers
Serial: this should NOT be set
Diagnostic: this should NOT be set
Parity Enable: setting depends on your interface; either EVERYTHING
or NOTHING on the bus should be checking parity.
Buffer Disc: 3 sets of jumpers select 2, 4, 6, 8, 12, 16, 24 and
32K buffer sizes. Factory default is 16K. This is
the number of bytes transferred over the bus in a
single operation. A mininum of 16K is required for
the SCSI "COPY" command.
Where to find all this at the back of the drive:
[OOOO] TTTTTTTT TTTTTTTT TTTTTTTT
[JJ] SSSSSSSSSSSSSSSSSSSSSSSSSS
Where: [OOOO] is the power connector
[JJ] is the jumper block
TTTTTT are the three 8-pin terminators
SSSSSS is the 25x2 SCSI connector
The jumper block looks like this (in the orientation as above):
[ SERIAL ] [ CF2 ] [ ID2 ]
[ DIAG. ] [ CF1 ] [ ID1 ]
[ PARITY ] [ CF0 ] [ ID0 ]
SERIAL: no jumper
DIAG: no jumper
PARITY: jumper to enable
============================= BUFFER ==============================
SIZE: 2K 4K 6K 8K 12K 16K 24K 32K
CF2: o o o o o o o o [o=o] [o=o] [o=o] [o=o]
CF1: o o o o [o=o] [o=o] o o o o [o=o] [o=o]
CF0: o o [o=o] o o [o=o] o o [o=o] o o [o=o]
============================= SCSI ID =============================
ID: 0 1 2 3 4 5 6 7
ID2: o o o o o o o o [o=o] [o=o] [o=o] [o=o]
ID1: o o o o [o=o] [o=o] o o o o [o=o] [o=o]
ID0: o o [o=o] o o [o=o] o o [o=o] o o [o=o]
===================================================================
---------- end enclosure
----- Begin Included Message -----
>From tomf@amgen.com Thu Oct 20 19:36:26 1994
Date: Thu, 20 Oct 1994 16:35:23 +0800
From: tomf@amgen.com (Tom Friscia)
To: don@mars.dgrc.doc.ca
Subject: Re: QIC 150 tape drive
X-Sun-Charset: US-ASCII
Content-Length: 1418
It sounds more like a problem with SCSI
or did you use
boot -r
to reconfigure the system to recognize the drive
Tom
> From sun-managers-relay@ra.mcs.anl.gov Thu Oct 20 15:56 PDT 1994
> Sender: sun-managers-relay@ra.mcs.anl.gov
> Reply-To: don@mars.dgrc.doc.ca (Donald McLachlan)
> Followup-To: junk
> To: sun-managers@delta.eecs.nwu.edu
> Subject: QIC 150 tape drive
> Content-Type: text
> Content-Length: 902
> X-Lines: 31
>
> I have an Archive QIC 150 tape drive that I have used on a SunOS4.1.x
> but is non-reponsive when connected to an Axil 311 (SS10 clone) running
> Solaris 2.3.
>
> I am guessing that it is a termination problem. Aside from the ID
> jumpers which are self evident, does anyone know what the jumpers
> do/should be set to?
>
> On the back of the drive (right under the power connector there is a
> small area of jumper blocks. The board silk screening underneath the
> jumper blocks is labeled ...
>
> back of PCB
>
> --------------------------------------------------------
> | A| PEN | CF0 | ID0 |
> side | |-----------------|
> of | B| DIA | CF1 | ID1 |
> PCB | |-----------------|
> | C| | CF2 | ID2 |
> | --------------------|
> |A| X X | X X | X X |
> | |-----|-----|-----|
> |B| X X | X X | X X |
> | |-----|-----|-----|
> |C| X X | X X | X X |
> | ------------------|
> | R T (BOTTOM OF PCB)
> | X X
> | D D
> |
>
----- End Included Message -----
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:13 CDT