On Sun, 6 Oct 1996, Jason Thorpe wrote:

> Ah, this is the problem ... Pay special attention to this ... it didn't
> assign a driver to the device, because it doesn't report itself as
> a sequential access device.
> 
> Also, not the ILLEGAL REQUEST errors from the tape ... these happen
> when the SCSI layer is asking about devices at other luns on the
> target... At the very least, it needs a SDEV_NOLUNS quirk...

Nuts. Is this something that can be tinkered with in the source code, or
is it a problem with the way the drive was designed and therefore will
never work under NetBSD?


> You say MacOS only works with it pre-7.x ... this could indicate that it
> doesn't use standard SCSI tape commands... You might consider contacting
> the vendor and getting technical documentation suitable for writing
> a device driver for the drive... with that, you could probably massage
> the SCSI tape driver into working fairly easily.

It's an Apple drive, and Apple wrote the software way back when. In the
Apple Tech Info Lib (at Apple's support web site), they recommend using a
3rd party software package. The hardware is fully Sys 7 compatible. There
was a reference to A/UX and it seems that the drive works just fine with
that. 


> Hope this helps...

Yes, quite a bit. Thanks...


---------------------------------------------------------------------------
Greg Putrich - Internet: gregp@primenet.com                       [skeezix]
Public Key 27E97EBD = 62 0E B9 A2 45 D2 64 AC 8A B4 6D 9D 5B 23 90 1F

               An fsck a day keeps the core dump away