Windows 7 / Getting Started

The Redirection Symbols

As in MS-DOS and UNIX, Command Prompt sessions in Windows allow you to override the default source for input (the keyboard) or the default destination for output (the screen).

Redirecting Output To redirect output to a file, type the command followed by a greater than sign (>) and the name of the file. For example, to send the output of the Dir command to a file instead of the screen, type the following:

dir /b *.bat > batch.lst

This command line creates a file called Batch.lst that contains the names of all the .bat files in the current folder.

Using two greater than signs (>>) redirects output and appends it to an existing file. For example:

dir /b *.cmd >> batch.lst

This command line appends a list of .cmd files to the previously created file containing .bat files. (If you use >> to append to a file that doesn't exist, Windows creates the file.)

Redirecting Input To redirect input from a file, type the command followed by a less than sign (<) and the name of the file. The Sort and More commands are examples of commands that can accept input from a file. The following example uses Sort to filter the file created with the Dir command just shown:

sort < batch.lst

The input file, Batch.lst, contains a list of .bat files followed by a list of .cmd files (assuming you have some of each in the current folder). The output to the screen is the same list of files sorted alphabetically by file name.

Redirecting Input and Output You can redirect both input and output in a command line. For example, to use Batch.lst as input to the Sort command and send its output to a file named Sorted.lst, type the following:

sort < batch.lst > sorted.lst

Standard Output and Standard Error Programs can be written to send their output either to the standard output device or to the standard error device. Sometimes programs are written to send different types of output to each device. You can't always tell which is which because, by default, both devices are the screen.

The Type command illustrates the difference. When used with wildcards, the Type command sends the name of each matching file to the standard error device and sends the contents of the file to the standard output device. Because they both go to the screen, you see a nice display with each file name followed by its contents.

However, if you try to redirect output to a file like this:

type *.bat > std.out

the file names still appear on your screen because standard error is still directed to the screen. Only the file contents are redirected to Std.out.

Windows allows you to qualify the redirection symbol by preceding it with a number. Use 1> (or simply >) for standard output and 2> for standard error. For example:

type *.bat 2> err.out

This time the file contents go to the screen and the names are redirected to Err.out. You can redirect both to separate files with this command line:

type *.bat 2> err.out 1> std.out
[Previous] [Contents] [Next]

In this tutorial:

  1. Working with the Command Prompt
  2. Starting and Ending a Command Prompt Session
  3. Easy ways to invoke administrator Command Prompt sessions
  4. Starting Command Prompt at a Particular Folder
  5. Strings with Spaces Need Quotes
  6. Cmd.exe vs. Command.com
  7. Commands Are Not Case Sensitive
  8. Starting Command Prompt and Running a Command
  9. Cmd.exe and Other Command Prompts
  10. Using AutoRun to Execute Commands When Command Prompt Starts
  11. Using Cmds Command-Line Syntax
  12. Using Commands
  13. Type /? for help
  14. Starting Programs
  15. Open Windows Explorer at the current Command Prompt folder
  16. Using File-Name and Folder-Name Completion
  17. Use a different completion character
  18. Using Wildcards
  19. Editing the Command Line
  20. Using Command Symbols
  21. The Redirection Symbols
  22. The Pipe Symbol
  23. The Command Combination Symbols
  24. Pausing or Canceling Commands
  25. Simplifying Command Entry with Doskey Macros
  26. DOSKEY Saves Typing
  27. System Variables Identify the Environment
  28. Viewing Environment Variables
  29. Modifying Environment Variables
  30. Predefined Environment Variables
  31. Customizing Command Prompt Windows
  32. Setting the Window Size and Position
  33. Setting the Window Size and Position Visually
  34. Selecting a Font
  35. Setting Colors
  36. Setting Other Options
  37. Copy and paste in the command prompt window
  38. Navigating from the command prompt
  39. Printing a list of filenames
  40. Commands Use Paths
  41. Identifying Executables
  42. Modifying the Path to Executables
  43. Modifying the Path with the GUI
  44. Changing the Current Path with CD
  45. Changing the Current Path with Windows Explorer
  46. Capturing the Output
  47. A Sampling of Commands
  48. Dir
  49. Copy
  50. XCopy
  51. SET
  52. NET USE
  53. SystemInfo
  54. DriverQuery
  55. Echo
  56. Advanced Shell Commands
  57. Creating a Batch File
  58. Scheduling a Batch File
  59. Creating Scheduled Tasks with a Script
  60. Using Windows PowerShell and the PowerShell ISE
  61. Windows PowerShell ISE
  62. PowerShell Commands
  63. Verbs and Nouns
  64. Sending Output to a Text File
  65. PowerShell Syntax
  66. Variables Created with a $ Symbol
  67. Comparison Operators
  68. Parentheses, Brackets, and Braces
  69. Running PowerShell Scripts
  70. PowerShell Execution Policy
  71. Changing the Execution Policy
  72. Looping
  73. Collections
  74. Creating a PowerShell Script
  75. Documenting Scripts
  76. Using PowerShell Commands
  77. Getting Help on PowerShell
  78. Using WMI_Cmdlets
  79. Getting Details on an Object
  80. Querying Information on Specific Objects
  81. Terminate Applications with Win32_process
  82. Formatting Output with the -f Format Operator
  83. Filtering the Output with the Where-Object Command
  84. Using the IF statement
  85. Using the Switch Statement
  86. Script Reusability