|Author:||Pete Rittwage (registered user: 558 posts )|
|Date:||Mon, Mar 07th, 2011 @ 20:51 ( . )|
Syncs are only "read" by counting cycles during the sync. The drive goes into "free fall" from the time the 10th bit occurs and the end of a sync mark. We aren't reading real $FF bytes during this time, just inserting them into the stream according to density and cycle counting. For that reason, we also run into motor speed, belt drive flutter, etc. That's probably why it measures it twice during protection check.
So it is possible that the sync length is wrong, and very much probably is. Arnd Menge has tweaked this code to be much closer now- it did lose a bit here and there before. I will reread an original and see how different it is. Also, VICE is inaccurate in sync counting as well, so what works on a real drive may be off in emulation.
--* V-Max secondary checks
3/08/2011 @ 02:19--Lord Crass
--- 0 Users Online --- 0 Recent Unique Posters