'V-Max secondary checks'
Author:Lord Crass (guest: search)
Date: Thu, Apr 28th, 2011 @ 02:41 ( . )

The 17th sync mark was one byte too long. However, something else happened because after I fixed that, the sector checksum kept failing and it would load the track over and over.

This track has a different byte for the end of data block which also starts the next sync. It's a $7F. However, the protection passes if you use 7F FF FF FF FF as that header block sync mark and AF FF FF FF FF FF for the data block sync mark, so that's what I did since it meant changing fewer entries.

I've attached a fixed up image.


REPLY: [With No Quote] --- [With Quoted Text]

--* V-Max secondary checks
4/28/2011 @ 03:03--Lord Crass
4/28/2011 @ 10:36----Fungus
4/28/2011 @ 11:30------Lord Crass
5/12/2011 @ 23:46--------Fungus
5/13/2011 @ 16:22----------Fungus
1/17/2013 @ 01:40------------hyper active
10/22/2013 @ 01:16--------------Hyperactive
12/21/2017 @ 18:00----------------hyper active
12/26/2017 @ 00:32------------------hyper active
5/23/2018 @ 13:45------------------Pete Rittwage

--- 0 Users Online --- 0 Recent Unique Posters

Q82=1669948765 - Threads: / 1669948765