Simply type
SET
and press Enter to see the list.
50.
Create custom versions of
AutoExec.NT
and
Config.NT
for applications that require them.
The custom versions can use different settings to ensure that the application runs as anticipated.
You specify these custom files using the Windows PIF Settings dialog box that you
access by clicking Advanced on the Program tab of the application??™s Property dialog box.
51.
Use the error level output of commands and utilities to detect errors in batch files. An
IF
ERRORLEVEL
command can detect the error. A simple
GoTo
command can redirect the flow
of the batch file to an error-handling section, and then redirect program flow for another
attempt at the failed command or utility. Using this looping approach helps you create a
589
certain level of error handling and fault tolerance even in batch files. Make sure you record
all error information possible in an output file.
52.
The command line is like the submerged part of an iceberg. Few people see it, many people
don??™t know about it, yet it exists and it comprises the greater part of the Windows operating
system. Every time you think that a graphical utility will replace the command line, look
again because someone will find a way to automate it with a batch file or script.
Pages:
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349