Soft links are ok, what about hard links?

[zappis]

NTFS supports hard links. Does TC support making hard links? If not, I ask for this to be implemented in the next version.

[ghisler(Author)]

No it doesn't, but it handles them correctly, e.g. when you delete a hard link to a folder, TC will not delete the whole folder contents.

I find it too risky for normal users to use hard links, that's why I'm not adding an internal function to create them. There are enough free tools out there to create hard links.

[IGL]

I wish it could be done with TC after enabling an option "allow to crate NTFS hard lings (CAUTION!)" or something like that. This option can be disabled by default.

[Sheepdog]

I wish it could be done with TC after enabling an option "allow to crate NTFS hard lings (CAUTION!)" or something like that. This option can be disabled by default.

Download this program. Make a new button and fill in as Paramter '%O.lnk %N'. Then you can create Hardlinks from within TC.

sheepdog

(I didn't check, if this prog really creates hardlinks for I do not know the difference between hard and softlinks. But I assume it does.)

[Black Dog]

[face=courier]On 04-05-2004 11:14:47 +0000 ghisler(Author) wrote:

g> I find it too risky for normal users to use hard links,
g> that's why I'm not adding an internal function to create
g> them.

OMG... Christian, isn't it too risky for Normal User to e.g. delete files (or even folders)?! What about moving? These are scaring to death things for that poor guy! DISABLE THEM TOO, PLEASE, I'M BEGGING YOU!!![/face]

[robinsiebler]

Now, now children, if you can't play nicely, I shan't let you play at all.

[icfu]

You don't need extra tools:
fsutil hardlink create <newfile> <existingfile>

Too dangerous to implement? That sounds ridiculous, what a bad excuse.

Is there any other file manager for professionals out there that isn't used by "normal" users? Are there any normal users using TC at all? I think most of them are masochists anyway, they would like to live with some kind of danger instead of having to live with lack of features due to "normal users".

Why do I use a professional file manager like TC when I have to install an extra tool for advanced(?) file operations anyway?

1. File cutting, not splitting
2. Creating new files without opening stupid notepad
3. Creating hard links
4. Creating junctions
5. Setting sparse attribute and others unknown to TC
6. Synchronizing folders (deleting empty folders)
7. Resuming local copy operations
8. Extra search tool for finding files by creation date, that's UNBELIEVABLE!
9. ...

Icfu

[Lefteous]

2icfu

You don't need extra tools:
fsutil hardlink create <newfile> <existingfile>

It's a windows commandline tool, which is an extra program from my point of view. Nevertheless it has the disadvantage that it only works for Administrator group members only, which is not necessary to create a hard link.

The program mentioned by Sheepdog works without this restriction. It's simply using the CreateHardLink API function.

[icfu]

Users without administrative rights shouldn't be able to create hard links imho. Maybe that's the point for the excuse to not implement it, no idea.

Icfu

[ghisler(Author)]

It's not too dangerous to implement - it's just not the right thing in the hands of normal users. Why do you think that Microsoft has removed it from Windows 2000? To my knowledge, it was there in some early beta versions (I may be wrong, though).

[icfu]

Why can't you make an option to disable it by default and activate it through wincmd.ini? I really don't get it, sorry.

I thought that people using TC do that because they want some improvement to Windows Explorer, maybe I am completely wrong and people are using TC because they like the fancy GUI and are too stupid to ask what making hard links means before they activate such an option?

fsutil is available under XP, so even if Microsoft removed the possibility in Windows 2000 there must have been some reason to reimplement it.

Icfu

[Black Dog]

[face=courier]On 06-05-2004 22:17:02 +0000 ghisler(Author) wrote:

g> It's not too dangerous to implement - it's just not the
g> right thing in the hands of normal users.

OMG... What about cm_AdministerServer, is it the right thing in the hands of normal users? Christian, you can hide all additional NTFS function you may implement as well as you did with already implemented ones. Who knows about e.g. cm_EditOwnerInfo or cm_EditAuditInfo?

g> Why do you think that Microsoft has removed it from Windows
g> 2000? To my knowledge, it was there in some early beta
g> versions (I may be wrong, though).

Who cares about what M$ removed - why do you think that Microsoft has made such a horror as Explorer at all?! %) The only thing I care is why you doesn't add all the nice things NTFS can support? As hidden internal commands, of course.[/face]

[Genghis86]

i vouch for implementation of creation of hard links
Total Commander has always been a tool for the professional in my opinion

[IGL]

Please, do not let TC be a program for dummies (Ms Explorer is for them).
An option being off by default and a (WARNING!) word next to an option is enough protection.

[krassonkel]

And here is another vote for this function =)
Really, TC isn't for "normal users"... And if you really think it's too "dangerous" then make it disabled by default...
You also could also just add an ini-line to activate it so no normal user will find it at any time...