-[8.50b7 x86 & x64] Symbolic link bug

[johnlee]

First, I could make a symlink as follows:

Code: Select all

c:\any dir in path>mklink a.exe b.exe

and then try launching it:

Code: Select all

c:\any dir in path>a.exe
c:\any other dir>a.exe

Both of the above attempts made in Command Prompt successfully result in b.exe being executed, whereas entering either command in the Edit1 box of TC produces a "Search path not found!" error.

FWIW, double-clicking a.exe in a TC panel works well.

[ghisler(Author)]

This is most probably a bug in the Windows function to launch programs, sorry. I will check it, but I doubt that I can do anything about it.

[johnlee]

... probably a bug in the Windows function ...

That's possible, but does not seem very likely, cuz the following AutoHotkey code works without a hitch as well, no matter what the current working directory is.

Code: Select all

Run, a.exe

I mean, the example of Command Prompt working well is not an isolated case.

[ghisler(Author)]

Unfortunately it really is a Windows bug in function ShellExecuteEx.

My test results:
Case 1:
lpVerb=NULL
lpFile=a.exe
lpParameters=NULL
lpszDir=c:\current tc dir
--> Error: File not found

Case 2:
lpVerb=open
lpFile=a.exe
lpParameters=NULL
lpszDir=c:\current tc dir
--> Error: Access denied

Case 3:
lpVerb=open
lpFile=c:\full_path_to\a.exe
lpParameters=NULL
lpszDir=c:\current tc dir
--> OK