So why is this now a problem if I have a working method? I'm not scared by command line, I can remember when there was only command line, so DOS utilities/instructions are fine. I can code for C# / VB.net / C++ / Python / DOS Batch provided the required libraries are free or built in. The question is: Is there a method that will verify the files as they are copied or a better verification program than WinDiff, or even better yet a guaranteed way to copy these files with 100% integrity so I don't have to verify them? Individually creating MD5, checksum or hash of files is not an option unless there's an efficient library/method/algorithm that I can implement in a programming language as there would be hundreds of thousands of individual files. I have previously used XCopy with the /v switch but was advised that that utility was depreciated in Windows 7 and I shouldn't be using it.

This process works but WinDiff is slow, sometimes taking more time to verify than it took to originally copy RoboCopy does not have a and verify switch like XCopy. Occasionally the files on the other disc do not match the source disc, in the order of for every 4TB copied there will be one error in one file (that's 0.000000025%).Ĭurrently I am using RoboCopy or Windows Explorer copy to duplicate the files onto the other discs and WinDiff to verify the contents, which is how I know that there's a very small error rate. I am a GIS specialist, part of this is to routinely copy vast quantities of data to disc - backup, archiving and delivery.

Teracopy for windows 7