ghisler(Author) wrote:I will consider it. But TC shouldn't check the checksum anyway when the copy function stops in the middle...
TC should also not check after appending, except after appending to a 0 byte file. But this behavior is very convenient for testing, so I suggest to fix this later.
Christian,
If if the file sizes are equal, I would suggest to compare
the first few bytes of the files
the last few bytes of the files
the middle few bytes of the files
and perhaps a few bytes from a random location in the files
Shouldn't increase the comparison noticeably if files are equal but should decrease the duration of the verify operation by quite a lot if they are not.
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.
white wrote:TC should also not check after appending, except after appending to a 0 byte file. But this behavior is very convenient for testing, so I suggest to fix this later.
HISTORY.TXT wrote:01.10.13 Fixed: Verify after copy not working correctly when appending to existing file (32/64)
It seems now the appended part is checked for CRC errors. Nice!
I noticed a difference in verifying after appending and after normal copying. If something is appended to the file during verify, verify after copy does not report a CRC error, but verify after appending does. Perhaps the offset for verifying after appending is calculated using file size?