-Move is like copy and delete

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: Hacker, petermad, Stefan2, white

Post Reply
mp
Junior Member
Junior Member
Posts: 23
Joined: 2010-10-21, 13:55 UTC

-Move is like copy and delete

Post by *mp »

8.51a x64

When I move a file from one directory to another one (on the same drive), Total Commander makes a copy of the file in the target directory and then deletes it from the source. It feels like moving files to another network drive.

When I use the background queue (F2) Total Commander behaves different. Here it's like renaming the file.

Moving directories shows the same behaviour.
In normal mode all files (and subfolders) of the directory are copied and deleted seperately.
When the background queue is used, the whole directory is moved in one single step. This is much faster.

The verify option is not selected in both cases.

You can reproduce this best when you move large files and/or large directories with a large number of subdirectories and files.
Here you can see that the whole moving process is much slower when you do not use the background queue.

This problem persists on network drives. It doesn't occur on local hard drives.
User avatar
MarcinW
Power Member
Power Member
Posts: 852
Joined: 2012-01-23, 15:58 UTC
Location: Poland

Post by *MarcinW »

When moving files (and/or directories) to same partition, this can be done by moving information about file, without moving the file data itself (this is similar to simple rename operation).

When moving to another partition, file data must also be physically moved (copy + delete).

Regards
mp
Junior Member
Junior Member
Posts: 23
Joined: 2010-10-21, 13:55 UTC

Post by *mp »

The move operation is done on the same partition.

Total commander simply renames a file/directory when I use the background queue. That's good.

But it does a slow copy + delete when I simply press [F6] and [RETURN].
User avatar
MarcinW
Power Member
Power Member
Posts: 852
Joined: 2012-01-23, 15:58 UTC
Location: Poland

Post by *MarcinW »

Ok, I overlooked your important notice:
mp wrote:This problem persists on network drives. It doesn't occur on local hard drives.
I couldn't reproduce this with 32-bit TC (with clean INI) and Windows XP.

Did you tested this with clean INI files?
Can you reproduce this also with x32 version?
mp
Junior Member
Junior Member
Posts: 23
Joined: 2010-10-21, 13:55 UTC

Post by *mp »

Thank you very much!

I've got it.

I tried 64-bit with clean INI files. The Problem wasn't there.

Setting "Netwarebugfix=1" causes this problem.

Can you reproduce this?
User avatar
MarcinW
Power Member
Power Member
Posts: 852
Joined: 2012-01-23, 15:58 UTC
Location: Poland

Post by *MarcinW »

After adding "Netwarebugfix=1" setting to wincmd.ini, I could reproduce the problem with TC 8.51a 32-bit and Windows 2003 Server.

This means that you found a bug in TC - TC ignores "Netwarebugfix=1" setting when moving files/directories in background.

Regards
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50547
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Actually Netwarebugfix=1 does exactly this: Copy+Delete instead of Move. And indeed this is currently only supported in the foreground. Since this Netware bug was fixed in later versions of Netware, there should be no need to use Netwarebugfix=1 any more.
Author of Total Commander
https://www.ghisler.com
Post Reply