Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Have WHICH say how it located an external program ...

May
13,000
174
... via the path ... via the AppPaths key ... current directory ... (are there others?).
 
I thought it did look in AppPaths. I put DUMPBIN.EXE in AppPaths a long time ago and, often, after a VS update, TCC can't find it. After running my FIXDUMPBIN.BTM (which fixes AppPaths), TCC finds it.

Code:
v:\> which dumpbin
dumpbin is an external : C:\program files\microsoft visual studio\2022\community\vc\tools\msvc\14.39.33519\bin\hostx64\x64\dumpbin.exe

v:\> path
PATH=d:\uty;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Microsoft Network Monitor 3\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;d:\gnu;d:\uty;C:\Users\vefatica\AppData\Local\Microsoft\WindowsApps;v:\octave
 
It definitely does.
Code:
[C:\Users\anrdaemon]$ tcc /c which brain
brain is an external : C:\Programs\PersonalBrain2\brain.exe

[C:\Users\anrdaemon]$ set path | tr ; \n | grep -i brain
<nothing>
 
But only the one under HKEY_LOCAL_MACHINE, not the one under HKEY_CURRENT_USER.
 
@Charles Dye

Code:
PATH=d:\uty
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\
C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
C:\WINDOWS\System32\OpenSSH\
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Microsoft Network Monitor 3\
C:\Program Files\dotnet\
C:\Program Files\PowerShell\7\
d:\gnu
d:\uty
C:\Users\vefatica\AppData\Local\Microsoft\WindowsApps
v:\octave

Why not use PATH /N ??
 
I didn't know about it. But is it relevant to this thread?

Code:
v:\> path /n
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\
C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
C:\WINDOWS\System32\OpenSSH\
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Microsoft Network Monitor 3\
C:\Program Files\dotnet\
C:\Program Files\PowerShell\7\
D:\MatLab\bin
d:\uty
d:\gnu
d:\uty

v:\> which dumpbin
dumpbin is an external : C:\program files\microsoft visual studio\2022\community\vc\tools\msvc\14.39.33519\bin\hostx64\x64\dumpbin.exe
 
just easiter to spot the individual paths if you had used /N - maybe an extra 3 characters.... not much to ask
 
Back
Top