|Author:||Nate (guest: search)|
|Date:||Thu, Apr 14th, 2011 @ 17:29 ( . )|
That's what I was wondering -- how you guys determined which data was needed when the density used to read the image was wrong. I think you are just disassembling the protection code and looking for the pattern it is searching for and what it sets the density to before doing so, right?
I'll make it easy to specify density for ranges of bytes in a track. This will get written out to the g64 correctly (using the extended speed map) but will be lost if writing a .nib file. This way you can read out the track multiple times with nibread and then piece back together each track by just putting in the text file something like:
(2, xx xx xx) (3, yy yy)
BTW, does nibwrite or VICE support the g64 extended speed map? It doesn't seem like it.
4/15/2011 @ 23:10--J Achernar
--- 0 Users Online --- 0 Recent Unique Posters