|
Windows® OS has a built in logic to figure out which program should be executed if you type a file name without a path. Sometimes it's necessary to find out which pathname it took finally. The 'Locate Command' tab of the 'Windows™ Extensions' tab can:
- Find out the full path of the exe, bat or cmd which would be started using the same strategy as 'cmd.exe'
- Both strategies of 'cmd.exe' are known, the one for 64-bit and the one for 32-bit programs
- Verbose log which locations are checked
- Detect errors like non-existing directories in the PATH and PATHEXT environment variables which slow down your system
- Brute search for executables and scripts located in any of the Windows program folders independently of any strategy.
- Display of the architecture of the found command (32-bit, 64-bit, ARM aso.)
- Display of all the properties that are available about the found candidate, for example creator company, version number and detailed description.
- Transfer of one of the found path names to the Command Shell tab with one click. Can be used as a basis for testing arguments.
- Opening of a Windows Command Shell on the folder of one of the found path names.
Example: You can use this in case you get the information of your firewall software that the program "Xyz.exe" wants to access the internet (besides, why doesn't it display the full path?) What is "Xyz.exe" and where is it?
Warning: .NET Framework manipulates the result of filename queries. Some special files are visible in a Command Shell and also in File Explorer but not returned by .NET calls. One such example is "C:\Windows\System32\igfxEM.exe". It's just not found by any calls. This is a natural restriction for Mighty Desktop which it can't circumvent because it's based on the .NET Framework. But as far as I know there are only a few of them.
|
