Just found an (imho) serious bug in 4.2 if a copy-session is canceled during a file-copy and then re-started.
1. Options besides default: Only copy newer, resume partial (no effect)
2. Copy some dir with big files (vmware-data here)..
3. Click cancel during copy of one big file
4. Click copy again
5. Partial file gets not resumed, nor overwritten, but "existing file is newer or same" message is shown
6. Data-loss in destination
Could be a by-design bug which is caused by date-compare without file-length compare or similar. I consider it serious, it almost caused a data-loss here, if I would not have seen the much different file size by accident.
The image shows 2 partial incomplete files, did two tries with cancel/restart.
If you can't reproduce, I will try to assist!
And thanks for this otherwise very good and much needed software! |
