Re: CMD
  Home FAQ Contact Sign in
microsoft.public.windowsxp.configuration_manage only
 
Advanced search
POPULAR GROUPS

more...

... owsxp.configuration_manage Profile…
 Up
Re: CMD         


Date: Aug 25, 2006 10:40

"[I AM] Tainted" discussions.microsoft.com> wrote
> when i try and open the command prompt it says "cmd is not a valid win32
> aplication" does anyone know how to fix this
> --
> Excuse Me, You''re Stepping On My Eyeball.

Try this as well:

cmd.exe

If cmd.exe works but cmd does not, then you probably have a file called cmd.com somewhere (in the path) which is being run instead.
You will really want to find it and delete it since it's most likely to be bad.

--
Alec S.
news/alec->synetech/cjb/net
29 Comments
Re: CMD         


Author: Will Denny
Date: Aug 25, 2006 12:11

Hi

I've never come across cmd.com - only cmd.exe. Where did you hear about
cmd.com?

--

Will Denny
MS-MVP Windows Shell/User
Please reply to the News Groups
Show full article (0.81Kb)
28 Comments
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 13:37

Will,

From my standard post on cmd.com that I have had for over a YEAR...

You have a trojan/virus/worm. cmd.com is *NOT* an XP file.

cmd.exe and command.com are legitimate Windows XP files.

You have a trojan/virus/worm. cmd.exe is not part of the 16 bit MS-DOS
Subsystem. autoexec.nt and config.nt have nothing to do with cmd.exe.

When you type cmd in the Start | Run box, XP finds cmd.com instead of
cmd.exe. When a command is typed without an extension, XP looks for the
.com extension first before it looks for the .exe extension, if it finds
cmd.com, it will not even look for cmd.exe. Because XP finds cmd.com XP
thinks that it needs autoexec.nt and config.nt to run cmd.com.

cmd.com is *NOT* an XP file, it's added by a trojan/worm/virus.

If you were to type cmd.exe in the Start | Run box, cmd.exe might open if
the trojan/worm/virus hasn't rendered it useless.

UPDATE your antivirus software and run a complete scan.

UPDATE whatever anti-spyware applications that you have and run a full
system scan with each one.
Show full article (2.96Kb)
6 Comments
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 13:40

From
Sat, Jun 11 2005 3:06 pm
http://groups.google.com/group/microsoft.public.windowsxp.general/browse_thread/...#877c65797df5e18d

"cmd.com" author:wesley author:vogel
http://groups.google.com/groups?q=%%22cmd.com%%22+author%%3Awesley+author%%3Avogel&start...&

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:%%23f9WYpHyGHA.3492@TK2MSFTNGP02.phx.gbl,
Will Denny mvps.org> hunted and pecked:
> Hi
>
> I've never come across cmd.com - only cmd.exe. Where did you hear about
> cmd.com?
>
> --...
Show full article (1.49Kb)
20 Comments
Re: CMD         


Author: Will Denny
Date: Aug 25, 2006 14:55

Exactly. So I've got no idea why cmd.com can be a legit file.

--

Will Denny
MS-MVP Windows Shell/User
Please reply to the News Groups

"Wesley Vogel" <123WVogel955@comcast.net> wrote in message
news:%%23ihzkYIyGHA.4912@TK2MSFTNGP03.phx.gbl...
> Will,
>
> From my standard post on cmd.com that I have had for over a YEAR...
>
> You have a trojan/virus/worm. cmd.com is *NOT* an XP file.
>
> cmd.exe and command.com are legitimate Windows XP files.
3 Comments
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 15:35

cmd.com is NOT a legit file. But if you happen to be unlucky enough to have
cmd.com, typing cmd in the Run command causes problems because cmd.exe will
NOT open. All you get is some error message about cmd.com.

Like one of these...

C:\WINDOWS\SYSTEM32\cmd.com
The NTVDM CPU has encountered an illegal instruction.CS:0549 IP:010c4 f6 06
a9 02 choose 'close' to terminate the application.

