home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.periphs.scsi
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!gatech!usenet.ins.cwru.edu!agate!overload.lbl.gov!dog.ee.lbl.gov!hellgate.utah.edu!csn!tware!bash
- From: bash@tware.com (Paul Bash)
- Subject: Archive Python DAT question (problem?)
- Message-ID: <1993Jan3.201029.837@tware.com>
- Organization: Techware Design, Boulder, Colorado
- Date: Sun, 3 Jan 1993 20:10:29 GMT
- Lines: 27
-
-
- I just bought one of these drives and have a question. It appears that
- unless a tape is inserted in the drive at boot time (on a 486-33 running
- MSDOS), the controller (an Adaptec 1542B) will not recognize that the
- unit exists. I verified this using Roy's SCSICNTL program and having it
- list the available devices. If a tape is in the drive at boot time,
- SCSICNTL lists it as an available device. If no tape is in the drive,
- SCSICNTL doesn't "see" it.
-
- This is relatively easy to work around by just leaving a tape in the
- unit at all times. My questions are:
-
- 1) Is this a normal characteristic of the Archive Python?
-
- 2) If so, will this cause problems with excess head wear, etc? In
- other words, doesn't the head spin on a helical scan device and
- wouldn't constant contact with a tape cause premature wear on
- the, most importantly, read/write head but also the tape?
-
- I understand that if both of the above are true, I could just stick a
- tape in the drive when I boot and remove it later, but I tend to
- forget little details like this. If 1) above is true, this seems like
- an unfortunate design decision no matter whether 2) is true or not.
-
- --
- Paul Bash Techware Design
- bash@tware.com Boulder, CO U.S.A.
-