Well, I'm already disappointed, I can't understand how the IMD format could keep the 1..20 sector numbering working on the alternate disk sides.
The Interleave option is probably not mandatory, I may be wrong, but it looks like this system was able to read disks with or without interleaved sectors. The read error happens at sector #11:
Code: Select all
static disc_spec zorba_spec = {
.name = "Zorba",
.disk_mode = MFM250,
.sectors_per_track = 10,
.tracks = 40,
.sides = 2,
.sector_size = 512,
.gap3_length = 0x2a,
.filler_byte = 0xe5,
.boottracks = 2,
.directory_entries = 64,
.extent_size = 2048,
.byte_size_extents = 1,
.first_sector_offset = 1,
.alternate_sides = 1,
.has_skew = 1,
.skew_tab = { 0,5,1,6,2,7,3,8,4,9,10,15,11,16,12,17,13,18,14,19}
//.skew_tab = { 0,5,1,6,2,7,3,8,4,9 }
};
Code: Select all
TD 1.5 5.25-96 LD MFM D-step, 2 sides ADV 6/04/2001 11:06:35
cpm1 from 360 to 1.2
80 tracks, 800 sectors converted.
------------------------
IMD TD 1.5 5.25-96 LD MFM D-step, 2 sides ADV 6/04/2001 11:06:35
------------------------
0/0 250 kbps DD 10x512
1 6 2 7 3 8 4 9 5 10
D D D D D D D D D D
0/1 11 16 12 17 13 18 14 19 15 20
HD: 0 0 0 0 0 0 0 0 0 0
D D D D D D D D D D
1/0 1 6 2 7 3 8 4 9 5 10
D D D D D D DE5 D D26 D
1/1 11 16 12 17 13 18 14 19 15 20
HD: 0 0 0 0 0 0 0 0 0 0
D D D D D D D D D D
2/0 1 6 2 7 3 8 4 9 5 10
D D D D D D D D D D
2/1 11 16 12 17 13 18 14 19 15 20
(...)
I'm just curious on whether appmake is able to deal with it in "dsk", "d88" or "imd" mode.
EDIT: the mentioned KayComp II format refers to the KayPro II, there's an interesting story about the mess happening behind the scenes at the product launch