PATH environment variable not working ?

  • Thread starter Thread starter Sporkman
  • Start date Start date
S

Sporkman

I'm a little confused by XP's apparent inability to find applications in
the \Windows\system32 directory from a DOS Command Prompt window, even
though the PATH that is reported includes "%systemroot%\system32". What
prompted me to realize this is I was trying to use IPCONFIG and PING
from a DOS window, and Windows wasn't finding those apps. I can SET
PATH in the DOS window to include "%PATH%;C:\Windows\system32" and
thereafter for that DOS session everything works fine (naturally). But
of course if I exit then start another Command Prompt I would have to
SET PATH again or else change to the \Windows\system32 directory. Why
does Windows do this? The "%systemroot%\system32" entry in the PATH
variable should cover that, should it not?

OK, I can certainly set up a batch file to run, but I'd rather know
what's going on. Anybody have a clue? And BTW, where IS the PATH
variable set? It's not in BOOT.INI, nor in any other INI files or other
places that I figure might be possible. Is it done in the Registry
somewhere? (If it is it's not that easy to find.)

TIA
'Sporky'
Charlotte, NC
 
Hi, Sporkman,

When you are in the Windows Command prompt, type CD\ to put you in the root
directory, you have to type the path each time, or change to the folder you
want to work in.

The Path variable is located in the following:

Start, right click My Computer, Properties, Advanced, Environment Variables,
Highlite Path, click Edit, hit the right arrow key to get rid of the
highlight, be sure to add a semi-colon if you add programs.
 
Hello Sporkman,

[Start]
| Help and Support |
autoexec
[Enter]

In "Full-text Search Matches (8 results)"
under 5. "Create custom startup files for an MS-DOS-based
program"

Jan

-----Original Message-----
I'm a little confused by XP's apparent inability to find applications in
the \Windows\system32 directory from a DOS Command Prompt window, even
though the PATH that is reported includes "%systemroot% \system32". What
prompted me to realize this is I was trying to use IPCONFIG and PING
from a DOS window, and Windows wasn't finding those apps. I can SET
PATH in the DOS window to include "% PATH%;C:\Windows\system32" and
thereafter for that DOS session everything works fine (naturally). But
of course if I exit then start another Command Prompt I would have to
SET PATH again or else change to the \Windows\system32 directory. Why
does Windows do this? The "%systemroot%\system32" entry in the PATH
variable should cover that, should it not?
Click to expand...
 
Back
Top