ZX Interface 1: Difference between revisions

Jump to navigation Jump to search
Line 126: Line 126:
Each sector consists of two files, each similar. There is the Sector Header, which is a 15 byte file record, or the data record recorded after the sector header, which is 528 bytes, including one "sacrificial byte" on the D1 data line, which does not contribute to the data stored, though could be modified into a high-order byte checksum in the future to improve data integrity on older cartridges.
Each sector consists of two files, each similar. There is the Sector Header, which is a 15 byte file record, or the data record recorded after the sector header, which is 528 bytes, including one "sacrificial byte" on the D1 data line, which does not contribute to the data stored, though could be modified into a high-order byte checksum in the future to improve data integrity on older cartridges.


[https://sinclair.wiki.zxnet.co.uk/w/images/thumb/9/98/Logic_Analysis_of_sector_Header_and_Data_sections_with_gaps.png/800px-Logic_Analysis_of_sector_Header_and_Data_sections_with_gaps.png]
[[File:Logic_Analysis_of_sector_Header_and_Data_sections_with_gaps.png]]
[[File:Logic_Analysis_of_sector_Header_and_Data_sections,_with_gaps.png]]


Each of these structures is similar, apart from length, and can be examined independently.
Each of these structures is similar, apart from length, and can be examined independently. From this image, it can be seen that the ERASE line turns on just before the R/W line begins writing the sector. In this case, the Sector Header has been read, and it has been determined previously when the sector map was constructed that this sector can be written to. The ERASE is activated, and then the R/W is activated (active low ) just prior to writing data.


== External links ==
== External links ==
34

edits

Navigation menu