Commands Use Paths
When you execute commands from the command prompt, the system needs to know where to find the command. It fi rst tries to execute it in the current path and then looks for it in predefi ned paths. A path identifies a location on the hard drive.
As an example, when you first launch the command prompt, it will start in the C:\ Users\%username% path by default, where %username% will be replaced with the username you're logged on with. (If you launch it with Run As Administrator, it will start in the c:\%windir%\System32 folder.) If you execute a command (such as IPConfig), it will look for it in the current folder first. If it isn't located in the current folder, it will search the folders identifi ed in the predefi ned paths. If the command isn't located in any of the known paths, you'll see an error. For example, if you type x and press Enter, you'll see this error:
'x' is not recognized as an internal or external command, operable program or batch file.
Note Documentation commonly uses the terms folders and directories interchangeably In the early DOS days, they were almost always called directories When the Windows GUI came out, they were referred to as folders because the icon looks like a folder It matched a metaphor users could easily understand; that is, files were placed in folders in the real world and they are placed in folders in Windows However, there is no difference between a folder and a directory; both terms mean the same thing.
If the system didn't have predefined paths, it would search only the current folder, and commands would be a lot harder to enter and execute. However, the system starts with several predefined paths. On my system, this path includes all of these directories:
- C:\Windows\system32
- C:\Windows
- C:\Windows\System32\Wbem
- C:\Windows\System32\WindowsPowerShell\v1.0\
- C:\Windows\System32\Windows System Resource Manager\bin
- C:\Windows\idmu\com
You can execute the PATH or the SET PATH command to view the predefined path for your system. Some applications will modify the path, and you can also modify the path yourself.
In this tutorial:
- Working with the Command Prompt
- Starting and Ending a Command Prompt Session
- Easy ways to invoke administrator Command Prompt sessions
- Starting Command Prompt at a Particular Folder
- Strings with Spaces Need Quotes
- Cmd.exe vs. Command.com
- Commands Are Not Case Sensitive
- Starting Command Prompt and Running a Command
- Cmd.exe and Other Command Prompts
- Using AutoRun to Execute Commands When Command Prompt Starts
- Using Cmds Command-Line Syntax
- Using Commands
- Type /? for help
- Starting Programs
- Open Windows Explorer at the current Command Prompt folder
- Using File-Name and Folder-Name Completion
- Use a different completion character
- Using Wildcards
- Editing the Command Line
- Using Command Symbols
- The Redirection Symbols
- The Pipe Symbol
- The Command Combination Symbols
- Pausing or Canceling Commands
- Simplifying Command Entry with Doskey Macros
- DOSKEY Saves Typing
- System Variables Identify the Environment
- Viewing Environment Variables
- Modifying Environment Variables
- Predefined Environment Variables
- Customizing Command Prompt Windows
- Setting the Window Size and Position
- Setting the Window Size and Position Visually
- Selecting a Font
- Setting Colors
- Setting Other Options
- Copy and paste in the command prompt window
- Navigating from the command prompt
- Printing a list of filenames
- Commands Use Paths
- Identifying Executables
- Modifying the Path to Executables
- Modifying the Path with the GUI
- Changing the Current Path with CD
- Changing the Current Path with Windows Explorer
- Capturing the Output
- A Sampling of Commands
- Dir
- Copy
- XCopy
- SET
- NET USE
- SystemInfo
- DriverQuery
- Echo
- Advanced Shell Commands
- Creating a Batch File
- Scheduling a Batch File
- Creating Scheduled Tasks with a Script
- Using Windows PowerShell and the PowerShell ISE
- Windows PowerShell ISE
- PowerShell Commands
- Verbs and Nouns
- Sending Output to a Text File
- PowerShell Syntax
- Variables Created with a $ Symbol
- Comparison Operators
- Parentheses, Brackets, and Braces
- Running PowerShell Scripts
- PowerShell Execution Policy
- Changing the Execution Policy
- Looping
- Collections
- Creating a PowerShell Script
- Documenting Scripts
- Using PowerShell Commands
- Getting Help on PowerShell
- Using WMI_Cmdlets
- Getting Details on an Object
- Querying Information on Specific Objects
- Terminate Applications with Win32_process
- Formatting Output with the -f Format Operator
- Filtering the Output with the Where-Object Command
- Using the IF statement
- Using the Switch Statement
- Script Reusability