meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
adv:hardsectorconf [2022/07/23 21:20] – diskblitzadv:hardsectorconf [2022/07/26 21:09] – diskblitz
Line 1: Line 1:
 ====== Adding Support for a Hard Sectored Disk Format ====== ====== Adding Support for a Hard Sectored Disk Format ======
  
 +As of Applesauce 1.66, it is possible for users to be able to add their own format definitions to be used by Applesauce. When you add a format, it will automatically be recognized everywhere in the client software such as the Disk Analyzer and Fast Imager. In order to add new formats, there is an Applesauce directory in your Documents folder. Within this folder there is a Formats one that contains the file ''hardsector_config.json''. The hard sector configuration files are text files in JSON format. The root object of the JSON should be an array. A single file can have as may format descriptions as desired. Whenever you edit the ''hardsector_config.json'', you will need to restart the Applesauce client in order to have it load the changes.
 +
 +Creating a format definition is a highly technical process and if you are not very familiar with how disks are structured, this will likely seem a daunting task.
 The hard sector configuration files are text files in JSON format. The root object of the JSON should be an array. A single file can have as may format descriptions as desired. The hard sector configuration files are text files in JSON format. The root object of the JSON should be an array. A single file can have as may format descriptions as desired.
  
Line 170: Line 173:
 ex: ''"addrCksumType": "8xrl"'' ex: ''"addrCksumType": "8xrl"''
  
-=== dataCksumIndex ===+=== addrCksumIndex ===
 Int - //Required//\\ Int - //Required//\\
 Byte index of the start of the stored checksum relative to the address marker (0 = address marker). Byte index of the start of the stored checksum relative to the address marker (0 = address marker).
  
-ex: ''"addrCksumIndex": 257''+ex: ''"addrCksumIndex": 5''
  
 === addrCksumByteSize === === addrCksumByteSize ===
Line 202: Line 205:
 Byte index of the last byte of the address field that needs to be checksummed, relative to the address marker (0 = address marker). Byte index of the last byte of the address field that needs to be checksummed, relative to the address marker (0 = address marker).
  
-ex: ''"addrCksumToIndex": 256''+ex: ''"addrCksumToIndex": 4''
  
 === addrCksumInit === === addrCksumInit ===