Windows command prompt Source: en.wikipedia.org/wiki/Windows_command_prompt

Command Prompt (cmd.exe)
Other names	Windows Command Processor
Developer(s)	Microsoft, IBM, ReactOS contributors
Initial release	December 1987; 37 years ago (1987-12)
Operating system	Windows NT family Windows CE family OS/2 eComStation ArcaOS ReactOS
Platform	IA-32, x86-64, ARM (and historically DEC Alpha, MIPS, PowerPC, and Itanium)
Predecessor	COMMAND.COM
Type	Command-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]

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

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.

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

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 (2¹³-1) characters. On earlier versions, such as Windows 2000 or Windows NT 4.0, the maximum length is 2047 (2¹¹-1) characters.

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"

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

Internal commands in OS/2:^[11]

Internal commands in Windows NT and later:^[12]

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

The net command is available as an external command.

Internal commands in ReactOS:^[2]

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.

• Comparison of command shells
• List of DOS commands

• David Moskowitz; David Kerr (1994). OS/2 2.11 Unleashed (2nd ed.). Sams Publishing. ISBN 978-0672304453.
• Stanek, William R. (2008). Windows Command-Line Administrator's Pocket Consultant (2nd ed.). Microsoft Press. ISBN 978-0735622623.

Wikimedia Commons has media related to Windows Command Prompt.

Wikibooks has a book on the topic of: Windows Batch Scripting

• "Command-line reference A-Z". Microsoft. April 26, 2023.
• "Cmd". Microsoft Windows XP Product Documentation. Microsoft. Archived from the original on September 2, 2011. Retrieved May 24, 2006.
• "Command Prompt: frequently asked questions". windows Help. Microsoft. Archived from the original on April 22, 2015. Retrieved April 20, 2015.
• "An A–Z Index of the Windows CMD command line". SS64.com.
• "Windows CMD.com – Hub of Windows Commands". windowscmd.com. Archived from the original on January 11, 2022. Retrieved January 4, 2022.
• Most important CMD commands in Windows - colorconsole.de