Files:CRC-verified files: Difference between revisions

Jump to navigation Jump to search
m
rephrase
(rewrite; please check this for accuracy)
m (rephrase)
Line 11: Line 11:
Any change, from a single changed bit to widespread changes throughout the file, will change the CRC. While a single-bit error is often imperceptible, files with major corruption may be unplayable. It is possible to patch a corrupt file to a known-good version using a tool such as [[Zidrav]] or [[QuickPar]].  
Any change, from a single changed bit to widespread changes throughout the file, will change the CRC. While a single-bit error is often imperceptible, files with major corruption may be unplayable. It is possible to patch a corrupt file to a known-good version using a tool such as [[Zidrav]] or [[QuickPar]].  


Other hashes, such as MD5, SHA-1, and ed2k are ''stronger'' than CRC: the chance of a CRC differing between two files with the same ed2k or MD5 hash is 79 billion billion billion to one. If the MD5, SHA-1, or ed2k hash matches a published 'good hash', then it is very unlikely indeed that the CRC will fail. When AniDB lists a file as CRC-verified, you can use any of the hashes listed to verify the file.  
The other hashes AniDB lists (MD5, SHA-1, and ed2k) are ''stronger'' than CRC: the chance of a CRC differing between two files with the same ed2k, SHA-1 or MD5 hash is at least 79 billion billion billion to one. If the MD5, SHA-1, or ed2k hash matches a published 'good hash', then it is very unlikely indeed that the CRC will fail. When AniDB lists a file as CRC-verified, you can use any of the hashes listed to verify the file.  


[[Category:Definitions]]
[[Category:Definitions]]
16

edits

Navigation menu

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.