PATH to ..\system32 seemingly not working

[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

 

[Bill James]

That is not normal for Windows XP, something has messed up the Path on your computer. You can check the Path by going to Control Panel, System, Advanced tab. If the Path is long, it's easier to copy and paste to NotePad to see it all in one piece. Click on Path in the bottom panel, then Edit.

--

Bill James
Microsoft MVP - Shell/User

Win9x VBScript Utilities » www.billsway.com/vbspage/
Windows Tweaks & Tips » www.billsway.com/notes_public/

 

[GSV Three Minds in a Can]

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?

Yes it should - if %systemroot% is set correctly. Try typing 'set' in
the CMD window, which should show you all the applicable environment
variables.

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.)

Try my computer, properties, advanced, environment variables (although
this just shows the additions that the user makes to 'path', not the
values which are added by default).

 

[Sporkman]

Thanks, Bill. That seems to have fixed the problem, whatever it was.
All I did was Edit the Path from System Properties, as you advised . . .
deleted the last path added by a program (UltraEdit), then added it back
after I confirmed everything working normally. And it still works
normally. Sheesh. Who woulda guessed? (Obviously you did.)

Best regards,
'Sporky'

 

[Bill James]

Did you happen to notice if there was an extra semicolon ( at the end of the path? I have seen that sometimes cause a problem, but there is more to it that since testing by adding a semicolon at the end has no effect. Something I have seen and fixed by removing the trailing semicolon, but it bugs me that it is not a reproducible problem.

--

Bill James
Microsoft MVP - Shell/User

Win9x VBScript Utilities » www.billsway.com/vbspage/
Windows Tweaks & Tips » www.billsway.com/notes_public/