COMMAND.COM

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Template:Short description Script error: No such module "redirect hatnote". Script error: No such module "Distinguish". Template:Use list-defined references Script error: No such module "Unsubst". Template:Use dmy dates Script error: No such module "Infobox".Template:Template other Script error: No such module "Check for unknown parameters".Script error: No such module "Check for conflicting parameters".

File:Microsoft Windows 95 Version 4.00.1111 command.com MS-DOS Prompt 492x259.png
Template:Mono running in a Windows console on Windows 95 (MS-DOS Prompt)

Template:Mono 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, Template:Mono has two distinct modes of operation: interactive mode and batch mode. Internal commands are commands stored directly inside the Template:Mono binary; thus, they are always available, but can only be executed directly from the command interpreter.Script error: No such module "Unsubst".

Description

Template:Mono'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 Template:Mono filename was also used by Template:Ill (DCP), an MS-DOS derivative by the former East German VEB Robotron.[1]

Template:Mono is a DOS program. Programs launched from Template:Mono are DOS programs that use the DOS API to communicate with the disk operating system. The compatible command processor under FreeDOS is sometimes also called FreeCom.

Operating modes

As a shell, Template:Mono 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.

Script error: No such module "anchor".Internal commands

Internal commands are commands stored directly inside the Template:Mono binary. Thus, they are always available but can only be executed directly from the command interpreter.

All commands are executed after the Template:Keypress key is pressed at the end of the line. Template:Mono is not case-sensitive, meaning commands can be typed in any mixture of upper and lower case.

[[BREAK (DOS command)|Template:Mono]]
Controls the handling of program interruption with Template:Keypress or Template:Keypress.
[[CHCP (command)|Template:Mono]]
Displays or changes the current system code page.
[[CHDIR|Template:Mono, Template:Mono]]
Changes the current working directory or displays the current directory.
[[CLS (DOS command)|Template:Mono]]
Clears the screen.
[[COPY (DOS command)|Template:Mono]]
Copies one file to another (if the destination file already exists, MS-DOS asks whether to replace it). (See also XCOPY, an external command that could also copy directory trees).
[[CTTY (DOS command)|Template:Mono]]
Defines the device to use for input and output.
[[DATE (command)|Template:Mono]]
Display and set the date of the system.
[[DEL (command)|Template:Mono, Template:Mono]]
Deletes a file. When used on a directory, deletes all files inside the directory only. In comparison, the external command Template:Mono deletes all subdirectories and files inside a directory as well as the directory itself.
[[DIR (command)|Template:Mono]]
Lists the files in the specified directory.
[[ECHO (command)|Template:Mono]]
Toggles whether the commands executed by a batch file are displayed on screen (Template:Codett) or not (Template:Codett). Also displays text on the screen (Template:Codett).
[[EXIT (command)|Template:Mono]]
Exits from Template:Mono and returns to the program which launched it.
Template:Mono
Enables or disables the return of long filenames by the Template:Mono command. (Windows 9x).Script error: No such module "Unsubst".
[[LOADHIGH|Template:Mono, Template:Mono]]
Loads a program into upper memory (Template:Codett in DR DOS).
[[LOCK (DOS command)|Template:Mono]]
Enables external programs to perform low-level disk access to a volume. (MS-DOS 7.1 and Windows 9x only)Script error: No such module "Unsubst".
[[MKDIR|Template:Mono, Template:Mono]]
Creates a new directory.
[[PATH (DOS command)|Template:Mono]]
Displays or changes the value of the Template:Mono environment variable which controls the places where Template:Mono will search for executable files.
[[PROMPT (DOS command)|Template:Mono]]
Displays or change the value of the Template:Mono environment variable which controls the appearance of the prompt.
[[REN (command)|Template:Mono, Template:Mono]]
Renames a file or directory.
[[RMDIR|Template:Mono, Template:Mono]]
Removes an empty directory.
[[SET (DOS command)|Template:Mono]]
Sets the value of an environment variable; without arguments, shows all defined environment variables.
[[TIME (command)|Template:Mono]]
Display and set the time of the system.
Template:Mono
Display the fully expanded physical name of a file, resolving [[ASSIGN (DOS command)|Template:Mono]], [[JOIN (DOS command)|Template:Mono]] and SUBST logical filesystem mappings.[2]
[[TYPE (DOS command)|Template:Mono]]
Display the content of a file on the console.
[[UNLOCK (DOS command)|Template:Mono]]
Disables low-level disk access. (MS-DOS 7.1 and Windows 9x only)Script error: No such module "Unsubst".
[[VER (command)|Template:Mono]]
Displays the version of the operating system.
[[VERIFY (DOS command)|Template:Mono]]
Enable or disable verification of writing for files.
[[VOL (command)|Template:Mono]]
Shows information about a volume.

Batch file commands

Control structures are mostly used inside batch files, although they can also be used interactively.[3][2]

