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 revisionBoth sides next revision
adv:hardsectorconf [2022/08/06 03:18] diskblitzadv:hardsectorconf [2023/06/10 16:49] – Add 'enabled' tag, decorate boolean values david-schmidt
Line 34: Line 34:
  
 ex: ''"export": ["northstar_nsi"]'' ex: ''"export": ["northstar_nsi"]''
 +
 +=== enabled ===
 +[Boolean] - //Required//\\
 +Set to ''true'' if you would like this named format definition to be considered when analyzing disks. If no value is provided, then it defaults to ''false''.
 +
 +ex: ''"enabled": true''
  
  
Line 232: Line 238:
 === addrCksumRefIn === === addrCksumRefIn ===
 Boolean\\ Boolean\\
-If true, then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.+If ''true'', then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.
  
 ex: ''"addrCksumRefIn": true'' ex: ''"addrCksumRefIn": true''
Line 238: Line 244:
 === addrCksumRefOut === === addrCksumRefOut ===
 Boolean\\ Boolean\\
-If true, then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.+If ''true'', then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.
  
 ex: ''"addrCksumRefOut": true'' ex: ''"addrCksumRefOut": true''
Line 305: Line 311:
 === trackVerify === === trackVerify ===
 Boolean - //Only used if trackDerived is "data"//\\ Boolean - //Only used if trackDerived is "data"//\\
-Set to true if you would like to validate that the track number matches the physical track number. If no value is provided, then it defaults to ''false''.+Set to ''true'' if you would like to validate that the track number matches the physical track number. If no value is provided, then it defaults to ''false''.
  
 ex: ''"trackVerify": true'' ex: ''"trackVerify": true''
Line 450: Line 456:
 === dataCksumRefIn === === dataCksumRefIn ===
 Boolean\\ Boolean\\
-If true, then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.+If ''true'', then the data bytes will be reflected (bit-endian reversed (eg: 0x80 becomes 0x01)) on input to the checksum algorithm. If no value is provided, then it defaults to ''false''.
  
 ex: ''"dataCksumRefIn": true'' ex: ''"dataCksumRefIn": true''
Line 456: Line 462:
 === dataCksumRefOut === === dataCksumRefOut ===
 Boolean\\ Boolean\\
-If true, then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.+If ''true'', then the result of the checksum algorithm will have its data reflected (bit-endian reversed) on output. If no value is provided, then it defaults to ''false''.
  
 ex: ''"dataCksumRefOut": true'' ex: ''"dataCksumRefOut": true''