Re: D9060 Hard drive

It was the line right in the middle of the cable.

On 4/2/2013 12:12 PM, Ethan Dicks wrote:
> On Tue, Apr 2, 2013 at 11:51 AM, Ted<ejohnson.ed@gmail.com>  wrote:
>> I got the bright idea of just bypassing the MFM to SCSI board and installing
>> a SCSI drive directly to the DOS board. The cable started melting
>> immediately. I have ordered a new cable and hope I did not fry the DOS
>> board.
> You probably had both ends of the cable trying to provide TERMPWR.
>
> What part of the cable melted?  (what SCSI pins?)
>
> There are small differences between the packet commands for SASI
> and SCSI-1.  There are plenty of differences between SASI and SCSI-2.
>
>> I did try plugging in a SCSI connector to connect the drive an
>> Winchester2SCSI board. Windows 7  could not recognize it.
> That is entirely unsurprising.  Among other things that older
> bridge cards do not support (even SCSI-1) is the IDENT
> packet that pretty  much all modern systems use to request
> the drive self-report its geometry.  Back in the old days, you
> had to tell the OS how large the disk was and it trusted you.
> Later, SCSI (and IDE) devices got smart enough that the OS
> could ask the drive and not force the human to know the
> geometry.
>
> Even the modern Linux drivers require IDENT to be there.
>
> Old UNIX (4.1BSD for example) and non-mainstream OSes
> like AmigaDOS let you/make you specify the drive geometry
> and could be used (if the command packets sent from the
> OS driver are compatible with what the drive supports) to
> raw-read the drive.
>
> Of course, there's one other wrinkle... the drive in the
> D9060/D9090 uses 256 byte sectors, *not* 512 byte
> sectors, which commonly confounds modern OS drivers.
>
> -ethan
>
>         Message was sent through the cbm-hackers mailing list


       Message was sent through the cbm-hackers mailing list