C:/WINDOWS/system32/cmd.com
C:/WINDOWS/SYSTEM32/AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'close' to terminate the
application.

C:/Windows/ system32/cmd.com
The NTVDM CPU has encountered an illegal instuction. CS:0557 IP:ffe4 OP:fe
ff 1d 09 21 Choose 'close' to terminate the application;" choosing "close"
or "ignore" both cause the application to exit.

C: /WINDOWS/system32/cmd.com
C: /WINDOWS/SYSTEM32/AUTOEXEC.NT. The system file is not suitable, in order
to implement applications for MS-DOS or Microsoft Windows. Click on
"Button", in order to terminate application.
Show full article (2.31Kb)
1 Comment
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 16:56

Regarding this line...

These files contain the string MZ so that this worm can disable the
following Windows tool applications:
from....
WORM_ALCAN.A - Technical details
http://www.trendmicro.com/vinfo/virusencyclo/default5.asp?VName=WORM_ALCAN.A&VSect...

It meant that the .com files mentioned have the MZ string.

I.E. CMD.COM, NETSTAT.COM, PING.COM, REGEDIT.COM, TASKKILL.COM,TASKLIST.COM
and TRACERT.COM

Com programs do not normally have the MZ string.

First line of cmd.exe...
MZ
1 Comment
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 17:08


Mark Zbikowski (an early DOS programmer whose initials are in EXE files)

Acronym Finder Search: What does MZ stand for?
http://www.acronymfinder.com/af-query.asp?Acronym=MZ&String=exact&p=ol


Another commonly used method to identify if the program is an EXE file is
looking for the MZ string at the beginning of the EXE file header. MZ are
the initials of Mark Zbikowsky, the programmer who designed the EXE file
format.

Tutorials - The Memory Resident Virus Primer
http://vx.netlux.org/lib/static/vdat/tumisc51.htm


Mark Zbikowski (born March 21, 1956 in Detroit, Michigan) is a Microsoft
Architect. He started working at the company only a few years after its
inception, leading efforts in MS-DOS, OS/2, Cairo and Windows NT. In 2006 he
was honored for 25 years of service with the company, the first employee to
reach this milestone other than Bill Gates and Steve Ballmer.
Show full article (3.52Kb)
no comments
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 18:19

I copied those errors from posts and did not catch the incorrect paths.
I.e. the forward slashes. A couple of those error messages were translated
from other languages, that's why they look even goofier.

Like one of these...

C:\WINDOWS\SYSTEM32\cmd.com
The NTVDM CPU has encountered an illegal instruction.CS:0549 IP:010c4 f6 06
a9 02 choose 'close' to terminate the application.

C:\WINDOWS\system32\cmd.com
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'close' to terminate the
application.

C:\Windows\system32\cmd.com
The NTVDM CPU has encountered an illegal instruction. CS:0557 IP:ffe4 OP:fe
ff 1d 09 21 Choose 'close' to terminate the application;" choosing "close"
or "ignore" both cause the application to exit.

C:\WINDOWS\system32\cmd.com
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable, in order
to implement applications for MS-DOS or Microsoft Windows. Click on
"Button", in order to terminate application.
Show full article (3.79Kb)
no comments
Re: CMD         


Author: Wesley Vogel
Date: Aug 25, 2006 21:17

Try this.

I just did it myself.

Start | Run | Type: system32 | Click OK |

Scroll down to the bottom of the System32 folder.

Right click, point to New and select Text Document.

Rename it to cmd.com

Click YES to this message...

---------------------------
Rename
---------------------------
If you change a file name extension, the file may become unusable.

Are you sure you want to change it?
---------------------------
Yes No
---------------------------

cmd.com now exists in System32, with the DOS looking icon and 0 bytes.

You can check its Properties.

General tab
Type of file: MS-DOS Application
Show full article (1.87Kb)
no comments
1 2 3