Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!julius.cs.uiuc.edu!psuvax1!psuvm!psuecl!d6b
From: d6b@psuecl.bitnet
Newsgroups: comp.sys.amiga.tech
Subject: Re: Bug in Trackdisk.device?
Message-ID: <20544.26e39e69@psuecl.bitnet>
Date: 4 Sep 90 16:30:31 GMT
References: <6506@sugar.hackercorp.com>
Organization: Engineering Computer Lab, Pennsylvania State University
Lines: 25

In article <6506@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
> Is the bug in 1.2 and 1.3 trackdisk.device that requires a patch in CrossDos
> and MSH: also in 2.0?
> --
> Peter da Silva.   `-_-'
> <peter@sugar.hackercorp.com>.

_The_ bug? That implies that there's only one bug. :-)

What you might be thinking of is the hardware sync feature. All versions
of trackdisk up to and including 1.3 completely ignored it (hopefully
someone at Commodore can explain why). Anyway, the patches that you need
for CrossDOS 4.0+ (I don't know about MSH) simply invoke the hardware
sync feature. Not surprisingly, this corresponds to the 2.0 version of
trackdisk (so the answer to your question is "yes", I guess).
Note:This discussion ignores the real bugs and deficiencies of trackdisk,
which are fixed by TrackSalve.

One thing I don't like about the 2.0 trackdisk (and I don't know a lot
about it, as I haven't yet disassembled it :-)) is that, although it
does let you use the hw sync feature (via RawRead), it doesn't let
you specify the sync word; it always places a $4489 in the register.
Very annoying...

-- Dan Babcock