On Tuesday 09 August 2005 14:41, Julian Wolfe wrote:
--snip--
Here's what happens when various commands are
issued:
- st iput filename.ext 512 - tape goes back and forth then stops
with a media error
- st write - tape goes back and forth and then goes back to a dos
prompt. I try to do 'st rew' after this, but then it does what looks like
the 'write' operation
- st weof - "on line" light blinks continuously. This doesn't
always happen, sometimes it does the 'st write' behavior.
So, thus far, I have no boot tapes. Can anyone help me out with this?
Julian,
I've successfully used ST to read and create tapes on some drives...
Typically, I use a SCSI HP 88780 (800/1600/6250) tape drive, a SCSI Iomega ZIP
drive and an IDE CDROM. I happen to be using a BUSLOGIC SCSI controller -
but a similar Adaptec controller with the appropriate driver should work as
well.
OS: DOS 6.22
My config.sys is:
device=c:\dos\himem.sys
dos=high
files=40
device=c:\dos\ansi.sys
device=c:\buslogic\btdosm.sys /d
device=c:\cdrom\ide.sys /d:idecd000 /udma /q
My autoexec.bat is:
@echo off
prompt $p$g
path c:\dos; --- (lots of stuff)
mscdex /d:idecd000 /l:e
I have found ST to work in this configuration very reliably with the various
HP tape drives.
However, when I've tried to use the same configuration with a DEC TK50Z I have
found it will read TK50 tapes - but has similar issues writing and
controlling tapes (BSF, FSF, etc.) that you have experienced with your tape
drive.
My guess is that the HP drives meet SCSI specs better (they are SCSI-2) -
while the DEC TK50 is SCSI-1 (at best).
It could also be a nasty timing issue - but I've not looked at and debugged
the ST source to see precisely what the problem is...
Cheers,
Lyle
--
Lyle Bickley
Bickley Consulting West Inc.
Mountain View, CA
http://bickleywest.com
"Black holes are where God is dividing by zero"