🚀 go-pugleaf

henry@zoo.toronto.edu (Henry Spencer) writes:

>In article <86715@unix.cis.pitt.edu> kwgst@unix.cis.pitt.edu (Filip Gieszczykiewicz) writes:
>>	Now, someone told me that the SASI interface is a relative
>>	of SCSI.

>SASI is SCSI's grizzled old ancestor.  They are nominally still interoperable,
>last I heard.

Uh, not really.  In SASI-land, all you had to do in order to access
the remote device was to assert its SASI ID during the selection phase.
In SCSI-land, you need to assert both the controller's SCSI ID and the
remote device's SCSI ID on the bus during the selection phase.

>> Does anyone know if I can hook up a hard drive
>>	to the ST506 side and the SASI side to a Macintosh and
>>	expect this to work? 

>Maybe.  There is no *fundamental* reason for this to be unworkable, but much
>depends on details.  (E.g., is the Mac expecting a more modern controller
>and trying to exploit post-SASI features?)

More to the point: the mac is expecting a few basic commands to be
available so it can download a proper driver from the first N blocks of
the hard drive.  Where are you going to get a controller for it, even
if the mac can operate the SASI device?  Unless you're really shy of
dollars, I'd just go for a 20meg hard drive and build one of the many
"cheep scsi drives" projects that appear in the magazines from time to
time.

--
Andrew Scott Beals
abeals@autodesk.com