'PirateSlayer'
Author:Pete Rittwage (registered user: 558 posts )
Date: Thu, Jun 28th, 2012 @ 08:31 ( . )

It will have an expected track size based on the density detected.

/* To calculate the bytes per rotation:

4,000,000 * 60
b/minute = ------------------------------------------------ = x bytes/minute
speed_zone_divisor * 8bits

4,000,000 is the base clock frequency divided by 4.
8 is the number of bits per byte.
60 gets us to a minute of data, which we can then divide by RPM to get our numbers.

speed zone divisors are 13, 14, 15, 16 for densities 3, 2, 1, 0 respectively
*/

#define DENSITY3 2307692.308 // bytes per minute
#define DENSITY2 2142857.143
#define DENSITY1 2000000.000
#define DENSITY0 1875000.000

Further divide this by the RPM (300) to get the number of bytes on a track that "should" be there.

Now, if the disks were not written with a 1541, this will be inaccurate. It's already known that a trace duplicator will be a slightly different bitcell size that a 1541, but it's close.

Also, we cannot always tell where a custom tracks starts and ends when written on a 1541, though. Well, at least I can't- maybe there are other methods to do so I haven't explored.


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

Replies:
--* PirateSlayer
6/28/2012 @ 08:40--Displacer
6/28/2012 @ 11:16----Displacer
6/28/2012 @ 15:48------LordCrass
6/28/2012 @ 16:05--------Displacer
6/28/2012 @ 20:38----------LordCrass
6/28/2012 @ 21:49------------Displacer
7/01/2012 @ 11:31--------------Displacer
7/01/2012 @ 12:51----------------Displacer
8/18/2012 @ 06:59------------------Fungus

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

Q53=1657010750 - Threads: / 1657010750