[Rockman413]

Originally Posted by SigFriedChicken

This is a simple-seeming question, but it really depends on the specifics.

When you copy files, validation is usually handled by the operating system. I don't believe that operating systems generally perform a full "verify" operation when you copy a file, though they probably compare metadata, like file size, to confirm that the source and target are the same size. Generally, if no error is reported, you can be confident that the file is not corrupt. But "not corrupt" is not the same thing as "exactly the same as the source."

There are specialized copying and backup applications that will perform a full "verify" operation, where the source and target are compared, block by block, to ensure that they are exactly the same. Full verify operations are time-consuming and often take just as long as the actual copy operation. An alternative is to manually generate a checksum for a file, before it is copied, and then get a checksum for the file after it is copied and confirm that they match.

Well you said it may not be the same as the source. So after of 50 hours of mixing and hard work, then we copy to another location, and we should suspect that's not exactly the same as what we have mixed?