Total Commander

Hope to support NTFS Features:
1. Support sparse file copy or move.
2. To support hard-Link, point to a file multiple files to reduce the space occupied,and copy or move.

This feature is very useful

Hardlinks may harm if you don't know what you're doing (e.g. you have multiple links to same file and modify file via one of them).

You may create hardlinks via external tools like NTFS Links, also it allows to create junctions to folders.

or can support sparse file copy or move?

MVV wrote:Hardlinks may harm if you don't know what you're doing (e.g. you have multiple links to same file and modify file via one of them).

You may create hardlinks via external tools like NTFS Links, also it allows to create junctions to folders.

How is that harm? The file gets modified (as you likely wanted). The only problem I've run into with hardlinks, whether it is windows handling of them, TC or the tools that are doing the heavy lifting:
1) The date is not updated on hardlinked files, when one of the others are changed.
2) The count of hardlinks isn't reduced when one of the hardlinks are removed or deleted.

And the restriction on hardlinks under XP/2K (whether the same holds true for Vista/7 (?)) makes them mostly unusable to me: the hardlink must reside on the same physical drive.

And the restriction on hardlinks under XP/2K (whether the same holds true for Vista/7 (?)) makes them mostly unusable to me: the hardlink must reside on the same physical drive.

On XP you can use Junctions on folders to 'tunnel' files across multiple volumes.
On Vista/W7, Symbolic Links can be used for files. They work across multiple volumes and over network drives too.

The count of hardlinks isn't reduced when one of the hard links are removed or deleted

The Count isn't decremented if hardlink is moved to Recycle Bin. It is decremented when Recycle Bin is cleared.
If you delete hardlink with shift+del, count will be decremented immediately.

W7 (at least x64) heavily uses hard links and junctions. Almost all files in system32 are hardlinked. Support for "new" NTFS features would be very handy.
And [tc.size] reports 0 for symbolic links. I believe this is a bug. It should report size of the target file.

MVV wrote:Hardlinks may harm if you don't know what you're doing (e.g. you have multiple links to same file and modify file via one of them).

You may create hardlinks via external tools like NTFS Links, also it allows to create junctions to folders.

Lot's of things can harm, if you don't use them properly. However, I always thought of TC as advanced file manager which gives users various tools to work with. And as such, having the ability to work with these NTFS features makes perfect sense to me.

I'd also add out of the box support for junctions to the list. TC already supports them partially (displays and deletes them properly), could also create them as well.

I'm using above mentioned tool for years and it works well for both creation junctions and hardlinks.