No, guys, of course it's NOT specific to DO and I don't put DO into a bad light here. As you said, it won't also not work with ANY filemanager, but Protocol uses DO so I told him not use DO of course, but a recovery tool (Explorer, Total Commander,... are also NOT recovery tools!).
And sorry that I only report things that happened. I copied files (images) onto an ext. HDD using DO, got no warning or other messages. Then I moved them back to internal HDD (no error again), opened one and it was corrupt. Then I opened it on the ext. HDD and it was also corrupt (the files definetely were not corrupt on the original source). It was the first time that I got no error message (when trying to recover files from failed HDD's, I first try to copy the files using DO before trying "harder" methods).
Nevertheless if someone gets already an error message while copying with DO (or ANY other filemanager!), he should use a recovery-tool instead.
Edit: If someone wants to do complex and recurring sync-operations, I also would recommend to use a sync-tool. That's not putting DO into bad light! Should I always mention all other filemanagers when another tool (which was designed for the specific operation and thus is better than ANY filemanager under certain circumstances) could do a better job than DO? Of course not.
Sasa, no offense meant, you do great in explaining and helping, I was just trying to add some bits and describe why I found your experience weird. I might have misinterpreted your statement about DO vs. general filemanagers, sorry for that! o)
Anyway, corrupt files can also occur for bad cables and wiring, bad connections, bad memory inside the computer or the controller of the drive goes mad, mismatching bus frequencies etc. Such things are difficult to track down and I'm actually suprised current computers work as stable as they do! o)
I'm curious, although it does not belong here. The external drive, which let you copy onto without errors and read files without errors although they came in bad, was it connected by USB? Was it FAT32 formatted? Is it working correctly now and were you able to reproduce what happened? I have more to deal with drives failing at pcb/mechanics level, it's been long ago that I encountered corrupt data related issues, both are a pita - no question.
Is there any file-based recovery we can recommend for Protocol? I'm using R-Drive Studio, but unfortunately it's not free, rather expensive.
.