Start links from network drives broken

[MaxKane]

Hi,

I can't start any existing links from network drives. These are links to an executable also located on a network drive, working path too.

The last working version is 7.55a, all version above don't work anymore.

It seems, that the working dir will be ignored.

[sqa_wizard]

2MaxKane: Welcome to the forum !
Do your network drives are mapped to a drive letter by chance ?

You may note that mapped drive letters are user specific.
This means that a TC started "as administrator" will not see any drive letter of the normal user and vice versa.

[MaxKane]

the network drives are mapped to drive letters. The letters are valid.

Simple Example: an executable with 1-2 dynamic libraries,
- the exe is on \\server\volume\dir1 (\\server\volume mapped to x:)
- the libraries are on \\server\volume\dir2

make a link to the executable and as working dir enter \\server\volume\dir2

starting the link shows an error, that the first needed dynamic library couldn't be found. Using drive letter or unc shows the same error.

Starting the same link with TC 7.55a, already worked fine.

[HolgerK]

14.12.10 Release Total Commander 7.56a release candidate 1
...
13.12.10 Added: wincmd.ini [Configuration] DllLoad=0 Set DLL load method for plugins and Explorer extensions: -1: Never from current dir (most secure), 0: Only in context menu, 1: always also from current dir (as TC7.55a and older)

Maybe adding DllLoad=1 to the [Configuration] section of wincmd.ini can help?

Regards
Holger

[MaxKane]

Holger,

that's the solution. I should read the notes from new versions

Thanks!

[ghisler(Author)]

This was added to fix a huge security hole in Windows, e.g. when Windows tries to load a dll, and another (malicious) dll with the same name is in the current directory. I have no idea why this prevents links from working, but it really shouldn't...