Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!sgi!markb@denali.sgi.com
From: markb@denali.sgi.com (Mark Bradley)
Newsgroups: comp.sys.sgi
Subject: Re: Exabyte drive (Non sgi supplied)
Summary: Non-SGI Exabytes supported.
Message-ID: <52832@sgi.sgi.com>
Date: 6 Mar 90 18:21:58 GMT
References: <7016@ubc-cs.UUCP>
Sender: markb@denali.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 23

In article <7016@ubc-cs.UUCP>, buchanan@cs.ubc.ca (John Buchanan) writes:
> My guess is that I simply set it up as a quarter inch drive and let the 
> SCSI driver handle the rest.  This is probably incorrect, but it seems like
> a good place to start.  Does any one have any better advise?
> 
1st, be running 3.2 s/w release.  Next, address the drive as 6, preferably.
Next, look in /dev/mt.  There will be several devices with 6 as the address.
there are nr, ns, and v and combinations thereof.  All will talk to the
Exabyte drive...   There are *some* drives that give back a vendor specific
string on an inquiry, and there is some problem talking to the drive if 
that is so, as the s/w has no way of `knowing' what the heck it is.

							markb


--
Mark Bradley				"Faster, faster, until the thrill of
I/O Subsystems				 speed overcomes the fear of death."
Silicon Graphics Computer Systems
Mountain View, CA 94039-7311		     ---Hunter S. Thompson

 Disclaimer:  Anything I say is my opinion.  If someone else wants to use it, 
             it will cost...