cmd.exe

From Wikipedia, the free encyclopedia
(Redirected from Windows Command Prompt)
Jump to navigation Jump to search
Not to be confused with COMMAND.COM.
For other uses, see CMD.
"Command Prompt" redirects here. For the concept, see Command prompt.

Command Prompt (cmd.exe)
Other namesWindows Command Processor
DevelopersMicrosoft, IBM, ReactOS contributors
Initial releaseDecember 1987; 38 years ago (1987-12)
Repository
  • {{URL|example.com|optional display text}}Lua error in Module:EditAtWikidata at line 29: attempt to index field 'wikibase' (a nil value).
Engine
    Lua error in Module:EditAtWikidata at line 29: attempt to index field 'wikibase' (a nil value).
    Operating system
    PlatformIA-32, x86-64, ARM (and historically DEC Alpha, MIPS, PowerPC, and Itanium)
    PredecessorCOMMAND.COM
    TypeCommand-line interpreter

    cmd.exe, a.k.a. Command Prompt, is a shell program on later versions of Windows (NT and CE families), OS/2,[1] eComStation, ArcaOS, and ReactOS.[2] In some versions of Windows (CE .NET 4.2,[3] CE 5.0[4] and Embedded CE 6.0[5]) it is referred to as the Command Processor Shell. Implementation differs between operating systems, but with significant consistency of behavior and available commands.

    Older, related operating systems, DOS and Windows 9x, provided COMMAND.COM as the shell. cmd.exe replaced COMMAND.COM in the Windows product line with the introduction of NT. Current versions of Windows include PowerShell as an alternative shell that runs side-by-side with cmd.exe.

    The initial version of cmd.exe for Windows NT was developed by Therese Stowell.[6] Windows CE 2.11 was the first embedded Windows release to support a console and a Windows CE version of cmd.exe.[7] The ReactOS implementation of cmd.exe is derived from FreeCOM, the FreeDOS command line interpreter.[2]

    Use

    [edit | edit source]

    Desktop integration

    [edit | edit source]

    In Windows, the shell is presented in the desktop via Windows Terminal or on older versions via Windows Console.

    Concurrent piping

    [edit | edit source]

    In OS/2 and Windows, the shell supports pipes to allow both sides of a pipeline to run concurrently. As a result, it is possible to redirect the standard error stream. In contrast, COMMAND.COM uses temporary files, and runs the two sides serially, one after the other.

    Command separator

    [edit | edit source]

    Multiple commands can be included in a single line using the command separator & or &&.[8]

    With the & separator, a subsequent command is executed even if the previous command indicates an error.[9] In the following example, each of the three commands is executed, one after the other, and regardless of their result code. 

    >CommandA & CommandB & CommandC

    With the && separator, a command must complete successfully for the subsequent command to execute. In the following example, CommandB only executes if CommandA completes successfully, and CommandC only executes if CommandB also completes successfully. 

    >CommandA && CommandB && CommandC

    Command line limit

    [edit | edit source]

    The shell limits the length of a command line which includes entered text, individual environment variables that are inherited by other processes, and all environment variable expansions[10] On Windows XP and later, the maximum length is 8191 (213-1) characters. On earlier versions, such as Windows 2000 or Windows NT 4.0, the maximum length is 2047 (211-1) characters.

    Escaping special characters

    [edit | edit source]

    The shell reserves the following characters as special:[8] &<>[]{}^=;!'+,`~ and whitespace. In some cases, an argument that contains such characters must be enclosed in double quotes to escape from the special character handling. For example: 

    >echo me & you
me
'you' is not recognized as an internal or external command,
operable program or batch file.

