Command Reference

Here are some of the program's features that might not be self explanatory.

"Why does the program show 0x00 instead of that part's checksum?"

If any byte is repeated throughout a part, that byte's hexadecimal code will be shown instead of the checksum.

Removing a file from the comparison

Right-click the file's header and choose "Remove File" from the menu. You should not remove a file unless it has no good parts that would be needed to repair the file.

"I changed the location of one of the input files and the program can't find it when writing the output!"

If you are 100% sure where the file has been moved to, right-click the file's header and choose "Locate File" from the menu. This will only check if the file has the same file size, but does not verify the contents of the file.

The safe way is to click the Add File button and add it again to the comparison. After that you can remove the old record of the file. This way you will not lose your markers. (The problem of losing markers might be fixed some day in the future)

When to change the part length and algorithm?

If there are large blocks of corruption or the file is very large, you might want to go for larger parts. If you are fixing small files, you might want to make them smaller. The limits are 1 KB and 10 MB.

If CRC-32 (32 bits) is not reliable enough for you, you can use for example the MD5 (128 bits) or SHA-1 (160 bits) algorithm.

Tools: Try to Guess Good Parts

This will mark parts "good" based on their popularity. This does not necessarily mean that you will get an uncorrupted copy, so don't use this feature unless you know what you are doing. Rows that already have some markers will not be affected.


Return to Help Topics