Total Commander (English) • Re: Failed Move Triggers and Outcome?

2Cormy1

It is a specific dialog.

And that is why we ask for the message in that dialog, how else can your problem be adressed? Was it even a TC message or was it a system mesage?

It was a TC message, as I mentioned it simply stopped the copying process when the error occurred. TC did not crash, Windows did not report anything wrong. Only the copy operation dialogs went away. I just had the copy running as part of a queue.
It was a generic failure dialog. It never specified which file caused the error, and it never said what the problem was. I only guessed which file it MIGHT be based on where it APPEARED to be in the copy process based on the copy operation progress status bar.

Unreadable sectors would be the only one that would make any sense to me [...]

Unreadable files is similar to this. What do I mean by that? Well, files that were opened successfully but there's some error while reading the file. This can have several reasons, only one of which is anti-virus software, others are drivers, hardware issues (drive, network etc.) and the list goes on.

TC makes a difference if an error occurs when opening a file or while reading it. Only the former kind causes TC to continue with the next file and ask the user what to do at the end of the operation.

So an error while reading the file would cause the operation to abort...?

I tried to re-create the error but was unable to so I probably won't ever figure this out.

Statistics: Posted by Cormy1 — 2024-05-19, 14:56 UTC

---