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:ibmsectorconf [2022/07/26 21:07] – diskblitzadv:ibmsectorconf [2022/07/26 22:02] – diskblitz
Line 1: Line 1:
 ====== Adding Support for a modified IBM Sectored Disk Format ====== ====== Adding Support for a modified IBM 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 ''ibmsector_config.json''. The IBM 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.+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 ''ibmsector_config.json''. The IBM 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 ''ibmsector_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. 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.
Line 41: Line 41:
  
 === encodingAndMedia === === encodingAndMedia ===
-String - //Required//\\ +[String] - //Required//\\ 
-The physical type of media used as well as the encoding and density. It is represented as a string structured as ''{media}_{encoding}_{density}''. If the format supports more than a single value for either the media or density parameters, you can separate the values with a ``|`` or use a ''*'' as a wildcard value. Being as specific as possible speeds up the analysis process as it limits the number of comparisons that need to be done.+Array of the physical type of media used as well as the encoding and density. It is represented as a string structured as ''{media}_{encoding}_{density}''. If the format supports more than a single value for either the media or density parameters you can use a ''*'' as a wildcard value. Being as specific as possible speeds up the analysis process as it limits the number of comparisons that need to be done.
  
 ^Media^Description^ ^Media^Description^
Line 58: Line 58:
 |500|500kbps (2µs cell window)| |500|500kbps (2µs cell window)|
  
-ex: ''"encodingAndMedia": "5.25_mfm_*"'' or ''"encodingAndMedia": "8|5.25_fm_500"''+ex: ''"encodingAndMedia": ["5.25_mfm_*","8_mfm_500]''