Command Prompt not recognizing some commands

Hello,

I've been playing around with VDMSound (now uninstalled) and DOSBox (also uninstalled) this weekend trying to get an old DOS program working.

This morning I'm back to work and the command line to not working correctly. Things like Path and DIR seem to work ok however so far "Net use" and "Ping" are not working! ARGH!

What have I done!

The only changes to the laptop over the weekend are DOSBox 0.73 and VDMSound 2.1.0. VMDSound I've worked with for years and never had any issues however DOSBox is new to me. I'm thinking its done something but what?

Any ideas..... I need this ASAP as alot of my work is though the command line.
Ace_Crosley_79Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve KnightIT ConsultancyCommented:
Most likely, sounds like your path has been messed up?  If you just type PATH at the CMD.EXE prompt does it include c:\windows\system32;c:\windows etc. (or wherever your windows dir is).

If you open a cmd.exe prompt and do
C:
cd \windows\system32
net use

If your path is hosed easy enough to fix,

Properies of my computer
Advanced
Environment variables
The path one by default should include these at least:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem

Steve
0
Ace_Crosley_79Author Commented:
OK this is wired! %systemroot%system32 is in the paths however so is everything you would expect! When in c:\windows\system32 net use is working. Drop out (even though its in the paths) and Net use stops working!

I can't understand when system32 is in the path and commands still don't work?

I'm giving this 2 more hours before I ghost this laptop....
Path.JPG
0
Steve KnightIT ConsultancyCommented:
Is Systemroot showing in your environment as those should be replaced by the time you see them in a path or set command.  Type

SET

to see them all.

Steve
0
Ace_Crosley_79Author Commented:
yes systemroot=c:\windows
0
Steve KnightIT ConsultancyCommented:
Interesting.  could you dump out set to a text file for me... set > set.txt

As I said typing SET should show the variables as the full path, not %systemroot% etc. as they should have been expanded by then.

The length should be OK as you can have upto nearly 1Kb and that is about 1/4 of that... maybe worth just editing the path in the GUI in case some dodgy chars or something have got in there...

It SHOULD show in the system variables part as the full "c:\windows\system32" etc. and when you click Edit it can show as "%Systemroot%" etc.  Sounds like somehow the %Systemroot% bit has got saved in there wrongly.... perhaps a dodgy uninstaller there messed it up.

Steve
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft DOS

From novice to tech pro — start learning today.