command.com in WinXP

[MikeS]

I tried using command.com (50620 bytes, 29 Aug 2002 14:00) instead of cmd.exe. It gives "Incorrect
MS-DOS version" from both Start, Run and a cmd.exe prompt. Does anybody know how to use it within
WinXP? If this is not possible, why is it copied into ..\System32 during a standard WinXP Pro
install? Other old Win9x programs there (eg edit.com) run ok.

MikeS

 

[purplehaz]

It's just command, not command.com

Start, run, type in: command, hit enter.

 

[MikeS]

Thanks!

It's just command, not command.com

Start, run, type in: command, hit enter.

 

[Alex Nichol]

I tried using command.com (50620 bytes, 29 Aug 2002 14:00) instead of cmd.exe. It gives "Incorrect
MS-DOS version" from both Start, Run and a cmd.exe prompt. Does anybody know how to use it within
WinXP? If this is not possible, why is it copied into ..\System32 during a standard WinXP Pro
install?

The one supplied with the system should work at Start - Run. As it is
an alternative to cmd.exe it will not run from that. Check the file, in
windows\system32. Right click - Properties. It should date 23 August
2001 - an earlier one has been copied from an earlier version of windows
and will *not* work. And make sure you are not then trying to use it to
run an old version external command file - these might well not work

Command.com is a genuine 16 bit DOS command shell to run in the XP
emulation of the DOS environment. It is to the DOS 5.0 level - and does
*not* know about long file names. Generally use cmd.exe instead - a 32
bit shell that is more extensive but has essentially the same commands.

 

[purplehaz]

You're welcome.

Thanks!

 

[MikeS]

That was an ironic "Thanks!" - your suggestion does not address the
problem.
MikeS

 

[MikeS]

cmd.exe. It gives
"Incorrect

The one supplied with the system should work at Start - Run. As it is
an alternative to cmd.exe it will not run from that. Check the file, in
windows\system32. Right click - Properties. It should date 23 August
2001 - an earlier one has been copied from an earlier version of windows
and will *not* work. And make sure you are not then trying to use it to
run an old version external command file - these might well not work

Command.com is a genuine 16 bit DOS command shell to run in the XP
emulation of the DOS environment. It is to the DOS 5.0 level - and does
*not* know about long file names. Generally use cmd.exe instead - a 32
bit shell that is more extensive but has essentially the same commands.

I found another version in the i386 folder. This expanded to give the
same date as above but a
file size of 29130 bytes. It runs but pops up an error box (title: 16
bit MS-DOS subsystem)
with message "The NTVDM CPU has encountered an illegal instruction"
(etc). After that I tried the
larger version again and now it runs and gives the same 16bit subsystem
and error.

I have no idea where the other, larger version came from.
Any thoughts on the error message?

Thanks,
MikeS

 

[Alex Nichol]

It's just command, not command.com

Normally either will do

 

[Alex Nichol]

I found another version in the i386 folder. This expanded to give the
same date as above but a
file size of 29130 bytes. It runs but pops up an error box (title: 16
bit MS-DOS subsystem)
with message "The NTVDM CPU has encountered an illegal instruction"
(etc). After that I tried the
larger version again and now it runs and gives the same 16bit subsystem
and error.

I have no idea where the other, larger version came from.

Might be worth looking at the modification date and size in the
properties. The correct one for XP *ought* to be 23 Aug 2001 and 50620
bytes. Earlier ones would probably be bigger still (the one on a Win98
startup floppy is 92K) so I don't know where that 29130 came from,
unless you were looking at the compressed file in \i386

Any thoughts on the error message?

Something damaged. With such things the best course is usually to have
the CD in the drive (if it is a retail one rather than a recovery type)
and Start - Run the line
SFC /SCANNOW

 

[MikeS]

Might be worth looking at the modification date and size in the
properties. The correct one for XP *ought* to be 23 Aug 2001 and 50620
bytes. Earlier ones would probably be bigger still (the one on a Win98
startup floppy is 92K) so I don't know where that 29130 came from,
unless you were looking at the compressed file in \i386


Something damaged. With such things the best course is usually to have
the CD in the drive (if it is a retail one rather than a recovery type)
and Start - Run the line
SFC /SCANNOW

Problem solved. The 29130 byte file was command.co_ from \i386
renamed instead of expanded - don't know what I did. A second attempt
produced a file dated 23 Aug 2001 and 50620 bytes as you said. This
one runs correctly.

Thanks for the advice,
MikeS

 

[Alex Nichol]

Problem solved. The 29130 byte file was command.co_ from \i386
renamed instead of expanded - don't know what I did. A second attempt
produced a file dated 23 Aug 2001 and 50620 bytes as you said. This
one runs correctly.

Good to hear