Re: FB-354 drive incompatibility

From: smf <smf_at_null.net>
Date: Fri, 22 Apr 2016 16:25:53 +0100
Message-ID: <75a3198a-9531-f404-3c35-f494c1606523@null.net>
On 22/04/2016 15:47, silverdr@wfmh.org.pl wrote:
>
> That would be then even easier than I thought. But weren't there two types/approaches to that? One that worked only on KS2+ and the other that worked on earlier ones too. I /think/ one of them treated the drive differently than the other.
>

Trackdisk.device in kickstart 2 and later supported noclick by setting a 
flag, while earlier versions needed code patches. How they work 
physically is the same.

On 20/04/2016 12:10, MichaƂ Pleban wrote:
> Obviously the FB-354B drive knows whether there is disk inserted or not,
> but does not expose this information outside.

It shouldn't be too hard to find the sensor and trace where it goes and 
find a place to tap into it.


       Message was sent through the cbm-hackers mailing list
Received on 2016-04-22 16:00:17

Archive generated by hypermail 2.2.0.