|Author:||Lord Crass (guest: search)|
|Date:||Mon, Apr 11th, 2011 @ 12:26 ( . )|
Correction to my last post: Just because the data is showing up at the start of the track in the image does not necessarily indicate a good read. I forgot that Pete's protection-handler routine for V-Max track 20 will look for bit-shifted versions of the $5A header and align the start-of-track based on that. The track could still have been read in a manner that put data on both sides of the illegal GCR and caused a shift half-way through. So even if you bit-shift the whole track in the image after this, the loader's checksum will fail since some of the data was bad.
Also, a header-search feature ensures that the data comes in framed exactly how you want it, you wouldn't have to bit-shift an entire track after that just to get it to work in an emulator.
On a side note, getting a good read of the V-Max version on Gauntlet: The Deeper Dungeons (Mindscape NTSC) is an exercise in patience right now. There's bad GCR all over the place on almost every track. So the image loads for a while, then stalls on some track load looking for the $64 byte forever.
--- 0 Users Online --- 0 Recent Unique Posters