Batch file

A batch file is a script file in DOS, OS/2 and Microsoft Windows. It consists of a series of commands to be executed by the command-line interpreter, stored in a plain text file. A batch file may contain any command the interpreter accepts interactively and use constructs that enable conditional branching and looping within the batch file, such as codice_1, codice_2, and codice_3 labels. The term "batch" is from batch processing, meaning "non-interactive execution", though a batch file may not process a "batch" of multiple data.
Similar to Job Control Language (JCL), DCL and other systems on mainframe and minicomputer systems, batch files were added to ease the work required for certain regular tasks by allowing the user to set up a script to automate them. When a batch file is run, the shell program (usually COMMAND.COM or cmd.exe) reads the file and executes its commands, normally line-by-line. Unix-like operating systems, such as Linux, have a similar, but more flexible, type of file called a shell script.
The filename extension .bat is used in DOS and Windows. Windows NT and OS/2 also added .cmd. Batch files for other environments may have different extensions, e.g., .btm in 4DOS, 4OS2 and 4NT related shells.
The detailed handling of batch files has changed significantly between versions. Some of the detail in this article applies to all batch files, while other details apply only to certain versions.
Variants.
DOS.
In DOS, a batch file can be started from the command-line interface by typing its name, followed by any required parameters and pressing the key. When DOS loads, the file AUTOEXEC.BAT, when present, is automatically executed, so any commands that need to be run to set up the DOS environment may be placed in this file. Computer users would have the AUTOEXEC.BAT file set up the system date and time, initialize the DOS environment, load any resident programs or device drivers, or initialize network connections and assignments.
A .bat file name extension identifies a file containing commands that are executed by the command interpreter COMMAND.COM line by line, as if it were a list of commands entered manually, with some extra batch-file-specific commands for basic programming functionality, including a codice_3 command for changing flow of line execution.
Early Windows.
Microsoft Windows was introduced in 1985 as a graphical user interface-based (GUI) overlay on text-based operating systems and was designed to run on DOS. In order to start it, the codice_5 command was used, which could be added to the end of the AUTOEXEC.BAT file to allow automatic loading of Windows. In the earlier versions, one could run a .bat type file from Windows in the MS-DOS Prompt. Windows 3.1x and earlier, as well as Windows 9x invoked COMMAND.COM to run batch files.
OS/2.
The IBM OS/2 operating system supported DOS-style batch files. It also included a version of REXX, a more advanced batch-file scripting language. IBM and Microsoft started developing this system, but during the construction of it broke up after a dispute; as a result of this, IBM referred to their DOS-like console shell without mention of Microsoft, naming it just DOS, although this seemingly made no difference with regard to the way batch files worked from COMMAND.COM.
OS/2's batch file interpreter also supports an EXTPROC command. This passes the batch file to the program named on the EXTPROC file as a data file. The named program can be a script file; this is similar to the #! mechanism.
Windows NT.
Unlike Windows 98 and earlier, the Windows NT family of operating systems does not depend on MS-DOS. Windows NT introduced an enhanced 32-bit command interpreter (cmd.exe) that could execute scripts with either the .CMD or .BAT extension. Cmd.exe added additional commands, and implemented existing ones in a slightly different way, so that the same batch file (with different extension) might work differently with cmd.exe and COMMAND.COM. In most cases, operation is identical if the few unsupported commands are not used. Cmd.exe's extensions to COMMAND.COM can be disabled for compatibility.
Microsoft released a version of cmd.exe for Windows 9x and ME called WIN95CMD to allow users of older versions of Windows to use certain cmd.exe-style batch files.
, cmd.exe is the normal command interpreter for batch files; the older COMMAND.COM can be run as well in 32-bit versions of Windows able to run 16-bit programs.
Batch file parameters.
COMMAND.COM and cmd.exe support that a number of special variables (codice_14, codice_15 through codice_16) in order to refer to the path and name of the batch job and the first nine calling parameters from within the batch job, see also SHIFT. Non-existent parameters are replaced by a zero-length string. They can be used similar to environment variables, but are not stored in the environment. Microsoft and IBM refer to these variables as "replacement parameters" or "replaceable parameters", whereas Digital Research, Novell and Caldera established the term "replacement variables" for them. JP Software calls them "batch file parameters".
Examples.
This example batch file displays codice_17, prompts and waits for the user to press a key, and then terminates. (Note: It does not matter if commands are lowercase or uppercase unless working with variables)
@ECHO OFF
ECHO Hello World!
PAUSE
To execute the file, it must be saved with the filename extension suffix .bat (or .cmd for Windows NT-type operating systems) in plain text format, typically created by using a text editor such as Microsoft Notepad or a word processor working in plain text mode.
When executed, the following is displayed:
Explanation.
The interpreter executes each line in turn, starting with the first. The codice_18 symbol at the start of any line prevents the prompt from displaying that command as it is executed. The command codice_19 turns off the prompt permanently, or until it is turned on again. The combined codice_20 is often as here the first line of a batch file, preventing any commands from displaying, itself included. Then the next line is executed and the codice_21 command outputs codice_17. The next line is executed and the codice_23 command displays codice_24 and pauses the script's execution. After a key is pressed, the script terminates, as there are no more commands. In Windows, if the script is executed from an already running command prompt window, the window remains open at the prompt as in MS-DOS; otherwise, the window closes on termination.
Limitations and exceptions.
Null values in variables.
Variable expansions are substituted textually into the command, and thus variables which contain nothing simply disappear from the syntax, and variables which contain spaces turn into multiple tokens. This can lead to syntax errors or bugs.
For example, if %foo% is empty, this statement:
IF %foo%==bar ECHO Equal
parses as the erroneous construct:
IF ==bar ECHO Equal
Similarly, if codice_25 contains codice_26, then a different syntax error results:
IF abc def==bar ECHO Equal
The usual way to prevent this problem is to surround variable expansions in quotes so that an empty variable expands into the valid expression codice_27 instead of the invalid codice_28. The text that is being compared to the variable must also be enclosed in quotes, because the quotes are not special delimiting syntax; these characters represent themselves.
IF "%foo%"=="bar" ECHO Equal
The delayed !VARIABLE! expansion available in Windows 2000 and later may be used to avoid these syntactical errors. In this case, null or multi-word variables do not fail syntactically because the value is expanded after the IF command is parsed:
IF !foo!==bar ECHO Equal
Another difference in Windows 2000 or higher is that an empty variable (undefined) is not substituted. As described in previous examples, previous batch interpreter behaviour would have resulted in an empty string. Example:
C:\>set MyVar=
C:\>echo %MyVar%
%MyVar%
C:\>if "%MyVar%"=="" (echo MyVar is not defined) else (echo MyVar is %MyVar%)
MyVar is %MyVar%
Batch interpreters prior to Windows 2000 would have displayed result codice_29.
Quotation marks and spaces in passed strings.
Unlike Unix/POSIX processes, which receive their command-line arguments already split up by the shell into an array of strings, a Windows process receives the entire command-line as a single string, via the GetCommandLine API function. As a result, each Windows application can implement its own parser to split the entire command line into arguments. Many applications and command-line tools have evolved their own syntax for doing that, and so there is no single convention for quoting or escaping metacharacters on Windows command lines.
Where a string contains quotation marks, and is to be inserted into another line of text that must also be enclosed in quotation marks, particular attention to the quoting mechanism is required:
C:\>set foo="this string is enclosed in quotation marks"
C:\>echo "test 1 %foo%"
"test 1 "this string is enclosed in quotation marks""
C:\>eventcreate /T Warning /ID 1 /L System /SO "Source" /D "Example: %foo%"
ERROR: Invalid Argument/Option - 'string'.
Type "EVENTCREATE /?" for usage.
On Windows 2000 and later, the solution is to replace each occurrence of a quote character within a value by a series of three quote characters:
C:\>set foo="this string is enclosed in quotes"
C:\>set foo=%foo:"="""%
C:\>echo "test 1 %foo%"
"test 1 """this string is enclosed in quotes""""
C:\>eventcreate /T Warning /ID 1 /L System /SO "Source" /D "Example: %foo%"
SUCCESS: A 'Warning' type event is created in the 'Source' log/source.
Escaped characters in strings.
Some characters, such as pipe (codice_30) characters, have special meaning to the command line. They cannot be printed as text using the command unless escaped using the caret ^ symbol:
C:\>Echo foo | bar
'bar' is not recognized as an internal or external command,
operable program or batch file.
C:\>Echo foo ^| bar
foo | bar
However, escaping does not work as expected when inserting the escaped character into an environment variable. The variable ends up containing a live pipe command when merely echoed. It is necessary to escape both the caret itself and the escaped character for the character display as text in the variable:
C:\>set foo=bar | baz
'baz' is not recognized as an internal or external command,
operable program or batch file.
C:\>set foo=bar ^| baz
C:\>echo %foo%
'baz' is not recognized as an internal or external command,
operable program or batch file.
C:\>set foo=bar ^^^| baz
C:\>echo %foo%
bar | baz
The delayed expansion available with or with in Windows 2000 and later may be used to show special characters stored in environment variables because the variable value is expanded after the command was parsed:
C:\>cmd /V:ON
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>set foo=bar ^| baz
C:\>echo !foo!
bar | baz
Sleep or scripted delay.
Until the TIMEOUT command was introduced with Windows Vista, there was no easy way to implement a timed pause, as the PAUSE command halts script activity indefinitely until any key is pressed.
Many workarounds were possible, but generally only worked in some environments: The codice_31 command was not available in older DOS versions, codice_32 was only available if TCP/IP was installed, and so on. No solution was available from Microsoft, but a number of small utility programs, could be installed from other sources. A commercial example would be the 1988 Norton Utilities Batch Enhancer (BE) command, where codice_33 would wait for 1 second, or the free 94-byte WAIT.COM where codice_34 would wait for 5 seconds, then return control to the script. Most such programs are 16-bit .COM files, so are incompatible with 64-bit Windows.
Text output with stripped CR/LF.
Normally, all printed text automatically has the control characters for carriage return (CR) and line feed (LF) appended to the end of each line.
@echo foo
@echo bar
C:\>batchtest.bat
foo
bar
It does not matter if the two echo commands share the same command line; the CR/LF codes are inserted to break the output onto separate lines:
C:\>@echo Message 1&@echo Message 2
Message 1
Message 2
A trick discovered with Windows 2000 and later is to use the special prompt for input to output text without CR/LF trailing the text. In this example, the CR/LF does not follow Message 1, but does follow Line 2 and Line 3:
@echo off
set /p ="Message 1"<nul
echo Message 2
echo Message 3
C:\>batchtest2.bat
Message 1Message 2
Message 3
This can be used to output data to a text file without CR/LF appended to the end:
C:\>set /p ="Message 1"<nul >data.txt
C:\>set /p ="Message 2"<nul »data.txt
C:\>set /p ="Message 3"<nul »data.txt
C:\>type data.txt
Message 1Message 2Message 3
However, there is no way to inject this stripped CR/LF prompt output directly into an environment variable.
Setting a Uniform Naming Convention (UNC) working directory from a shortcut.
It is not possible to have a command prompt that uses a UNC path as the current working directory; e.g. codice_35
The command prompt requires the use of drive letters to assign a working directory, which makes running complex batch files stored on a server UNC share more difficult. While a batch file can be run from a UNC file path, the working directory default is codice_36.
In Windows 2000 and later, a workaround is to use the ' and ' command with command extensions.
If not enabled by default, command extensions can be temporarily enabled using the switch for the command interpreter.
So to run a batch file on a UNC share, assign a temporary drive letter to the UNC share, and use the UNC share as the working directory of the batch file, a Windows shortcut can be constructed that looks like this:
The working directory attribute of this shortcut is ignored.
This also solves a problem related to User Account Control (UAC) on Windows Vista and newer. When an administrator is logged on and UAC is enabled, and they try to run a batch file as administrator from a network drive letter, using the right-click file context menu, the operation will unexpectedly fail. This is because the elevated UAC privileged account context does not have network drive letter assignments, and it is not possible to assign drive letters for the elevated context via the Explorer shell or logon scripts. However, by creating a shortcut to the batch file using the above / construct, and using the shortcut to run the batch file as administrator, the temporary drive letter will be created and removed in the elevated account context, and the batch file will function correctly.
The following syntax does correctly expand to the path of the current batch script.
 %~dp0
UNC default paths are turned off by default as they used to crash older programs.
The Dword registry value codice_37 at codice_38 allows the default directory to be UNC. codice_39 command will refuse to change but placing a UNC path in Default Directory in a shortcut to Cmd or by using the Start command. ( share is for administrators).
Character set.
Batch files use an OEM character set, as defined by the computer, e.g. Code page 437. The non-ASCII parts of these are incompatible with the Unicode or Windows character sets otherwise used in Windows so care needs to be taken. Non-English file names work only if entered through a DOS character set compatible editor. File names with characters outside this set do not work in batch files.
To get output in Unicode into file pipes from an internal command such as codice_40, one can use the codice_41 command. For example, codice_42 creates a file containing a directory listing with correct Windows characters, in the UTF-16LE encoding.
Batch viruses and malware.
As with any other programming language, batch files can be used maliciously. Simple trojans and fork bombs are easily created, and batch files can do a form of DNS poisoning by modifying the hosts file. Batch viruses are possible, and can also spread themselves via USB flash drives by using Windows' Autorun capability.
The following command in a batch file will delete all the data in the current directory (folder) - without first asking for confirmation:
del /Q *.*
These three commands are a simple fork bomb that will continually replicate itself to deplete available system resources, slowing down or crashing the system:
 start "" %0
 goto TOP
Other Windows scripting languages.
The cmd.exe command processor that interprets .cmd files is supported in all 32- and 64-bit versions of Windows . COMMAND.EXE, which interprets .BAT files, was supported in all 16- and 32-bit versions up to at least Windows 10.
There are other, later and more powerful, scripting languages available for Windows. However, these require the scripting language interpreter to be installed before they can be used:
Script files run if the filename without extension is entered. There are rules of precedence governing interpretation of, say, codice_43 if codice_44, codice_45, codice_46, codice_47, etc. exist; by default codice_44 has highest priority. This default order may be modified in newer operating systems by the user-settable PATHEXT environment variable.