Total Commander

Total Commander in VirtualBox 6.1.4, Windows 10
Host: Ubuntu 18.04

It wont open in a shared folder a symlink to folder made on the host machine.

on the host execute in the virtualbox shared folder Verifify in the guest (in the Windows 10 Virtual Machine) that TC wont open the (as the WindowsExplorer would).

Links usually contain the absolute path with the drive letter. TC cannot know which drive the target is, e.g. drive c:\ on the target could be \\targetpc\mydata on the other PC.

ghisler(Author) wrote: ↑2020-04-30, 07:58 UTC Links usually contain the absolute path with the drive letter. TC cannot know which drive the target is, e.g. drive c:\ on the target could be \\targetpc\mydata on the other PC.

I believe you misread the report.

As stated, @projoy executed `ln -s` on an Ubuntu Linux box to create a symlink within a folder (on the Linux box). There can be no drive letters nor UNC paths involved.

In VirtualBox, @projoy is running a Win10 guest with Total Commander. The Linux folder with the `link_folder`symlink inside is made accessible to to the guest as a shared folder. I have no experience with VirtualBox, so i don't know if the Win10 guest will see the `link_folder`symlink inside the shared folder as a directory or a file.

But if i understand @projoy correctly, Windows Explorer of the Win10 guest has no problem opening this `link_folder`like a normal directory, but TC doesn't do it, which would point to some behavior/issue specific to TC.

Total Commander checks with SetCurrentDirectory whether a directory is accessible. You may not have the necessary rights to do this, then TC will fail to switch to the directory.

ghisler(Author) wrote: ↑2020-05-04, 13:24 UTC Total Commander checks with SetCurrentDirectory whether a directory is accessible. You may not have the necessary rights to do this, then TC will fail to switch to the directory.

You overlooked the following

projoy wrote: ↑2020-04-28, 17:32 UTC (as the WindowsExplorer would).

There are rights to the folder. The Windows Explorer opens the folder with no problems. I believe it is a TC bug.

Windows Explorer only needs the "Read" right for the folder, TC needs read and execute. This is necessary so I can set the current directory when using the command line.

Why do you need the execute rights for a directory ?!?

Anyhow, I found that it is not completely the problem.
The link directory is on a drive, which hadnt been automounted (in linux). After automounting the drive, the TC problem with the directory also disappeared.

Its definitely an interesting TC problem, you could pay attention to. At least I would have done it.

Huh? Why is failing to (auto)mount a drive on your Linux host system a "TC problem"?
Maybe i fail to grasp what you intended to say, but that is what your last post seems to say....

Why do you need the execute rights for a directory ?!?

For "SetCurrentDirectory".