Going back to Microsoft's documentation:
Quote:
Hard links
A hard link is the file-system representation of a file by which more than one path references a single file in the same volume. To create a hard link, use the CreateHardLinkA function.
Any changes made to a hard-linked file are instantly visible to applications that access it through the links that reference it. The attributes on the file are reflected in every hard link to that file, and changes to that file's attributes propagate to all the hard links. However, the directory entry size and attribute information of the file are visibly updated only at the link through which the change was made. For example, if you clear the read-only attribute flag on a particular hard link so you can delete that hard link, and there are multiple hard links to the file, the other hard links display that the read-only attribute is still set, which isn't true. To change the file back to the read-only state, you must set the read-only flag on the file from one of its remaining hard links.
For example, in a system where C: and D: are local drives and Z: is a network drive mapped to \\fred\share, the following references are permitted as a hard link:
C:\dira\ethel.txt linked to C:\dirb\dirc\lucy.txt
D:\dir1\tinker.txt linked to D:\dir2\dirx\bell.txt
C:\diry\bob.bak linked to C:\dir2\mina.txt
This is because all the links are files on the same volume. Hard links can't reference directories, only files, and they can't reference files on different volumes.
The following references aren't permitted:
C:\dira linked to C:\dirb
C:\dira\ethel.txt linked to D:\dirb\lucy.txt
C:\dira\ethel.txt linked to Z:\dirb\lucy.txt
To delete a hard link, use the DeleteFileA function. You can delete hard links in any order regardless of the order in which they're created.
|
It seems rather clear that hardlinks can not be used with a directory/folder. Symlinks can but we are going round the rose with hardlinks.