Windows Administration at the Command Line
at all; you just have to know what task they perform, which is why many people don't use them.
of information you must provide. For example, the
tory path, and ending with a filename specification. None of these entries is a command line switch,
but they're all important parameters.
provide text input
as well as command
line switches.
so you can see what to type at the command line. The point is that most people could use a command at
the command prompt if they simply knew the simple
commands provide some information, usually enough to jog your memory when you need to use it .
orized by now. However, like many people, I find that memorizing all of those commands, their param-
eters, and their command line switches is just too much work. However, discovering the required
parameters one time isn't too much work. That's where batch files come to my aid. I use batch files to
remember specific command sequences for me.
want to use them, a batch file can do the job. In fact, you can create batch files that have a limited
amount of intelligence so they don't perform the same task in the same way every time. Batch files are
the first method that many people use to automate the command line. I have batch files that I wrote over
18 years ago when I started with computers and I'm still using them today. In short, a good batch file can
last a very long time. The thing to remember about batch files is that they're very easy to write, only have
a little intelligence (so there isn't any heavy coding), and don't require anything special to execute.
You'll discover how to work with batch files in Chapter 7.