CrcCheckCopy - How it works
We describe here how to use CrcCheckCopy, our CRC file and folder comparison utility to compare and verify the integrity of large sets of files.
Scans the files, calculates their CRC32 stamp and saves it together with their file size in a file called CRCstamps.txt.
To start the scan use the command:
CrcCheckCopy /scan c:\my-source-folder
./CrcCheckCopy /scan /my-source-folder
The scan progress will look like this:
The CRCstamps.txt will be saved in the current folder (working directory) and will look like this:
# This file is created by vCrcCheckCopy 2.1 (http://www.StarMessageSoftware.com) # Date of run:2021-01-03 12:49:44 # Calculating the CRC signatures of the files in path:\tmp # List of ignored files: # \tmp\CRCstamps.txt # Number of ignored files: 1 # Total files in source path:860 # List of files (relative paths), their CRC and their filesize: "5.8.7.yaml" f1812144 1283 "5.9.4.yaml" 18620e4d 1443 "cpp-demo-win.iobj" 60862df6 583371 "cpp-demo-win.ipdb" 5e156ef8 156272 "cpp-demo-win.pdb" 36bc3764 4935680 ......... "Win32\Release\intermediate-Win32\libShareware.log" 1adb1e37 358 "winget.txt" 2dc6518 291 # End of scanned files, their CRC and their filesize. # Performance statistics: # 00:01:23.8 total processing time, of which, # 00:00:00.3 were for the scanning of the disk folders and # 00:00:00.2 for the sorting of the files in memory. # 860 files, 998'276'859 bytes. # Processing rate: 10 files/sec, 11636 Kb/sec.
The CRC checksum is stored in HEX format because this is the common format for CRC codes, and the file size in decimal form because this is how the sizes are presented in file explorer (or MacOS finder) and in the DOS command prompt (or MacOS terminal).
Our CRC comparison utility uses the CRCstamps.txt (that was created in the "scan" phase) to verify that each file on the "destination" folder has the same filesize and the same CRC32.
The CRCstamps.txt file must be in the current folder (working directory).
To start the verification use the command:
CheckCopy /verify c:\my-destination-folder
./CheckCopy /verify /my-destination-folder
The CRC verification progress will look like this:
The CRC comparison results are shown on screen but also logged in a report file named "CrcCheckCopy-verification-report.txt". The report file will contain a list of missing files, files that have different file size and files that have different CRC checksum.
The report file is stored in the current folder (working directory) and will look like this:
Reading CRCstamps.txt and comparing files in the destination path:c:\tmp Date of run:2021-01-03 14:27:56 List of files that did not pass the verification: (missing files, files of different filesize, or different CRC) --- Start of error report ------------------------------------------------------ [Different filesize] CrcCheckCopy-verification-report.txt --- End of error report ------------------------------------------------------- Verification of the 860 files was completed. Total number of errors: 1 Performance statistics: 00:01:07.2 total processing time. 860 files, 998'276'304 bytes. Processing rate: 12 files/sec, 14510 Kb/sec.
Requirements (Filesystem permissions needed)
The utility needs to create in the current directory a "CRCstamps.txt" file during the scanning/CRC generation phase and a report file during the file comparison phase.
Therefore, the user account that executes the program must have read+write permissions to the current directory (also called working directory).
For the folders that need to be scanned or compared, the user account that executes the program must have read permissions.