>echo "me & you"
"me & you"

    Internal commands

    [edit | edit source]

    The following sections list internal commands for implementations of the shell on various operating systems.

    OS/2

    [edit | edit source]
    File:Microsoft OS 2 Version 1.3 cmd.exe OS 2 Window 640x373.png
    cmd.exe running in OS/2 Window on OS/2 version 1.3

    Internal commands in OS/2:[11]

    Windows NT family

    [edit | edit source]
    File:Windows11Terminal uk.png
    cmd.exe running in Windows Terminal on Ukrainian Windows 11

    Internal commands in Windows NT and later:[12]

    Windows CE

    [edit | edit source]
    File:Microsoft Windows CE Version 3.0 (Build 126) cmd.exe Command Prompt 800x574.png
    Pocket CMD v 3.0 (cmd.exe) on Windows CE 3.0

    Internal commands in Windows CE .NET 4.2,[13] Windows CE 5.0[14] and Windows Embedded CE 6.0:[15]

    • attrib
    • call
    • cd
    • chdir
    • cls
    • copy
    • date
    • del
    • dir
    • echo
    • erase
    • exit
    • goto
    • help
    • if
    • md
    • mkdir
    • move
    • path
    • pause
    • prompt
    • pwd
    • rd
    • rem
    • ren
    • rename
    • rmdir
    • set
    • shift
    • start
    • time
    • title
    • type

    The net command is available as an external command.

    ReactOS

    [edit | edit source]
    File:ReactOS-0.4.13 cmd.exe Command Prompt 667x434.png
    cmd.exe on ReactOS

    Internal commands in ReactOS:[2]

    • ?
    • alias
    • assoc
    • beep
    • call
    • cd
    • chdir
    • choice
    • cls
    • color
    • copy
    • ctty
    • date
    • del
    • delete
    • delay
    • dir
    • dirs
    • echo
    • echos
    • echoerr
    • echoserr
    • endlocal
    • erase
    • exit
    • for
    • free
    • goto
    • history
    • if
    • memory
    • md
    • mkdir
    • mklink
    • move
    • path
    • pause
    • popd
    • prompt
    • pushd
    • rd
    • rmdir
    • rem
    • ren
    • rename
    • replace
    • screen
    • set
    • setlocal
    • shift
    • start
    • time
    • timer
    • title
    • type
    • ver
    • verify
    • vol

    Comparison with COMMAND.COM

    [edit | edit source]

    On Windows, cmd.exe provides various user experience enhancments as compared to COMMAND.COM, including:

    • More detailed error reporting for malformed commands than the generic COMMAND.COM "Bad command or file name". In OS/2, errors are reported in the chosen language of the system, their text being taken from the system message files. The HELP command can then be issued with the error message number to obtain further information.
    • Supports using of arrow keys to scroll through command history. With COMMAND.COM, this functionality was only available in DR DOS (via HISTORY) and later via an external component called DOSKEY.
    • Adds rotating command-line completion for file and folder paths, where the user can cycle through results for the prefix using the Tab ↹, and ⇧ Shift+Tab ↹ for reverse direction.
    • Treats the caret character (^) as the escape character; the character following it is to be taken literally. There are special characters in cmd.exe and COMMAND.COM that are meant to alter the behavior of the command line processor. The caret character forces the command line processor to interpret them literally.
    • Supports delayed variable expansion with SETLOCAL EnableDelayedExpansion, allowing values of variables to be calculated at runtime instead of during parsing of script before execution (Windows 2000 and later), fixing DOS idioms that made using control structures hard and complex.[16] The extensions can be disabled, providing a stricter compatibility mode.
    • The COMMAND.COM DELTREE command was merged into the rd command via the /S switch.
    • SetLocal and EndLocal commands limit the scope of changes to the environment. Changes made to the command line environment after SetLocal are local to the batch file. EndLocal restores the previous settings.[17]
    • The call command allows subroutines within batch file. The COMMAND.COM CALL command only supports calling external batch files.
    • File name parser extensions to the set command are comparable with C shell.[further explanation needed]
    • The set command can perform expression evaluation.
    • An expansion of the for command supports parsing files and arbitrary sets in addition to file names.
    • The new pushd and popd commands provide access past navigated paths similar to forward and back buttons in a web browser or File Explorer.
    • The conditional if command can perform case-insensitive comparisons and numeric equality and inequality comparisons in addition to case-sensitive string comparisons. This was available in DR-DOS, but not in PC DOS or MS-DOS.

    See also

    [edit | edit source]

    References

    [edit | edit source]
    1. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    2. ^ a b c Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    3. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    4. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    5. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    6. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    7. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    8. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    9. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    10. ^ Command prompt (Cmd.exe) command-line string limitation
    11. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    12. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    13. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    14. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    15. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    16. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    17. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).

    Further reading

    [edit | edit source]
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    [edit | edit source]
    Error creating thumbnail: File missing
    Wikimedia Commons has media related to Windows Command Prompt.
    Wikibooks has a book on the topic of: Windows Batch Scripting
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
    • Most important CMD commands in Windows - colorconsole.de
    Retrieved from "http://70.231.62.181/index.php?title=Cmd.exe&oldid=3676664"