5 replies
by ttrza1986 Accepted solution
by thumbsup2 Accepted solution
... this time, highlight Path statement and click edit. Inside, it should say, at the very minimum:
%SystemRoot%\system32;
On my system, %SystemRoot% translates to C:\Windows, but yours may be different.
Also make sure this is the first entry in the Path statement and nothing precedes it. Sometimes programs install themselves and put their path before the system path, which leads to exactly what you're seeing, not recognized as an internal or external command.
by ttrza1986 Accepted solution
by thumbsup2 Accepted solution
Often, older programs will install a path statement in the environment variable which confuses the system.
Try copying the contents of the path statement into Notepad and save the file. Then, remove all BUT the %SystemRoot%\system32 statement in the environment variable, reboot and test. If your command line works fine, one by one, add each additional path statement back into the environment variable (from your Notepad file), reboot and test again. You should eventually bump into the errant statement which is preventing your command line from working correctly (it will probably be the last one). At this point, you'll have to decide if that particular path statement is indeed needed (or maybe correct it).
Note: Each path statement in the environment variable is separated by a semi-colon (;) and no spaces between them. Make sure you add things back to the environment variable exactly the way they were copied out of it, into your Notepad file, until you find the bad one.
by 45geek Accepted solution
You say that you are a student and the object of your problem is in the computer lab.
My first thought would be that your tech support administrator for your school has locked you out of the command line (CLI). Which is a common practice for computer labs. An easy way to find out is type /? at the command prompt. If you get the same resopnse you are locked out, and attempting to change anything will be fruitless.
Although you can get by this on a couple of levels if you know how to script. Another test is to go to Start>Run> and type wbemtest and then click on OK. You should then get a window that allows you to see all of the available "Classes" installed on the machine if you know what you are doing. This is one piece of testing/development that is very difficult to lock out.
But again if you are typing ipconfig as all one word if you are not locked out you should get some output. Remember that typing just ipconfig with no switches will take you to the interactive mode. A more common command is with the /all switch. ( >ipconfig /all)
Have fun!
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending