1. How to get the meaning of the terminology?
In the support tool, you will find a file named: Glossary, which has an explanation of most of the meaning of the terminology. Open this file, you will see a list of terminology indexed in alphabetical order. The index uses hypertext link technology, which can be queried in many ways. For example, to find out: English abbreviation SNMP is what it means, you can click the S in the index table with the mouse, any term with the first letter S will be displayed, and then find SNMP, the text will be explained below. These texts are of course also in English. Another way is that in the help documentation of each tool, all the abbreviated terms are also annotated with hypertext links. The fonts of these abbreviations are particularly obvious. When clicked, the comments can be displayed. But these comments are relatively simple.
2. The command parameters are different from the ones in the documentation:
This phenomenon has been mentioned many times in this series of articles. The cause is this: I first Read the introductory documentation for the tool command and verify the past on the machine. Just like using other programs, I have to habitually look at the online prompts or help of the program before I use them. This look, see the problem, found that there are discrepancies between the online prompt and the help document. Of course, there are a few who have discrepancies, and most of them are perfect. The discrepancies are not limited to diagnostic tools, as is the case in the management that has already been introduced. Is there still in the tool behind, I have not come and finished reading. The parts that come in and out have parameters and switches. There are more and more places here, and there have been fewer places here. As for the details, the article has already pointed out that it will not be repeated here. Therefore, when using the support tools, don't trust the help documentation too much. Be sure to check the online prompts.
3. Can not look down on cmd.exe
The working environment of the support tool is relatively "bad", not limited resources, or system failure. Working in such a limited resource or fault environment is like showing a thousand miles in a square, and the difficulty can be imagined. Therefore, you can only choose the command line mode that takes up less resources. Since the command line is used, the command interpreter is required. In Windows 2000, the command interpreter is cmd.exe. This is a program that doesn't seem to be eye-catching. The successful startup interface does not have the dos mode window in win95 and 98. But after using it, I thought it was a light look at it - this is actually a very powerful program.
Many of the programs in the support tool can only be run on cmd, and some tools can be run in both environments (command line environment and GUI environment).
cmd itself has very detailed prompt information. In the Chinese professional version of windows2000, the online prompt information of cmd is also Chinese, so it is very convenient to use. In the prompt message, there is also a so-called extension command, which is a bit like an external command in dos. All extension commands are as follows:
Command line extensions include changes and/or additions to the following commands:
DEL or ERASE
COLOR
CD or CHDIR
MD or MKDIR
PROMPT
PUSHD
POPD
SET
SETLOCAL
ENDLOCAL
IF
FOR
CALL
SHIFT
GOTO
START (also includes External commands invoke changes made)
ASSOC
FTYPE
For more information, type the HELP command name.
There are several ways to open the cmd of the command line program: 1. Click on the mouse click on "Start -> Run -> Browse" and find "“cmd.exe” after “OK”, It can be started. 2. If you have a support tool installed, the command line tool will be displayed in the desktop menu. The specific location is: Start-Programs-Windows 2000 Support Tools-Tools-command prompt. 3. After booting or restarting, according to the screen Tip, press the F8 key at the right time, then there will be a menu to select the startup mode, select the safe mode with the command line to start, you can directly enter the command line interface. Because Windows 2000 has strict security requirements, even in this case, you must log in with a password before you can successfully start.
cmd is not designed for support tools only, nor can it be used without installing support tools. It is actually a shell of the core of the entire system. Therefore, the original dos command can still be applied in the cmd window. If you want to exit cmd, you can type "EXIT" after the system prompt, and then press Enter to return to Windows2000.
Some readers have reported problems with batch Windows auto-upgrade files. Some patch packages have
In the LAN environment, many common workstations may not have timely installation of system patches
V. Personalization & ldquo;Task Bar & rdquo; & "Start” Menu On the right side of the win
The volume adjustment function provided by Windows 2000 allows the user to easily change the volume
Windows 2000 installation fonts
Windows Server 2008 Virtualization Feature Resolution
Win2K "secret weapon" file version viewing tool
Windows 2000 Server system account security settings tips
Microsoft: Windows Server 2008 saves 10% power
New SAM file - win2k Active Directory database file ntds.dit
Windows HPC Server 2008 Shows Dew
WindowsServer2003 three practical small flexible technology
Manage Windows Server 2003 Active Directory Tree
Modify the registry to completely block Win 2003 security risks
How does Beyond Compare clear log messages?
Win7 system how to obtain a file or folder
Ubuntu13.04 sets static ip (whether notebook, desktop, virtual machine)
Windows resource sharing hidden tips WIN7 universal
Windows 7 bug fix install update 8024402f error
Teach you to enhance the security performance of Vista and Windows 7 system
How to always display the menu bar
Ubuntu installs AMD proprietary driver steps
Using the command to solve the problem that WinXP control panel can't open