- Environmental Variable - Path
- Posted by M on February 27th, 2008
I have been given an application at work to test and find that it makes two
additional entries to the System Path. The default entry is:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy stem32\Wbem
however this application add two further entries to its own location.
What is the significance of this and does it matter?
Thanks
- Posted by R. McCarty on February 27th, 2008
It extends the "Known" locations for executables, so that items can be
invoked by name only and not have to include the path to the items.
"M" <spamtrap@spambouncer.org> wrote in message
news:OrYFTnXeIHA.2448@TK2MSFTNGP03.phx.gbl...
- Posted by M on February 27th, 2008
Is there any disadvantage? Why not make the path C:\ and be done with it?
"R. McCarty" <PcEngWork-NoSpam_@mindspring.com> wrote in message
news:%23UEh6zXeIHA.4260@TK2MSFTNGP05.phx.gbl...
- Posted by R. McCarty on February 27th, 2008
Not sure I understand how you mean disadvantage. Path variables
do not imply sub-folders are included. Making a Path Variable that
only references C:\ or the Root Folder wouldn't find executables to
run.
The functionality is there so that instead of C:\Windows\System\Calc.Exe
you simply make a call to Calc
"M" <spamtrap@spambouncer.org> wrote in message
news:OOaJb2XeIHA.5208@TK2MSFTNGP04.phx.gbl...
