Closed pelrun closed 2 years ago
The extended dsk specification says the track size table in the DIB should be uint16_t, but I've now seen multiple images where the table is uint8_t instead and storing the high byte only.
Looks like I already treat the table as uint8_t; that probably means the spec is wrong.
The copy of the spec on cpcwiki contains the high-byte-only definition, so it's probably what everyone else is using.
The extended dsk specification says the track size table in the DIB should be uint16_t, but I've now seen multiple images where the table is uint8_t instead and storing the high byte only.