command prompt problems

[Al]

When I type a command such as "ping" I receive the response 'ping' is not
recognized as an internal or external command, operable program or batch
file. However a command such as "dir" works fine.

Now when I go start--run--ping I get the correct response but the window
disappears so quickly I have trouble reading it.

Everything else seems to work okay.

 

[David H. Lipman]

You may have a path problem.

Did you use COMMAND or CMD ?

Dave



| When I type a command such as "ping" I receive the response 'ping' is not
| recognized as an internal or external command, operable program or batch
| file. However a command such as "dir" works fine.
|
| Now when I go start--run--ping I get the correct response but the window
| disappears so quickly I have trouble reading it.
|
| Everything else seems to work okay.
|
|

 

[Al]

Both cmd and command open the prompt window. Then when I type ping i get
'ping' is not recognized as an internal or external command, operable
program or batch file.
If I go start-- run--ping the the command appears to work but the window
disappears quickly rather than remaining open.

 

[David H. Lipman]

CMD and COMMAND may both open a command prompt but they are two different interpreters.

If you open a command prompt and type SET, does the PATH variable include...
PATH=C:\WINDOWS\system32;C:\WINNT;C:\WINNT\System32\Wbem ????


In addition:
If you post to UseNet with your TRUE, not a munged, email address then you have now invited
the Swen worm to visit you.

The Swen is news spelled backwards. The reason it is called this is because the Swen worm
harvests email addresses from UseNet News Groups. It has an engine that allows it to post
itself to UseNet News Groups and well as it has its own email engine. From the list of
email addresses that it has harvested, it will then email itself to those addresses.

Dave



| Both cmd and command open the prompt window. Then when I type ping i get
| 'ping' is not recognized as an internal or external command, operable
| program or batch file.
| If I go start-- run--ping the the command appears to work but the window
| disappears quickly rather than remaining open.
| | > You may have a path problem.
| >
| > Did you use COMMAND or CMD ?
| >
| > Dave
| >
| >
| >
| > | > | When I type a command such as "ping" I receive the response 'ping' is
| not
| > | recognized as an internal or external command, operable program or batch
| > | file. However a command such as "dir" works fine.
| > |
| > | Now when I go start--run--ping I get the correct response but the
| window
| > | disappears so quickly I have trouble reading it.
| > |
| > | Everything else seems to work okay.
| > |
| > |
| >
| >
|
|

 

[Al]

No it doesn't. Instead it refers to Roxio Shared. I think I know what to
try next. Thanks.
Also thanks for the email address warning.

 

[Al]

OOPS. Uninstalling roxio cdcreator didn't fix the problem. What gives?
How do I permanently change the path? How did this happen anyway? Just from
installing Roxio products?

 

[Wesley Vogel]

David;
cmd.exe = Windows Command Processor
command.com = MS-DOS Prompt
===========
CMD.EXE or COMMAND.COM

Windows NT comes with two "command line shells" -- one called CMD.EXE and the
other called
COMMAND.COM. If you're wondering which one to use, following information might
help:
CMD.EXE is the Windows NT's native command prompt (or shell), which means it is
more portable
among different hardware platforms. For example, if you type SET and press
ENTER inside a CMD.EXE
prompt, you'll notice that CMD.EXE exposes more environment variables than
COMMAND.COM. On the other hand, COMMAND.COM is the more "MS-DOS compatible"
version of the two shells. For example, this shell will call AUTOEXEC.NT and
CONFIG.NT (located in the SYSTEM32 directory inside your Windows NT directory)
just like MS-DOS used to call AUTOEXEC.BAT and CONFIG.SYS.

So, if you're having trouble running your old DOS command line programs from
Windows NT, try
running them inside a COMMAND.COM shell, not CMD.EXE.

 

[David H. Lipman]

I don't have XP in front of me, I have Win2K but it is similar enough that if I tell 'ya how
to do it in Win2K it should give you an ide how to do it in XP.

Right Click "My Computer" --> Advanced --> Environmental variables --> System variables -->
path --> edit
insert - C:\WINDOWS\system32;C:\WINNT;C:\WINNT\System32\Wbem
In the beginning of the string.

Dave



