[Coco] DSKINI glitch while using physical drive 1 and SDC DOS 1.5
Arthur Flexser
flexser at fiu.edu
Sun Sep 3 18:16:51 EDT 2017
I'm guessing the preferred solution for the DSKINI problem in that case
would be to use a more conservative sector interleave in the verification
stage, at a sacrifice of a bit of speed in that stage.
Art
On Sun, Sep 3, 2017 at 5:37 PM, Darren A <mechacoco at gmail.com> wrote:
> On Sun, Sep 3, 2017 at 3:08 PM, Arthur Flexser wrote:
>
> >
> > I used the speed detection method within DSKCON of counting how many
> > horizontal interrupts occurred while a short loop executed. I can send
> > this very short routine if you like.
> >
>
>
> Thanks Art, but SDC-DOS already has code in place to detect the current CPU
> speed. I use it for the CoCo3 DriveWire client to determine if normal
> speed needs to be restored after executing the 115 kbps bit-banger code at
> double speed.
>
> I would prefer not having to rely on double-speed to solve the DSKINI
> problem because it also needs to work on a CoCo 1 and 2. It’s possible to
> run SDC-DOS in Map Type 1 (All RAM) on a 64K machine, in which case the
> address-dependent speed mode has no effect.
>
>
> - Darren
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
More information about the Coco
mailing list