You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**Fill failed blocks**|Fill blocks that give read errors with null bytes. When this option is checked, *tapeimgr* calls *dd* with the flags `conv=noerror,sync`. The use of these flags is often recommended to ensure a forensic image with no missing/offset bytes in case of read errors (source: [*forensicswiki*](https://www.forensicswiki.org/wiki/Dd)), but when used with a block size that is larger than the actual block size it will generate padding bytes that make the extracted data unreadable. Because of this, any user-specified value of the **Initial Block Size** setting (see above) is ignored when this option is used. **WARNING: this option may result in malformed output if the actual block size is either smaller than 512 bytes, and/or if the block size is not a multiple of 512 bytes! (I have no idea if this is even possible?).**|
108
+
|**Swap little/big endian**|Use this option to swap the endianness of the file by adding `conv=swab`*dd* option. This is needed most commonly if the tape was created on an older [big endian OS](https://geraldonit.com/2017/09/04/big-and-little-endian-operating-systems/).|
108
109
|**Identifier**|Unique identifier. You can either enter an existing identifier yourself, or press the *UUID* button to generate a [Universally unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier).|
109
110
|**Description**|A text string that describes the tape (e.g. the title that is written on its inlay card).|
110
111
|**Notes**|Any additional info or notes you want to record with the tape.|
@@ -113,11 +114,12 @@ If needed you can use the folowing options to customize the behaviour of *tapeim
113
114
114
115
It is also possible to invoke *tapeimgr* with command-line arguments. The general syntax is:
|`--fill, -f`|Fill blocks that give read errors with null bytes. When this option is checked, *tapeimgr* calls *dd* with the flags `conv=noerror,sync`. The use of these flags is often recommended to ensure a forensic image with no missing/offset bytes in case of read errors (source: [*forensicswiki*](https://www.forensicswiki.org/wiki/Dd)), but when used with a block size that is larger than the actual block size it will generate padding bytes that make the extracted data unreadable. Because of this, any user-specified value of the `--blocksize`setting (see above) is ignored when this option is used. **WARNING: this option may result in malformed output if the actual block size is either smaller than 512 bytes, and/or if the block size is not a multiple of 512 bytes! (I have no idea if this is even possible?).**|
146
+
|`--endianswap, -E`|Use this option to swap the endianness of the file by adding `conv=swab`*dd* option. This is needed most commonly if the tape was created on an older [big endian OS](https://geraldonit.com/2017/09/04/big-and-little-endian-operating-systems/).|
144
147
|`--identifier IDENTIFIER, -i IDENTIFIER`|Unique identifier. You can either enter an existing identifier yourself, or enter special value `@uuid` to generate a [Universally unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier).|
145
148
|`--description DESCRIPTION, -c DESCRIPTION `|A text string that describes the tape (e.g. the title that is written on its inlay card).|
146
149
|`--notes NOTES, -n NOTES`|Any additional info or notes you want to record with the tape.|
0 commit comments