| OOPS. Uninstalling roxio cdcreator didn't fix the problem. What gives?
| How do I permanently change the path? How did this happen anyway? Just from
| installing Roxio products?
| | > No it doesn't. Instead it refers to Roxio Shared. I think I know what to
| > try next. Thanks.
| > Also thanks for the email address warning.
| > | > > CMD and COMMAND may both open a command prompt but they are two
| different
| > interpreters.
| > >
| > > If you open a command prompt and type SET, does the PATH variable
| > include...
| > > PATH=C:\WINDOWS\system32;C:\WINNT;C:\WINNT\System32\Wbem ????
| > >
| > >
| > > In addition:
| > > If you post to UseNet with your TRUE, not a munged, email address then
| you
| > have now invited
| > > the Swen worm to visit you.
| > >
| > > The Swen is news spelled backwards. The reason it is called this is
| > because the Swen worm
| > > harvests email addresses from UseNet News Groups. It has an engine that
| > allows it to post
| > > itself to UseNet News Groups and well as it has its own email engine.
| > From the list of
| > > email addresses that it has harvested, it will then email itself to
| those
| > addresses.
| > >
| > > Dave
| > >
| > >
| > >
| > > | > > | Both cmd and command open the prompt window. Then when I type ping i
| > get
| > > | 'ping' is not recognized as an internal or external command, operable
| > > | program or batch file.
| > > | If I go start-- run--ping the the command appears to work but the
| > window
| > > | disappears quickly rather than remaining open.
| > > | | > > | > You may have a path problem.
| > > | >
| > > | > Did you use COMMAND or CMD ?
| > > | >
| > > | > Dave
| > > | >
| > > | >
| > > | >
| > > | > | > > | > | When I type a command such as "ping" I receive the response 'ping'
| > is
| > > | not
| > > | > | recognized as an internal or external command, operable program or
| > batch
| > > | > | file. However a command such as "dir" works fine.
| > > | > |
| > > | > | Now when I go start--run--ping I get the correct response but the
| > > | window
| > > | > | disappears so quickly I have trouble reading it.
| > > | > |
| > > | > | Everything else seems to work okay.
| > > | > |
| > > | > |
| > > | >
| > > | >
| > > |
| > > |
| > >
| > >
| >
| >
|
|

 

[Alex Nichol]

Both cmd and command open the prompt window. Then when I type ping i get
'ping' is not recognized as an internal or external command, operable
program or batch file.

At that point give PATH

It should start with
PATH=C:\WINDOWS\SYSTEM32;C:\windows;C:\windows\SYSTEM32\WBEM
and so on.

If it does not, look in the windows\system32\autoexec.nt file to see if
an erroneous PATH has got in there, and also go to Control Panel -
System - Advanced and click Environmental variables, to make sure the
PATH defined there is also correct

 

[Torgeir Bakken (MVP)]

I don't have XP in front of me, I have Win2K but it is similar enough that if I tell 'ya how
to do it in Win2K it should give you an ide how to do it in XP.

Right Click "My Computer" --> Advanced --> Environmental variables --> System variables -->
path --> edit
insert - C:\WINDOWS\system32;C:\WINNT;C:\WINNT\System32\Wbem
In the beginning of the string.

Hi

Note that the path string above erroneously uses a mix of C:\WINDOWS and C:\WINNT as to what
folder Windows is installed to.

It is better to use the same original values that a OS install put in the path (when editing the
path through the "System variables" GUI that David lists above):

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM

This way you don't need to think about what folder the OS is installed to.

 

[David H. Lipman]

Torgeir:

Thanks for fixing my screw-up !

Dave



| "David H. Lipman" wrote:
|
| > I don't have XP in front of me, I have Win2K but it is similar enough that if I tell 'ya
how
| > to do it in Win2K it should give you an ide how to do it in XP.
| >
| > Right Click "My Computer" --> Advanced --> Environmental variables --> System
variables -->
| > path --> edit
| > insert - C:\WINDOWS\system32;C:\WINNT;C:\WINNT\System32\Wbem
| > In the beginning of the string.
|
| Hi
|
| Note that the path string above erroneously uses a mix of C:\WINDOWS and C:\WINNT as to
what
| folder Windows is installed to.
|
| It is better to use the same original values that a OS install put in the path (when
editing the
| path through the "System variables" GUI that David lists above):
|
| %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM
|
| This way you don't need to think about what folder the OS is installed to.
|
| --
| torgeir
| Microsoft MVP Scripting and WMI, Porsgrunn Norway
| Administration scripting examples and an ONLINE version of the 1328 page Scripting Guide:
| http://www.microsoft.com/technet/scriptcenter
|
|