Re: reading data from G64 track

From: Pete Rittwage <peter_at_rittwage.com>
Date: Thu, 30 May 2013 13:10:05 -0400 (EDT)
Message-ID: <56370.10.2.0.31.1369933805.squirrel@rittwage.com>
Yes, each track can be considered a closed loop of data, just like a real
disk.  It is usually good practice to have the track splice occur at this
loop as it was written on the floppy, but that is not always possible to
determine.

-Pete


On Thu, May 30, 2013 12:52 pm, silverdr@wfmh.org.pl wrote:
> One more question regarding the G64 format (the answer could also possibly
> find its way to the doc ;-)
>
> When scanning G64's track data for whatever (SYNC, header, payload, ..)
> can it happen that the data "wraps-around" the buffer?
>
> A theoretical example: sector was found 128 bytes before the end of the
> G64 track data. While its headers and part of the payload fits still
> there, what happens with the remaining part of the payload? Will I find it
> at the beginning of the buffer?
>
> Or another example: I try to find next SYNC mark. Found three consecutive
> bits set in the last byte of the track data. Should I check for the
> remaining seven in the first byte of the track data?
>
> --
> SD!
>        Message was sent through the cbm-hackers mailing list
>


       Message was sent through the cbm-hackers mailing list
Received on 2013-05-30 18:01:52

Archive generated by hypermail 2.2.0.