ok, got the TK50 hooked up to my LX, and got it booted.  but the TK50 does a
very poor job of identifying itself to NetBSD (and the ROM for that matter.

ok probe-scsi
Target 0 
  Unit 0   Disk     CONNER  CFP2107S  2.14GB5767
Target 3 
  Unit 0   Removable Tape     ARCHIVE VIPER 150  21531-003    SUN-03.00.00
Target 4 
  Unit 0   Removable Tape     ARCHIVE Python 28454-XXX4ASB
Target 5 
  Unit 0   Removable Tape     DEC     TLZ04 1989(C)DEC1615030E
Target 6 
  Unit 0   Removable Tape  Qualifier  50 

st0 at scsibus0 target 3 lun 0: <ARCHIVE, VIPER 150  21531, -003> SCSI1 1/sequential removable
st0: rogue, drive empty
probe(esp0:4:0): max sync rate 5.00MB/s
st1 at scsibus0 target 4 lun 0: <ARCHIVE, Python 28454-XXX, 4ASB> SCSI2 1/sequential removable
st1: density code 140, 512-byte blocks, write-enabled
st2 at scsibus0 target 5 lun 0: <DEC, TLZ04 1989(C)DEC, 1615> SCSI2 1/sequential removable
st2: density code 0, 1319824-byte blocks, write-protected
st3 at scsibus0 target 6 lun 0: <, , > SCSI1 1/sequential removable
st3: rogue, drive empty                                            

  Unit 0   Removable Tape  Qualifier  50 
st3 at scsibus0 target 6 lun 0: <, , > SCSI1 1/sequential removable

is this normal for a TK50? or does mine just have wacked roms?

thanks,

-brian