Other names | MS-DOS Prompt, Windows Command Interpreter |
---|---|
Developer(s) | Seattle Computer Products, IBM, Microsoft, The Software Link, Datalight, Novell, Caldera |
Initial release | 1980 |
Written in | x86 assembly language [1] |
Operating system | |
Platform | 16-bit x86 |
Successor | cmd.exe |
Type | Command-line interpreter |
COMMAND.COM is the default command-line interpreter for MS-DOS, Windows 95, Windows 98 and Windows Me. In the case of DOS, it is the default user interface as well. It has an additional role as the usual first program run after boot ( init process). As a shell, COMMAND.COM has two distinct modes of operation: interactive mode and batch mode. Internal commands are commands stored directly inside the COMMAND.COM binary; thus, they are always available, but can only be executed directly from the command interpreter.
COMMAND.COM is the default command-line interpreter for MS-DOS, Windows 95, Windows 98 and Windows Me. In the case of DOS, it is the default user interface as well. [2] It has an additional role as the usual first program run after boot ( init process), hence being responsible for setting up the system by running the AUTOEXEC.BAT configuration file, and being the ancestor of all processes.[ citation needed]
COMMAND.COM's successor on OS/2 and Windows NT systems is cmd.exe, although COMMAND.COM is available in virtual DOS machines on IA-32 versions of those operating systems as well. The COMMAND.COM filename was also used by Disk Control Program [ de] (DCP), an MS-DOS derivative by the former East German VEB Robotron. [3]
COMMAND.COM is a DOS program. Programs launched from COMMAND.COM are DOS programs that use the DOS API to communicate with the disk operating system. The compatible command processor under FreeDOS is sometimes also named FreeCom.
As a shell, COMMAND.COM has two distinct modes of operation. The first is interactive mode, in which the user types commands which are then executed immediately. The second is batch mode, which executes a predefined sequence of commands stored as a text file with the .BAT extension.
Internal commands are commands stored directly inside the COMMAND.COM binary. Thus, they are always available but can only be executed directly from the command interpreter.
All commands are executed after the ↵ Enter key is pressed at the end of the line. COMMAND.COM is not case-sensitive, meaning commands can be typed in any mixture of upper and lower case.
ECHO ON
) or not (ECHO OFF
). Also displays text on the screen (ECHO text
).HILOAD
in
DR DOS).Control structures are mostly used inside batch files, although they can also be used interactively. [5] [4]
:likethis
).%0
with %1
, %1
with %2
, etc.).On exit, all external commands submit a return code (a value between 0 and 255) to the calling program. Most programs have a certain convention for their return codes (for instance, 0 for a successful execution). [6] [7] [8] [9]
If a program was invoked by COMMAND.COM, the internal IF command with its ERRORLEVEL conditional can be used to test on error conditions of the last invoked external program.[ citation needed]
Under COMMAND.COM, internal commands do not establish a new value.[ citation needed]
Batch files for COMMAND.COM can have four kinds of variables:
Because DOS is a single-tasking operating system, piping is achieved by running commands sequentially, redirecting to and from a temporary file.[ citation needed] COMMAND.COM makes no provision for redirecting the standard error channel.[ citation needed]
command < filename
command > filename
command >> filename
command1 | command2
command1 ¶ command2
&
separator for compatibility with the cmd syntax in OS/2 and the Windows NT family.
[11] (cmd does not support the ¶ separator.)Generally, the command line length in interactive mode is limited to 126 characters. [12] [13] [14] In MS-DOS 6.22, the command line length in interactive mode is limited to 127 characters.[ citation needed]
{{
cite book}}
: |work=
ignored (
help) (NB. The provided link points to a HTML-converted version of the NWDOSTIP.TXT
, which is part of the MPDOSTIP.ZIP
collection.)
[1]
{{
cite book}}
: |work=
ignored (
help) (NB. BATTIPS.TXT is part of MPDOSTIP.ZIP. The provided link points to an HTML-converted older version of the BATTIPS.TXT file.)
[2]
[...] Multiple Commands: You can type several commands on the same command line, separated by a caret [^]. For example, if you know you want to copy all of your .TXT files to drive A: and then run CHKDSK to be sure that drive A's file structure is in good shape, you could enter the following command:
C:\>COPY *.TXT A: ^ CHKDSK A:
You may put as many commands on the command line as you wish, as long as the total length of the command line does not exceed 511 characters. You can use multiple commands in aliases and batch files as well as at the command line. If you don't like using the default command separator, you can pick another character using theSETDOS /C
command or the CommandSep directive in 4DOS.INI. [...]SETDOS /C:
(Compound character) This option sets the character used for separating multiple commands on the same line. The default is the caret [^]. You cannot use any of the redirection characters [<>|], or the blank, tab, comma, or equal sign as the command separator. The command separator is saved by SETLOCAL and restored by ENDLOCAL. This example changes the separator to a tilde [~]:C:\>SETDOS /C~
(You can specify either the character itself, or its ASCII code as a decimal number, or a hexadecimal number preceded by 0x.) [...] CommandSep = c (^): This is the character used to separate multiple commands on the same line. [...] Special Character Compatibility: If you use two or more of our products, or if you want to share aliases and batch files with users of different products, you need to be aware of the differences in three important characters: the Command Separator [...], the Escape Character [...], and the Parameter Character [...]. The default values of each of these characters in each product is shown in the following chart: [...] Product, Separator, Escape Parameter [...] 4DOS: ^, ↑, & [...] 4OS2, 4NT, Take Command: &, ^, $ [...] (The up-arrow [↑] represents the ASCII Ctrl-X character, numeric value 24.) [...]— Brothers, Hardin; Rawson, Tom; Conn, Rex C.; Paul, Matthias R.; Dye, Charles E.; Georgiev, Luchezar I. (2002-02-27). 4DOS 8.00 online help.
{{
cite book}}
: |work=
ignored (
help) (NB. MSDOSTIP.TXT is part of MPDOSTIP.ZIP, maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the MSDOSTIP.TXT file.)
[4]
4DOS5TIP.TXT
file, which is part of the MPDOSTIP.ZIP
collection.)
[5]
[...] all MS-DOS versions prior to Windows 95 [...] used a COM style COMMAND.COM file which has a special signature at the start of the file [...] queried by the MS-DOS BIOS before it loads the shell, but not by the DR-DOS BIOS [...] COMMAND.COM would [...] check that it is running on the "correct" DOS version, so if you would load their COMMAND.COM under DR-DOS, you would receive a "Bad version" error message and their COMMAND.COM would exit, so DR-DOS would [...] display an error message "Bad or missing command interpreter" (if DR-DOS was trying to load the SHELL= command processor after having finished CONFIG.SYS processing). In this case, you could enter the path to a valid DR-DOS COMMAND.COM (C:\DRDOS\COMMAND.COM) and everything was fine. Now, things have changed since MS-DOS 7.0 [...] COMMAND.COM has internally become an EXE style file, so there is no magic [...] signature [...] to check [...] thus no way for DR-DOS to rule out an incompatible COMMAND.COM. Further, their COMMAND.COM no longer does any version checks, but [...] does not work under DR-DOS [...] just crashes [...] the PC DOS COMMAND.COM works fine under DR-DOS [...]
Paul, Matthias R. (2004-06-17). "Re: Random Lockups with DR-DOS 7.03". FidoNet conference: ALT_DOS. Archived from the original on 2019-04-28. Retrieved 2019-04-28.
Other names | MS-DOS Prompt, Windows Command Interpreter |
---|---|
Developer(s) | Seattle Computer Products, IBM, Microsoft, The Software Link, Datalight, Novell, Caldera |
Initial release | 1980 |
Written in | x86 assembly language [1] |
Operating system | |
Platform | 16-bit x86 |
Successor | cmd.exe |
Type | Command-line interpreter |
COMMAND.COM is the default command-line interpreter for MS-DOS, Windows 95, Windows 98 and Windows Me. In the case of DOS, it is the default user interface as well. It has an additional role as the usual first program run after boot ( init process). As a shell, COMMAND.COM has two distinct modes of operation: interactive mode and batch mode. Internal commands are commands stored directly inside the COMMAND.COM binary; thus, they are always available, but can only be executed directly from the command interpreter.
COMMAND.COM is the default command-line interpreter for MS-DOS, Windows 95, Windows 98 and Windows Me. In the case of DOS, it is the default user interface as well. [2] It has an additional role as the usual first program run after boot ( init process), hence being responsible for setting up the system by running the AUTOEXEC.BAT configuration file, and being the ancestor of all processes.[ citation needed]
COMMAND.COM's successor on OS/2 and Windows NT systems is cmd.exe, although COMMAND.COM is available in virtual DOS machines on IA-32 versions of those operating systems as well. The COMMAND.COM filename was also used by Disk Control Program [ de] (DCP), an MS-DOS derivative by the former East German VEB Robotron. [3]
COMMAND.COM is a DOS program. Programs launched from COMMAND.COM are DOS programs that use the DOS API to communicate with the disk operating system. The compatible command processor under FreeDOS is sometimes also named FreeCom.
As a shell, COMMAND.COM has two distinct modes of operation. The first is interactive mode, in which the user types commands which are then executed immediately. The second is batch mode, which executes a predefined sequence of commands stored as a text file with the .BAT extension.
Internal commands are commands stored directly inside the COMMAND.COM binary. Thus, they are always available but can only be executed directly from the command interpreter.
All commands are executed after the ↵ Enter key is pressed at the end of the line. COMMAND.COM is not case-sensitive, meaning commands can be typed in any mixture of upper and lower case.
ECHO ON
) or not (ECHO OFF
). Also displays text on the screen (ECHO text
).HILOAD
in
DR DOS).Control structures are mostly used inside batch files, although they can also be used interactively. [5] [4]
:likethis
).%0
with %1
, %1
with %2
, etc.).On exit, all external commands submit a return code (a value between 0 and 255) to the calling program. Most programs have a certain convention for their return codes (for instance, 0 for a successful execution). [6] [7] [8] [9]
If a program was invoked by COMMAND.COM, the internal IF command with its ERRORLEVEL conditional can be used to test on error conditions of the last invoked external program.[ citation needed]
Under COMMAND.COM, internal commands do not establish a new value.[ citation needed]
Batch files for COMMAND.COM can have four kinds of variables:
Because DOS is a single-tasking operating system, piping is achieved by running commands sequentially, redirecting to and from a temporary file.[ citation needed] COMMAND.COM makes no provision for redirecting the standard error channel.[ citation needed]
command < filename
command > filename
command >> filename
command1 | command2
command1 ¶ command2
&
separator for compatibility with the cmd syntax in OS/2 and the Windows NT family.
[11] (cmd does not support the ¶ separator.)Generally, the command line length in interactive mode is limited to 126 characters. [12] [13] [14] In MS-DOS 6.22, the command line length in interactive mode is limited to 127 characters.[ citation needed]
{{
cite book}}
: |work=
ignored (
help) (NB. The provided link points to a HTML-converted version of the NWDOSTIP.TXT
, which is part of the MPDOSTIP.ZIP
collection.)
[1]
{{
cite book}}
: |work=
ignored (
help) (NB. BATTIPS.TXT is part of MPDOSTIP.ZIP. The provided link points to an HTML-converted older version of the BATTIPS.TXT file.)
[2]
[...] Multiple Commands: You can type several commands on the same command line, separated by a caret [^]. For example, if you know you want to copy all of your .TXT files to drive A: and then run CHKDSK to be sure that drive A's file structure is in good shape, you could enter the following command:
C:\>COPY *.TXT A: ^ CHKDSK A:
You may put as many commands on the command line as you wish, as long as the total length of the command line does not exceed 511 characters. You can use multiple commands in aliases and batch files as well as at the command line. If you don't like using the default command separator, you can pick another character using theSETDOS /C
command or the CommandSep directive in 4DOS.INI. [...]SETDOS /C:
(Compound character) This option sets the character used for separating multiple commands on the same line. The default is the caret [^]. You cannot use any of the redirection characters [<>|], or the blank, tab, comma, or equal sign as the command separator. The command separator is saved by SETLOCAL and restored by ENDLOCAL. This example changes the separator to a tilde [~]:C:\>SETDOS /C~
(You can specify either the character itself, or its ASCII code as a decimal number, or a hexadecimal number preceded by 0x.) [...] CommandSep = c (^): This is the character used to separate multiple commands on the same line. [...] Special Character Compatibility: If you use two or more of our products, or if you want to share aliases and batch files with users of different products, you need to be aware of the differences in three important characters: the Command Separator [...], the Escape Character [...], and the Parameter Character [...]. The default values of each of these characters in each product is shown in the following chart: [...] Product, Separator, Escape Parameter [...] 4DOS: ^, ↑, & [...] 4OS2, 4NT, Take Command: &, ^, $ [...] (The up-arrow [↑] represents the ASCII Ctrl-X character, numeric value 24.) [...]— Brothers, Hardin; Rawson, Tom; Conn, Rex C.; Paul, Matthias R.; Dye, Charles E.; Georgiev, Luchezar I. (2002-02-27). 4DOS 8.00 online help.
{{
cite book}}
: |work=
ignored (
help) (NB. MSDOSTIP.TXT is part of MPDOSTIP.ZIP, maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the MSDOSTIP.TXT file.)
[4]
4DOS5TIP.TXT
file, which is part of the MPDOSTIP.ZIP
collection.)
[5]
[...] all MS-DOS versions prior to Windows 95 [...] used a COM style COMMAND.COM file which has a special signature at the start of the file [...] queried by the MS-DOS BIOS before it loads the shell, but not by the DR-DOS BIOS [...] COMMAND.COM would [...] check that it is running on the "correct" DOS version, so if you would load their COMMAND.COM under DR-DOS, you would receive a "Bad version" error message and their COMMAND.COM would exit, so DR-DOS would [...] display an error message "Bad or missing command interpreter" (if DR-DOS was trying to load the SHELL= command processor after having finished CONFIG.SYS processing). In this case, you could enter the path to a valid DR-DOS COMMAND.COM (C:\DRDOS\COMMAND.COM) and everything was fine. Now, things have changed since MS-DOS 7.0 [...] COMMAND.COM has internally become an EXE style file, so there is no magic [...] signature [...] to check [...] thus no way for DR-DOS to rule out an incompatible COMMAND.COM. Further, their COMMAND.COM no longer does any version checks, but [...] does not work under DR-DOS [...] just crashes [...] the PC DOS COMMAND.COM works fine under DR-DOS [...]
Paul, Matthias R. (2004-06-17). "Re: Random Lockups with DR-DOS 7.03". FidoNet conference: ALT_DOS. Archived from the original on 2019-04-28. Retrieved 2019-04-28.