Value in KB, files smaller than this setting will not be included in the index … 0 means index all files
Maximum number of files to add to the index … good to set that to really low value like 100 at first as you test the program, afterwards set it 0, which means include all files
If set to true, only indexing will be built, but no copying or moving of identified files will take place
If set to true, as files being properly identified into sub directories, they’ll be “moved” to BaseRecoverFilterPath instead of copying.
it’s Recommended to set it to true if both Source and Destination dirs are on the same physical disk
This is where all the power of the program lies.
this setting here allows you to configure how the program identifies files and what it should do when a file is successfully identified.
An arbitary identifier for the type of identity defined .. you can call it anything .. and must be unique
- 'PDF document'
That’s the STRING that should be present in the file identification string.
Let’s say … we want to identify PDF documents.
run the command line:
./file-identity-recovery -f somepdfdocument.pdf
Output sample looks like this:
PDF document, version 1.7
Since the string “PDF document” is a unique output … it could then be a good candidate to be used as a type identifier, since no other file will contain “PDF document” as part of its identity
That’s the Sub-location (DIR) where files identified as PDF will be placed, the full path would be the value of BaseRecoverFilterPath/pdf
That’s the Min Size (KB) for pdf files to be identified, PDFs smaller than this value will not be included in the final output
That’s the EXTENSION that files identified as PDF should have, in almost every software recovery case, files may not have the proper extension, thus the extension specified here will be appended to the identified file.
setting this value to none will retain whatever extension the file already has