Internal commands

[parker309]

I have just recently upgraded a PC from XP Home to XP Pro and am having a bit of an issue. The internal commands like "rundll32" and "ping" are not recognized as internal commands. This is causing issues trying to install software. What has happened. I have upgraded other PC's and have not had this issue. Any insight would be appreciated. Thanks in advance.

 

[linney]

Was Home SP1 and Pro not SP1? Try reinstalling SP1.

Check your System Files by running SFC /Scannow from the Start Run box.

 

[parker309]

XP Home had no SP's. I did the upgrade to XP Pro and then applied SP1. I will try re-installing SP1. Any other thoughts? Thanks for the quick reply.

 

[Jontmke]

Somehow your "path" environment got messed up. How it got that way, who knows.
Go into the evironment variables and check it out.

Jon

There is much pleasure to be gained from useless knowledge. (Bertrand Russell)

 

[bcastner]

Both of your examples are external commands. Let me guess and say that the Environmental Variable "Path" is incorrect.

right-click My Computer, Properties, Advanced, (at the way bottom) Environmental Variables. In the lower box scroll until you see "Path" and hit edit. It should look at least in the beginning like this:


%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;

If not add the entries above exactly as they appear.

 

[parker309]

Thanks for the replys. I did check that and the Path for the System Variables is set correctly. I added a variable Path = c:\windows\system32 to the User Variables and was able to run all the necessary commands. However I am still having issue with the software not registering properly. Tech Support for the software stated that upon install it needs to run the rundll32.exe to register some dll's. That does not seem to be happening. I am confused. I have never seen this before. Why woould the three other upgraded systems work fine? Strange.

 

[linney]

For the syntax to register dll's type "regsvr32 /?" at any command prompt.