OK. Here’s the dealio:
I was using the MFMeditor portion of DiskMonTools on the amiga to read a raw sector. Now the darn editor won’t save to disk, so I can’t COMPARE the raw data which I’d love to do. I’m half contemplating taking some digital pictures and OCR’ing the fuqrs just so I can get some data to compare.
This is exactly one track’s, track 0, according to DiskMonTools. Don’t ask me why its not 13800, or 11xxx, etc.
The point right now isn’t so much that I’m getting one track perfectly delimited, its that what comes out of the drive is being read properly by my solution.
DiskMonTools says it’s reading 16200 bytes. My project is reading a filesize of 15892 consistently. I don’t think the data output is exactly the same each time, and that’s a problem Im going to have to address eventually.
I would rather be reading 16200, but hell i’d rather be under than over. This means my SX routines are missing some data someplace, if I had to bet, its an Interrupt problem, where a regular RTCC rollover event is happening during an edge event.
Here’s the link to the sampled file.
I think the sector header isn’t at the beginning of the file because I think the amiga starts streaming data immediately out of the drive (well, after it spins up) without regard to the position within the track.