D
Dick Watson
I'm trying to add an external command line utility (fsum.exe from slavasoft)
to a WinXP system but do not want to just dump the executable in
%SystemRoot%\system32 for reasons of traceability as to how all of the
add-in stuff like this got on the system. But I also don't want to add
%ProgramFile%\misc\fsum (wherein I document the source of the code, etc) to
the system environment path in order to avoid the path getting any more out
of hand than it already is and to avoid adding lots of directories (where
anything will be run from) to the path when I just want to be able to find
one specific executable.
I've tried creating a .lnk in %SystemRoot%, but cmd doesn't follow these.
I've tried registering
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\fsum.exe with a default REG_EXPANS_SZ pointing to the executable, but
cmd also appears to ignore these.
What is the "best practice" way to get a specific external command in the
path? Just put a copy of the executable in %SystemRoot% or
%SystemRoot%\system32?
to a WinXP system but do not want to just dump the executable in
%SystemRoot%\system32 for reasons of traceability as to how all of the
add-in stuff like this got on the system. But I also don't want to add
%ProgramFile%\misc\fsum (wherein I document the source of the code, etc) to
the system environment path in order to avoid the path getting any more out
of hand than it already is and to avoid adding lots of directories (where
anything will be run from) to the path when I just want to be able to find
one specific executable.
I've tried creating a .lnk in %SystemRoot%, but cmd doesn't follow these.
I've tried registering
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\fsum.exe with a default REG_EXPANS_SZ pointing to the executable, but
cmd also appears to ignore these.
What is the "best practice" way to get a specific external command in the
path? Just put a copy of the executable in %SystemRoot% or
%SystemRoot%\system32?