| Author: | Lord Crass (guest: search) |
|---|---|---|
| Date: | Sat, Mar 03rd, 2012 @ 18:03 ( . ) |
I took a look at a g64 of Bounty Bob today, but can't get it to read track 1.5 in Vice. It's looking for 5x$77 GCR bytes after a sync mark as the start of sector, but it never finds them, even though they show up in the image file. It keeps finding $52 or $75 after the sync mark, even if I remove those from track with a hex editor. Does anyone know if Vice handles half-tracks properly? It loads further in HOXS, up to 3 blocks remaining, then dies with a checksum error. They really pulled out all the stops for this protection: If the disk isn't write protected, or you have a second drive attached, you'll get a checksum error right away. The sectors are non-standard GCR, extra long, and without standard header. GCR decoding is done on the c64 instead of in the drive. Density is non-standard, and changes when you move to the half-track. I wonder if it was the game's author, Bill Hogue, who wrote this protection? |
3/04/2012 @ 11:07----Pete Rittwage 3/04/2012 @ 23:55--------Pete Rittwage 3/09/2012 @ 21:28------------Pete Rittwage 4/09/2012 @ 20:38----------------Pete Rittwage 4/10/2012 @ 21:29--------------------Pete Rittwage --- 0 Users Online --- 0 Recent Unique Posters |