1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved Command Shell Not Recognizing Commands

Discussion in 'Windows XP' started by Lydeard, 2011/10/25.

  1. 2011/10/25
    Lydeard

    Lydeard Well-Known Member Thread Starter

    Joined:
    2006/12/19
    Messages:
    119
    Likes Received:
    1
    XP Pro SP3

    I have a couple of minor issues which I am trying to resolve which are on another post, but when trying to work through the suggestions kind people have offered there I need to use use the CMD function in the Command Shell but can't get it to work (it used to in the past).
    The message I get when entering a command eg. 'IPConfig', 'Ping' or any others as far as I can see is;
    ''IPConfig' is not recognized as an internal or external command, operable program or batch file'.
    Searching for possible reasons for this (Google etc) most people reckon it is likely to be a 'Path' problem or corruption but I need a bit of help in checking and, if necessary, correcting this.
    If I go to 'System Properties>Advanced>Environment Variables' and look at the Path in the System Variables I see;
    C:\WINDOWS\System32;C\WINDOWS;..
    If I highlight this to Edit it I get the Variable Value shown as;
    %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\wbem

    Is this all as should be ?. If it is then what else is the possible cause of the commands not being recognized ?.
    Would greatly appreciate some help.
     
  2. 2011/10/25
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    What happens/shows when you type path in the command window (& press Enter)?
     
    Arie,
    #2

  3. to hide this advert.

  4. 2011/10/25
    Lydeard

    Lydeard Well-Known Member Thread Starter

    Joined:
    2006/12/19
    Messages:
    119
    Likes Received:
    1
    I get:-
    Path = %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\wbem
     
  5. 2011/10/25
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    That's not good :(

    You should get:
    Are you logged into an Administrator account?

    Try creating a new account & see if that works.
     
    Arie,
    #4
    Lydeard likes this.
  6. 2011/10/25
    Lydeard

    Lydeard Well-Known Member Thread Starter

    Joined:
    2006/12/19
    Messages:
    119
    Likes Received:
    1
    Yes Arie I am sole 'Owner/Administrater.
    So sorry to be a 'pain' but how do I create a new account ? Do you mean User Account, if you do then I think I can do that.
     
  7. 2011/10/25
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Yea, sorry, I meant user account :)
     
    Arie,
    #6
    Lydeard likes this.
  8. 2011/10/26
    Lydeard

    Lydeard Well-Known Member Thread Starter

    Joined:
    2006/12/19
    Messages:
    119
    Likes Received:
    1
    You're a star Arie, changed the Path to the value you said it should be and all seems to be well with the Command Shell now, didn't need to create a new user account. Thank you so much. I can get back to original problem and my thread about IPSec Services now.
    I wonder what caused the Path to become corrupted, the Command Shell used to be working ok.
    Regards

    Graham
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.