Closed comanche closed 3 years ago
This is indeed very confusing! Since DirHash checksum file can be verified with other applications, the issue is in DirHash building of full path for the entries in the checksum and for some of them this full path is not correct, which explains both Step 3 and Step 4.
In order to help me understand the issue:
-sumRelativePath
switch?DirHash Z:\ -sum
" or "DirHash . -sum
"?I will also try to re-check the code in case I notice something wrong their. Thank you for your help.
Found out what the issue is. DirHash is case sensitive. Fixed the filenames to match and that fixed the issue.
I have a used DirHash verify on a drive (361,855 files) with some these issues:
Steps 3 and 4 contradict each other.
I've run the DirHash checksum file with other similar applications that they pass verification. Only DirHash is having issues with it's own checksum file.
The confusing part is that I attempted to generate a checksum file for a directory with the problem files. This is only a tiny subset of the files in the checksum file. The verification passed without issues.
Any ideas? Could there be issues with