COMMAND.COM is the defaultcommand-line interpreter forMS-DOS,Windows 95,Windows 98 andWindows 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 afterboot (init process). As a shell, COMMAND.COM has two distinct modes of operation:interactive mode andbatch mode. Internal commands are commands stored directly inside the COMMAND.COMbinary; thus, they are always available, but can only be executed directly from the command interpreter.[citation needed]
COMMAND.COM is a DOS program. Programs launched from COMMAND.COM are DOS programs that use theDOS API to communicate with the disk operating system. The compatible command processor underFreeDOS is sometimes also calledFreeCom.
As a shell, COMMAND.COM has two distinct modes of operation. The first isinteractive mode, in which the user types commands which are then executed immediately. The second isbatch 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.
Copies one file to another (if the destination file already exists, MS-DOS asks whether to replace it). (See alsoXCOPY, an external command that could also copy directory trees).
Deletes a file. When used on a directory, deletes all files inside the directory only. In comparison, the external commandDELTREE deletes all subdirectories and files inside a directory as well as the directory itself.
On exit, all external commands submit areturn 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).[5][6][7][8]
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:
Environment variables: These have the%VARIABLE% form and are associated with values with the SET statement. Before DOS 3 COMMAND.COM will only expand environment variables in batch mode; that is, not interactively at the command prompt.[citation needed]
Replacement parameters: These have the form%0,%1...%9, and initially contain the command name and the first ninecommand-line parameters passed to the script (e.g., if the invoking command wasmyscript.bat John Doe, then%0 is "myscript.bat",%1 is "John" and%2 is "Doe"). The parameters to the right of the ninth can be mapped into range by using the SHIFT statement.[citation needed]
Loop variables: Used in loops, they have the%%a format when run in batch files. These variables are defined solely within a specific FOR statement, and iterate over a certain set of values defined in that FOR statement.[citation needed]
Commands separated by ASCII-20 (¶, invoked byCtrl+T) are executed in sequence (chaining of commands).[3] In other words, firstcommand1 is executed until termination, thencommand2.[3] This is an undocumented feature in COMMAND.COM ofMS-DOS/PC DOS 5.0 and higher.[3] It is also supported by COMMAND.COM of the Windows NT family as well as by DR-DOS 7.07. All versions of DR-DOS COMMAND.COM already supported a similar internal function utilizing an exclamation mark (!) instead (a feature originally derived fromConcurrent DOS andMultiuser DOS) - in the single-user line this feature was only available internally (in built-in startup scripts like "!DATE!TIME") and indirectly throughDOSKEY's $T parameter to avoid problems with ! as a valid filename character.[3]4DOS supports a configurable command line separator (4DOS.INI CommandSep= or SETDOS /C), which defaults to ^.[10] COMMAND.COM in newer versions of Windows NT also supports an& separator for compatibility with the cmd syntax in OS/2 and the Windows NT family.[10] (cmd does not support the ¶ separator.)
Generally, the command line length in interactive mode is limited to 126 characters.[11][12][13] InMS-DOS 6.22, the command line length in interactive mode is limited to 127 characters.[citation needed]
The message "Loading COMMAND.COM" can be seen on aHUD view of theTerminator and the internal viewport ofRoboCop when he reboots.[citation needed]
In the animated children's TV seriesReBoot, which takes place inside computers, the leader of a system (the equivalent of a city) is called the COMMAND.COM.[citation needed]
^Kurth, Rüdiger; Groß, Martin; Hunger, Henry (2016-11-29) [2007]."Betriebssystem DCP".www.robotrontechnik.de (in German).Archived from the original on 2019-04-03. Retrieved2019-04-28.
^Paul, Matthias R. (1997-05-01) [1993-10-01].BATTIPs — Tips & Tricks zur Programmierung von Batchjobs (in German). MPDOSTIP. Kapitel 7: ERRORLEVEL abfragen.Archived from the original on 2017-08-23. Retrieved2017-08-23. (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 in4DOS.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.) [...]
^Paul, Matthias R. (1997-07-01) [1994-01-01].MSDOSTIPs — Tips für den Umgang mit MS-DOS 5.0-7 (in German). MPDOSTIP.Archived from the original on 2017-08-22. Retrieved2013-10-25. (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]
^Paul, Matthias R. (1997-05-01) [1995-03-01]."Hinweise zu JPSofts 4DOS 5.5b/c, 5.51, 5.52a und NDOS".MPDOSTIP (in German).Archived from the original on 2016-11-04. Retrieved2015-05-08. (NB. The provided link points to a HTML-converted version of the4DOS5TIP.TXT file, which is part of theMPDOSTIP.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 [...]
