On 06/13/2014 12:58 PM, Fred Cisin wrote:
Well, my personal preference is 8 x 1024, or 15 x 512
(which makes life a
little simpler for interchange with systems that require extra work to
switch out of 512 byte sectors).
What, not 48x128? (There were systems that did that).
And sectors/size per track completely avoids how the data is logically
organized among those sectors.
Sector interleave (i.e. physical->logical equivalence), cylinder/side
ordering (e.g., one side then the other in reverse) have provided me
with endless hours of amusement. Oddball cylinder and side skewing are
fun in particular.
Where does the directory go? (e.g. the middle of the disk) How do you
order allocation units from there? (e.g. first, cylinders above the
directory, then cylinders below--or alternating above/below)
How about the boot tracks? If your controller can handle unity
interleave, why not speed up the cold boot process by avoiding any
interleave on those tracks?
How about your allocation unit size (e.g. absurdly large)? Directory
size (e.g. absurdly small)? Full or half-full directory entries (in an
attempt to keep 128 128-byte logical sectors as the limit for a single
directory entry).
Figuring the number of sectors and size of those on a track is only a
very small beginning.
CP/M in practice distinguished itself by the incredible number of disk
organization variations.
--Chuck