| Author | Message | ||
     Suman Beros Username: sberos Registered: N/A |
Running checksum for an HDD Using WinHex 15.1 SR-6 Compute Hash > Checksum (32 bit) I obtain: FACDA16B Using another tool (CHKSUM Version 1.49) I obtain: FBD6 08A2 2586 955D Running checksum for another USB flash drive Using WinHex 15.1 SR-6 Compute Hash > Checksum (32 bit) I obtain: 425A50A5 Using another tool (CHKSUM Version 1.49) I obtain: FC6C B8E3 F4A9 4C70 Why would the checksums be different? Is there some way to relate checksums between WinHex and CHKSUM? | ||
| Alfons Kramer Username: admin3 Registered: 4-2004 |
First, there are different algorithms and the same type of algorithm can be applied to different data types. One should only compare values resulting from the same algorithm / data type. Second, reading from raw storage can be irreproducible in case of bad sectors. Try to use Checksum (64 bit) in WinHex to get comparable results. | ||
| Suman Beros Username: sberos Registered: N/A |
Alfons, thank you for explaining. Rerun using WinHex Checksum (64 bit): 0000000E425A50A5 CHKSUM 1.49: FC6C B8E3 F4A9 4C70 Since applying to same data type and there are no bad sectors on the storage medium, must be the different algorithms. Right? Thanks. | ||
| Stefan Fleischmann Username: admin Registered: 1-2001 |
Yes, either different algorithms or different scope (different sectors hashed) or the data on the medium has changed already because it was not write-blocked and Windows has written to it in the meantime, or any combination of the above. | ||
| Suman Beros Username: sberos Registered: N/A |
Stefan, thanks for additional clarification... very helpful. |