Copy Files aborts on error

[Sledge]

When copying many files, the copy function aborts if a file cannot be copied, leaving the user unsure of which files have been copied and which ones have not.

This is a big failing of Windows Explorer and it is the reason I changed to FreeCommander, but I am disappointed it has the same weakness. There are other (better) programs that will skip a problem file and continue to copy the rest of the selected files.

[Paszt]

If I understand correctly: with a default install, FreeCommander simply uses the Windows shell to copy files. You can modify the .ini file to allow the use of one of those other (better) programs. I currently have freeCommander setup to use TeraCopy.

By the way, what version of Windows are you using that aborts a batch copy if one file fails? Windows XP and up will continue as far as I know; but I can't remember before Windows XP.

[retry]

i have XP pro.
FC aborts copy on any kind of error.
There is no way to do a redo.
All highlightings are removed.
This is a big disadvantage, so i don't know which file
caused the abort.
I would like to have a benign, tolerant behavior:
If the copying of a file failed it must stay highlighted, but the copy should continue.
Using an external program to do that sounds like a joke:
"If this filemanager can't manage file copy, use an other"