3 Apr
1999
3 Apr
'99
2:32 p.m.
Yesterday four geeks (including myself) had tried to
convince a HP 88780
9-track SCSI drive (cleverly disguised as Tandem 5160) to accept 6250 bpi
tapes. It works OK at 1600 bpi, but refuses to admit it knows about 6250:
"mt setdensity 3" on a Linux box results in "Incompatible media
installed"
error (when the tape written at 6250 bpi is loaded.)
You shouldn't have to do the setdensity operation; the drive ought
to be able to read the 6250 BPI drive in any event. What happens
when you try to read the 6250 BPI tape?
Historically, the SCSI commands for selecting tape drive density have
been either ignored or misinterpreted by everyone throughout the years.
--
Tim Shoppa Email: shoppa(a)trailing-edge.com
Trailing Edge Technology WWW: http://www.trailing-edge.com/
7328 Bradley Blvd Voice: 301-767-5917
Bethesda, MD, USA 20817 Fax: 301-767-5927
3 Apr
3 Apr
4:59 p.m.
On Sat, Apr 03, 1999 at 03:32:07PM -0500, CLASSICCMP(a)trailing-edge.com wrote:
When tape is loaded, both "1600" and "6250" are highlighted on front
panel.
"mt status" then reports current density of 1600 bpi. Attempts to set any
density other than 2 fail with sense key "Illegal Request" and additional
sense 0x3000 "Incompatible media installed". Attempts to read data fail
with sense key "Medium error" and same additional sense.
--
Sergey Svishchev -- svs{at}ropnet{dot}ru
Yesterday four
geeks (including myself) had tried to convince a HP 88780
9-track SCSI drive (cleverly disguised as Tandem 5160) to accept 6250 bpi
tapes. It works OK at 1600 bpi, but refuses to admit it knows about 6250:
"mt setdensity 3" on a Linux box results in "Incompatible media
installed"
error (when the tape written at 6250 bpi is loaded.)
You shouldn't have to do the setdensity operation; the drive ought
to be able to read the 6250 BPI drive in any event. What happens
when you try to read the 6250 BPI tape?
9401
days inactive
9401
days old
1 comments
2 participants
participants (2)
-
CLASSICCMP＠trailing-edge.com -
svs＠ropnet.ru