Difference between revisions of "Files:CRC-verified files"

From AniDB
Jump to navigation Jump to search
Line 1: Line 1:
CRC-Verified files are files that have been tested on file corruption. If you download a file, then you should always make a CRC-Check on it (provided, that a CRC-Code was shipped with the file), to prove that your file is a perfect match for the original file you have downloaded. If the CRC check of a file fails, that means that the file has been changed/that there were some transfer errors. As a result, the corrupt file (e.g. videos, zip, etc. ) might not be able to open/play or be of any use at all. If you have a corrupt file, you should either redownload it completely or request a Patch for it. (Text about Patching missing)
+
'''CRC-verified files''' are files that have been tested on file corruption. If you download a file, then you should always make a CRC check on it (provided that a CRC hash was shipped with the file), to prove that your file is a perfect match for the original file. If the CRC check of a file fails, the file may have been changed or your file has been corrupted by the transfer. As a result, the corrupt file (e.g. videos, zip etc) might not be able to open/play or be of any use at all. If you have a corrupt file, you should either redownload it completely or request a patch for it, via a tool such as [http://sourceforge.net/projects/zidrav/ ZIDRAV].
 +
<!--Text about Patching missing-->
  
There are download programs (emule/edonkey/bittorrent) that already have a file verification built in. Bittorent for example immediately checks each downloaded chunk for CRC-Correctness - if it fails the Hash-Check, then that chunk is redownloaded automatically.
+
There are P2P clients (eMule/eDonkey2000/BitTorrent) that already have an inbuilt file verification. For example, BitTorrent immediately checks each downloaded chunk against the SHA1 hash in the metadata file - if it fails the hash check, then that chunk is redownloaded automatically.
 
 
RPHX
 
  
 
[[Category:Definitions]]
 
[[Category:Definitions]]

Revision as of 18:48, 23 May 2005

CRC-verified files are files that have been tested on file corruption. If you download a file, then you should always make a CRC check on it (provided that a CRC hash was shipped with the file), to prove that your file is a perfect match for the original file. If the CRC check of a file fails, the file may have been changed or your file has been corrupted by the transfer. As a result, the corrupt file (e.g. videos, zip etc) might not be able to open/play or be of any use at all. If you have a corrupt file, you should either redownload it completely or request a patch for it, via a tool such as ZIDRAV.

There are P2P clients (eMule/eDonkey2000/BitTorrent) that already have an inbuilt file verification. For example, BitTorrent immediately checks each downloaded chunk against the SHA1 hash in the metadata file - if it fails the hash check, then that chunk is redownloaded automatically.