Why is NoClone a
TRUE duplicate file finder?
NoClone uses True Byte-by-Byte Comparison
that ensures the duplicate files uncovered are exactly the same in content.
Why is CRC or MD5 not reliable?
Comparing file content
by CRC or MD5 is a common practice of uncovering duplicate files. However the collision
rate of CRC is not satisfactory and recent research indicated that there is a possibility
of collision even for MD5 hashing. Below is an example from http://www.mscs.dal.ca/~selinger/md5collision/:
Here are two files with same MD5 hash value (cdc47d670159eef60916ca03a9d4a007)*.
Windows version:
Hello.exe
erase.exe
Run them and you will
find they got different output as follows:
Therefore, comparing exact content is the only way to ensure accurate result. Compared
with finding duplicate by CRC or MD5 hash, NoClone uncovers duplicate with 100%
accuracy.