VHD mounted drives and <LNK> directories
Moderators: white, Hacker, petermad, Stefan2
VHD mounted drives and <LNK> directories
Hi,
When mounting a VHD drive image created using windows 7's 'Backup & Restore' using Windows 7 'disk management' tool, it's impossible to navigate <LNK> folders.
For example, if the mounted drive resides on "I:\", navigating to "I:\Users\Blight\My Documents", opens up "C:\Users\Blight\My Documents".
This is not the case when navigating through explorer.
My concern about this bug is the potential for erasing the wrong files by accident.
When mounting a VHD drive image created using windows 7's 'Backup & Restore' using Windows 7 'disk management' tool, it's impossible to navigate <LNK> folders.
For example, if the mounted drive resides on "I:\", navigating to "I:\Users\Blight\My Documents", opens up "C:\Users\Blight\My Documents".
This is not the case when navigating through explorer.
My concern about this bug is the potential for erasing the wrong files by accident.
Yaron Gur
Zoom Player . Lead Developer
Zoom Player . Lead Developer
Related problem:Accessing remote server junctions/hardlinks(meanwhile fixed)
BTW:
BTW2:
There must be a reason for
"Configuration->Options->Display: [x] show hidden/system files(for experts only!)"
Regards
Holger
BTW:
Isn't it "C:\Users\Blight\Documents"?opens up "C:\Users\Blight\My Documents"
BTW2:
There must be a reason for
"Configuration->Options->Display: [x] show hidden/system files(for experts only!)"
![Wink :wink:](./images/smilies/icon_wink.gif)
Regards
Holger
- ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Unfortunately paths are stored with absolute locations in LNK files, so the drive C is hard coded. Unfortunately Total Commander cannot know whether such a hard-coded link is wrong or not. It seems that the Explorer makes some assumptions because the user mounts the drive within Explorer.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
ghisler:
Then you may want to add these assumptions to TC.
Otherwise TC can cause massive systemic data loss if a user decides to delete a directory containing such links.
Then you may want to add these assumptions to TC.
Otherwise TC can cause massive systemic data loss if a user decides to delete a directory containing such links.
Yaron Gur
Zoom Player . Lead Developer
Zoom Player . Lead Developer
- ghisler(Author)
- Site Admin
- Posts: 48088
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
So far I didn't find any. Also users may actually WANT to have hard links to other drives or sub-trees. For example, I have such a link to move some large files from drive C: (small SSD) to drive F: (Terabyte harddisk) and let Windows still assume that it's on drive C:.Also, there may be simply no way to ask Explorer about such assumptions.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Seeghisler(Author) wrote:So far I didn't find any. Also users may actually WANT to have hard links to other drives or sub-trees. For example, I have such a link to move some large files from drive C: (small SSD) to drive F: (Terabyte harddisk) and let Windows still assume that it's on drive C:.Also, there may be simply no way to ask Explorer about such assumptions.
My windows 7 installation was a clean installation (no update) but shows the same access rightshttp://support.microsoft.com/kb/930128 wrote:By default, a junction point has the following settings after you upgrade Windows XP to Windows Vista:
The attribute of a junction point is hidden.
The Read permission of a junction point is Deny.
Code: Select all
C:\Users\USERNAME>CACLS "My Documents"
C:\Users\USERNAME\My Documents Everyone:(DENY)(special access:)
FILE_READ_DATA]
NT AUTHORITY\SYSTEM:(OI)(CI)(ID)F
BUILTIN\Administrators:(OI)(CI)(ID)F
COMPUTERNAME\USERNAME:(OI)(CI)(ID)F
I guess a link created by the user neither has the hidden/system attribute nor this special permission for Everyone.
On the other side: some (TC) users are used to use the XP compatibility links, to navigate to some places.
Maybe it's a good idea to detect whether the link location is on the same drive as the link target.
By the way: it would be nice to have an option to hide this kind of compatibility junctions separately from "show system/hidden files" option.
Currently I'm using the ignore list here to get a clearer look to the file system structure.
Regards
Holger