>Oh, I'm sorry, I should have responded... I found the problem...
>the problem is really that st_interpret_sense is getting into the
>game for the check condition on the initial test unit ready...

No problem -- this stuff hasn't caused me any problems (that I'm aware
of) -- I was just responding to be "helpful".

[...]

>Michael- that second check condition on a write- that's really something
>busted in the drive f/w. That particular drive is a IBM branded Archive
>DAT drive, but that's a Vendor Unique ASC/ASCQ (or garbage- the distinction
>is sometimes small) so it's hard to know what to do when this happens.
>(got a manual for this puppy?)

Well, I have the owner's manual, though that's rather "light" on
firmware matters... :-)

As I said, the "clean-tape" light was on after I checked the drive
after a backup.  So, it's possible that maybe it was returning a tape
soft error or something?

The drive hasn't given me any problems under either NT or NetBSD, so I
don't think there's anything "wrong" with it.  But, only time will
tell...

-----------------------------------------------------------------------------
  Michael L. VanLoon                           michaelv@MindBender.serv.net
      Contract software development for Windows NT, Windows 95 and Unix.
             Windows NT and Unix server development in C++ and C.

        --<  Free your mind and your machine -- NetBSD free un*x  >--
    NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3,
        Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32...
    NetBSD ports in progress: PICA, others...
-----------------------------------------------------------------------------