Template:Monolabel
Defines a target for Template:Mono.
[[CALL (DOS command)|Template:Mono]]
Executes another batch file and returns to the old one and continues.
[[FOR (DOS command)|Template:Mono]]
Iteration: repeats a command for each out of a specified set of files.
Template:Mono
Moves execution to a specified label. Labels are specified at the beginning of a line, with a colon (Template:Codett).
[[IF (DOS command)|Template:Mono]]
Conditional statement, allows branching of the program execution.
[[PAUSE (DOS command)|Template:Mono]]
Halts execution of the program and displays a message asking the user to press any key to continue.
[[REM (DOS command)|Template:Mono]]
comment: any text following this command is ignored.
[[SHIFT (DOS command)|Template:Mono]]
Replaces each of the replacement parameters with the subsequent one (e.g. Template:Codett with Template:Codett, Template:Codett with Template:Codett, etc.).

IF command

On exit, all external commands submit a return code (a value between Template:Mono and Template:Mono) to the calling program. Most programs have a certain convention for their return codes (for instance, 0 for a successful execution).[4][5][6][7]

If a program was invoked by Template:Mono, the internal IF command with its Template:Mono conditional can be used to test on error conditions of the last invoked external program.Script error: No such module "Unsubst".

Under Template:Mono, internal commands do not establish a new value.Script error: No such module "Unsubst".

Variables

Batch files for Template:Mono can have four kinds of variables:

Redirection, piping, and chaining

Because DOS is a single-tasking operating system, piping is achieved by running commands sequentially, redirecting to and from a temporary file.Script error: No such module "Unsubst". Template:Mono makes no provision for redirecting the standard error channel.Script error: No such module "Unsubst".

command < filename
Redirect standard input from a file or device
command > filename
Redirect standard output, overwriting target file if it exists.
command >> filename
Redirect standard output, appending to target file if it exists.
command1 | command2
Pipe standard output from command1 to standard input of command2
command1command2
Commands separated by ASCII-20 (¶, invoked by Template:Keypress) are executed in sequence (chaining of commands).[2] In other words, first command1 is executed until termination, then command2.[2] This is an undocumented feature in Template:Mono of MS-DOS/PC DOS 5.0 and higher.[2] It is also supported by Template:Mono of the Windows NT family as well as by DR-DOS 7.07. All versions of DR-DOS Template:Mono already supported a similar internal function utilizing an exclamation mark (!) instead (a feature originally derived from Concurrent DOS and Multiuser DOS) - in the single-user line this feature was only available internally (in built-in startup scripts like "!DATE!TIME") and indirectly through DOSKEY's $T parameter to avoid problems with ! as a valid filename character.[2] 4DOS supports a configurable command line separator (4DOS.INI CommandSep= or SETDOS /C), which defaults to ^.[9] Template:Mono in newer versions of Windows NT also supports an & separator for compatibility with the cmd syntax in OS/2 and the Windows NT family.[9] (cmd does not support the ¶ separator.)

Limitations

Generally, the command line length in interactive mode is limited to 126 characters.[10][11][12] In MS-DOS 6.22, the command line length in interactive mode is limited to 127 characters.Script error: No such module "Unsubst".

In popular culture

  • The message "Loading Template:Mono" can be seen on a HUD view of the Terminator and the internal viewport of RoboCop when he reboots.Script error: No such module "Unsubst".
  • In the animated children's TV series ReBoot, which takes place inside computers, the leader of a system (the equivalent of a city) is called the Template:Mono.[13]

See also

References

<templatestyles src="Reflist/styles.css" />

  1. Script error: No such module "citation/CS1".
  2. a b c d e f g h Script error: No such module "citation/CS1". (NB. The provided link points to a HTML-converted version of the NWDOSTIP.TXT, which is part of the MPDOSTIP.ZIP collection.) [1]
  3. a b Script error: No such module "citation/CS1".
  4. Script error: No such module "citation/CS1". (NB. BATTIPS.TXT is part of MPDOSTIP.ZIP. The provided link points to an HTML-converted older version of the BATTIPS.TXT file.) [2]
  5. Script error: No such module "citation/CS1".
  6. Script error: No such module "citation/CS1". [3]
  7. Script error: No such module "citation/CS1".
  8. Script error: No such module "citation/CS1".
  9. a b c <templatestyles src="Template:Blockquote/styles.css" />

    [...] 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 the SETDOS /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.) [...]

    Script error: No such module "Check for unknown parameters".
  10. Script error: No such module "citation/CS1". (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]
  11. Script error: No such module "citation/CS1". (NB. The provided link points to a HTML-converted version of the 4DOS5TIP.TXT file, which is part of the MPDOSTIP.ZIP collection.) [5]
  12. Script error: No such module "citation/CS1". (xviii+856+vi pages, 3.5"-floppy) Errata: [6] [7]
  13. Script error: No such module "citation/CS1".
Cite error: <ref> tag with name "Microsoft_COMMAND" defined in <references> is not used in prior text.

Script error: No such module "Check for unknown parameters".

Further reading

<templatestyles src="Template:Quote_box/styles.css" />

[...] 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 [...]

Script error: No such module "citation/CS1".

Script error: No such module "Check for unknown parameters".

External links

  • Template:Github - Source code to COMMAND.COM version A067 released by Microsoft as part of MS-DOS 4.0
  • Template:GitHub – Source code to COMMAND.COM version 2.11 released by Microsoft as part of MS-DOS 2.0
  • Template:GitHub – Source code to COMMAND.COM version 1.17 released by Microsoft as part of MS-DOS 1.25
  • FreeCom – COMMAND.COM implementation of FreeDOS

Script error: No such module "Navbox". Script error: No such module "Navbox". Template:DOS system files