home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.hardware
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!sgiblab!sgigate!odin!sgihub!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Subject: Re: Sun "Archive Python" Tape Drive [ Viper, not Python ? ]
- Message-ID: <pgfamfs@zuni.esd.sgi.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- References: <1992Sep2.023035.11992@ee.gatech.edu>
- Date: Sun, 6 Sep 92 07:33:00 GMT
- Lines: 17
-
- In <1992Sep2.023035.11992@ee.gatech.edu> lockhart@eecom.gatech.edu (John B. Lockhart) writes:
-
- | My boss had a few dozen Sun 150 meg tape drives lying about gathering dust,
- | so I thought I'd snarf one and use it to backup my 'station with. Wrong.
- |
- | I connected it on it's lonesome (as SCSI id 4) to the NeXT, with a terminator,
- | and get I/O errors on all read/writes with gnutar.
-
- The Python is the DAT drive. It *does* support variable block size.
- The Viper is the QIC drive (and does not support variable block size).
-
- Others have covered the mode issues; assuming you actually have the
- Viper.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-