Verify while copy
Moderators: Hacker, petermad, Stefan2, white
Verify while copy
Is the Total Commander verifying/comparing source file to target file while copying? Or If i want to be sure about the copy is good, i have to use compare/synchronize?
Compare the contents... and watch
2trob
Hello ! Welcome on board !
¤ Indeed, you can use "Compare by contents" to know if the copying has been correct.
* You also see immediatly if the size of the copy in the target-dir is identical with the original file; it's a simple first visual control.
Kind regards,
Claude
Clo

¤ Indeed, you can use "Compare by contents" to know if the copying has been correct.
* You also see immediatly if the size of the copy in the target-dir is identical with the original file; it's a simple first visual control.

Claude
Clo
#31505 Traducteur Français de T•C French translator Aide en Français Tutoriels Français English Tutorials
In addition you can use Files->Create CRC Checksums (sfv format...) and Verify CRC Checksums (from sfv files).
But as far as I know the OS-function to verify the written data is enabled.
When I use a bad floppy and try to copy files there is always a complaint that data couldn't be written.
To be sure we have to wait for a comment of @ghisler.
sheepdog
But as far as I know the OS-function to verify the written data is enabled.
When I use a bad floppy and try to copy files there is always a complaint that data couldn't be written.
To be sure we have to wait for a comment of @ghisler.
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
Not as far as I can remember. But it comes in mind to me a thread about defective data which was based on hardware faults (USB Stick; HD Prob).trob wrote:Have You ever seen that the TC's copy was wrong?
So if you really want to be sure of identical data it's recommended to use CRC check.
If you copy zip archives its enough to test the copied archive (because zip himself uses CRC-check).
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
2.560.029 bytes in 21430 files took 5 minutes 55 seconds to build a checksum file and again 9 minutes 08 sec to verify them.
Dont know if copy and synchronize is faster, but if you must be sure to have the copied without error, you should verify again.
sheepdog
Dont know if copy and synchronize is faster, but if you must be sure to have the copied without error, you should verify again.
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
If you WANT to be sure closer to 100 procent you must verify with a checksum method (SFV / MD5 recommanded).trob wrote:(i'm copying my winchester to another one)
If still use removable storage medium try remove and attach them again before verifing checksum. Otherwise verify is in RAM !
Best wish,

My Best Wishes,
Eugen
Eugen
trob,
TC does not verify files while copying, AFAIK. I think at least one of these tools do, though - http://clubtotal.free.fr/ - Tools - and there look for filecopy and slowcopy.
HTH
Roman
TC does not verify files while copying, AFAIK. I think at least one of these tools do, though - http://clubtotal.free.fr/ - Tools - and there look for filecopy and slowcopy.
HTH
Roman
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.