Total Commander

2ghisler(Author)
True. Still, it's just annoying to have to abort the copy operation, close the program the file is open in and then start the move operation in TC again. When the files are located on an HDD it gets even worse because of disk thrashing which slows everything down.

It should be possible for TC to work like this:
Show a confirmation if moving the file(s) failed before it silently changes the operation to copy+delete. The message could say that moving failed and offer to copy+delete instead, but it should also offer to try the move operation again (so closing the other program helps).

I think I suggested this years ago, although probably not in a separate suggestion thread.

Regards
Dalai

Dalai wrote: ↑2023-08-18, 03:12 UTC 2Rekrul
When TC can't move a file within the same volume it will copy it instead and try to delete it afterwards. If it's still locked at that point in time, you'll get an error message. Try to move a (large) video file while it's being played in some video/media player. Then you'll see what I mean.

Except that none of the files were open in any other program. I saved the pictures from a web site, ran out of space, closed the tab in the browser and then tried to move them to a sub-directory, which is when I got the error message. There is no valid reason that TC should have been copying any of the files instead of directly moving them.

Rekrul wrote: ↑2023-08-19, 07:39 UTCThere is no valid reason that TC should have been copying any of the files instead of directly moving them.

In theory. There may have been a virus scanner still scanning the file(s).

But as I said: it's an annoying TC behavior to silently change the operation.

Regards
Dalai

I also don't understand why TC in such cases doesn't allow 3 simple options:
-Retry
-Cancel
-Change to copy and delete

i tried it on another disk and it moved the file. it didn't give an error.

I have to postpone this to a later version, it would require major changes to the copy/move functions.

Dalai wrote: ↑2023-08-19, 12:53 UTC In theory. There may have been a virus scanner still scanning the file(s).

And if there wasn't?

Well, something must have locked the file, so the MoveFile function failed.

I'm moving this to the suggestion forum as a reminder to improve the move function in a future version.

Moderator message