Some notes while testing RapidCRC Unicode 0.3.11:
Recursive Check
This is one of my big asks for any new hash checking program on the site. It's possible in RapidCRC, and if you want to do a recursive check (check all the directories all at once), go the "all files" route. The directories it stores are relative to the main directory so the check is portable. For example, my test using the Save.me program folder structure:
- Save.me\SaveMe.exe 00E9B767
Save.me\data\aiClipboardSettings\ClipboardContainer.stm 57C37D7F
Save.me\data\aiClipboardSettings\Icons.stm 163F8275
At the same time, some of the interface bits really confused me:
Directory Check
The check for every single file and all files is pretty easy: one checksum per file or one checksum or all files. However, if you go the directory route, and create a bunch of check files for different directories, you need to navigate those directories and check them one at a time.
Checking a new hash
So let's say you want an SHA-512 hash:
- Drag and drop it to the menu and the program and it will generate the plain old CRC check. (In settings you can just disable any kind of automatic check.)
- Click SHA-512. You get prompted "You have to calculate the sha512 checksums first. Click OK to do that now."
- I click OK and the hash is nowhere to be seen so I click the same button again.
- I'm prompted with "Create a .sha512 file for every single file, every directory, or for all files.
- I pick "all files" and choose a name for the checksum list.
Then, to check the file, drag and drop the hash file into the window. If you save the file somewhere other than the directory where it was located, it will error.
All that seems reasonable and I was able to wander my way through the interface to figure that out, but it wasn't exactly simple or intuitive. Someone who didn't use these programs frequently or didn't know what they were looking for would likely get tripped up. As such, a quick video or slideshow howto to get people onboard with the features might be ideal.
This is still a full-featured and very effective program -- but it's closer to FileVerifier++ in terms of complexity than my other favorite checksum program, Hash.
NTFS Check
I put a hash into the checksum into NTFS string and, apart from telling me that was done in the "Info" column next to a file, the way to verify it was to click "SVF file" button. Again, not obvious.
---
Anyway, I think I'm sort of writing a howto here rather than commenting on the program effectively but maybe that will help someone.