Windows 2000 system guidance process

Introduction
　　
However, during my work over the past two years, I found that many users are not very familiar with the features of Windows 2000, so that after the unfortunate occurrence of system faults or even crashes, just a hasty reinstallation of the system brings about a long restoration of the software environment and painful memories of lost files.
　　
　　
This document applies to Windows 2000, Windows, and Windows XP users.
　　
　　
This article aims to take Windows 2000 as an example to discuss the guiding process of the system, in order to thoroughly reveal the causes of various faults in the guiding process and propose a quick and effective solution.
　　
　　
1. PC-based Windows 2000 Boot Process
　　
The boot process of Windows 2000 on a PC is divided into several stages. By understanding the various stages of the boot process of Windows 2000 and the files used in each stage, this helps us analyze and handle various problems more effectively. The boot process for Windows 2000 is divided into five phases: Pre-boot, Boot, kernel loading, kernel initialization, and system login, as shown in figure 1,
　　　
　　
Figure 1
Table 1 lists the files referenced at different stages of system boot.
　　　
Table 1
　　
Here, we will not discuss the internal working mechanism of the Windows 2000 operating system for the time being. The following is a brief description of what the operating system is doing in these five phases through a combination of texts and texts, those programs play a role.
　　
The first step is the pre-boot phase, as shown in process 2. It first includes the system power-on self-check, which completes the enumeration and configuration of hardware devices. Then, the computer BIOS determines the location of the boot device and loads and runs the Master Boot Record (MBR) Main Boot zone content (such as lilo ). Scan the partition table, locate the active partition, and load the content of the pilot sector on the active partition to the memory for execution. Finally, load the ntldr file in the root directory of the system disk, which is the loader of the Windows 2000 operating system.
　　　
Figure 2
Step 2: In the boot phase, process 3 is shown. First, initialize the boot loader. At this time, ntldr completes processor mode switching and File System (fat or NTFS) driver loading, if a SCSI device is used, ntldr sets ntbootdd. sys is loaded to the memory for running. Secondly, ntldr reads boot from the root directory of the system disk. INI file, the screen shows the boot loader Operating System menu, waiting for the user to select the operating system to load, about boot. the settings of the INI file will be discussed in detail later. If the ntldr does not find the boot. by default, the INI file is loaded from the/winnt location of the first partition of the first disk. If you do not make any choice during the specified period, the default option is enabled. After the Windows 2000 operating system is loaded, ntldr reads and runs the program ntdetect.com to complete hardware detection. If multiple operating systems are installed, if you select to start Windows 98 or Windows ME, ntldr will load and run bootsect. DOS starts the selected operating system. Finally, after ntldr loads Windows 2000 and collects hardware information, it then calls the system's hardware configuration file based on the user's choice. If there is only one hardware configuration file, it is called as the default configuration directly, we strongly recommend that you back up an original hardware configuration file after the system is installed.
　　　
Figure 3
　　
Step 3: Kernel loading stage. process 4: After the system loads the default hardware configuration file, the screen is cleared, and a progress bar (>>>…) is displayed on the screen ...), Ntldris followed by an internal volume operation. ntoskrnl.exe is started first, but not initialized. Load the hardware abstraction layer file (Hal. dll), and then load the Registry key HKEY_LOCAL_MACHINE/system under % SYSTEMROOT/system32/config/system. Then select load control set to initialize the computer. Finally, load the driver of the low-level hardware device according to the control set.
　　
Figure 4
　　
　　
Step 4: Kernel initialization. process 5: When the kernel loading stage ends, the kernel starts initialization and ntldr transfers control of the system to the kernel. The screen displays a graphical interface with A status bar indicating the loading status. After successful initialization, the kernel will use the detected hardware data to create HKEY_LOCAL_MACHINE/hardwa in the registry. The second task is to create a clone control set by copying the control set referenced by the current HKEY_LOCAL_MACHINE/system/select Sub-key. Then the kernel starts to further load and initialize the device driver. Finally, session manager(smss.exe) starts subsystems and services at a higher level in Windows 2000 in sequence.
　　　
Figure 5
　　
Step 5: log on to the system. As shown in step 6, the system starts winlogon.exe first, and then starts local security authority(lsass.exe). The logon dialog box is displayed. Then the system executes service controller(screg.exe) to scan the Registry HKEY_LOCAL_MACHINE/system/CurrentControlSet/Control item again and automatically load the services of the system or users. So far, the user has successfully logged on to Windows 2000, and the system then copied the clone control set to the lastknowngood control set. After the above five steps are successfully completed, it can be called the perfect Boot Process of Windows 2000.
　　　
　　
Figure 6
　　
Ii. Advanced Guidance
　　
Before the system is officially booted, that is, before the third operation in step 2, if you press the F8 key, the advanced boot option is displayed, table 2 provides advanced boot options and their functions for your reference during system boot.
　　　
Table 2
　　
　　
Iii. About the boot. ini file
　　
The second step above mentioned boot. INI file, which is stored in the root directory of the system disk. It is used to locate the hardware location of the loaded operating system, especially when multiple systems are installed to implement the function of selecting boot, the following is a standard boot. INI file, which will be parsed as appropriate.
　　
[Boot loader]
　　
Timeout = 30
　　
Default = multi (0) disk (0) RDISK (0) Partition (1)/winnt
　　
[Operating systems]
　　
Multi (0) disk (0) RDISK (0) Partition (1)/winnt = "Microsoft Windows 2000 Professional"/fastdetect
　　
C:/= "Microsoft Windows 98"
Boot. the INI file consists of two parts: [boot loader] and [operating systems]. [boot loader] includes two parameters: wait time and default boot system. The number after timeout indicates the number of seconds to wait, after default, the system is guided by default. [Operating systems] includes the arc (Advanced RISC computing) boot path (part before the equal sign) for all systems installed) and the name (text between quotation marks) displayed on the menu, and the start parameter (the part behind the slash ). Table 3 below will explain in detail the meaning of the arc path
　　　
　　
Table 3
　　
Note that the number of Multi, SCSI, disk, and RDISK ranges from 0 to 1. Table 4 below explains the meaning of common startup parameters.
　　
　　
Table 4
　　
　　
Because boot. INI is a system protected file, which is hidden in the root directory of the system disk and has read-only attributes, to modify the file, go to the file browser tool> Folder Options> to view all the files and folders, unhide the protected operating system files, and cancel boot. you can use an editor such as NotePad to edit the read-only attribute of an INI file.
　　
　　
　　
4. Create two key floppy disks
　　
　　
We have a detailed understanding of the startup process and related files and programs of Windows 2000. We will plan ahead and arm ourselves with resources, in this way, we are not afraid of the challenges of future failures and crashes.
　　
To create a boot disk for Windows 2000, follow these steps:
　　
　　
1. Format a floppy disk on a computer running Windows 2000.
　　
2. on the primary partition where the system is installed, copy the files shown in the following table to a floppy disk. Note that the hidden files are displayed first.
　　
3. Use the boot disk to boot the system immediately and test whether the system works properly.
　　
Next, we will create another system Urgent Repair Disk, follow the path, start-> Program-> accessories-> System Tools-> Backup, we can easily make an Emergency Repair Disk. Note: The Urgent Repair Disk stores the system registry and startup configuration files, so it can only be used to create this machine. At the same time, the disk content should be updated in a timely manner, especially when new hardware or software is installed on the machine or the system configuration is changed
　　
V. troubleshooting of common guiding faults
　　
　　
So much has been said above to arm yourself as far as possible theoretically. Before entering the actual situation, we will first sort out the equipment we bring, 1) window2000 installation disk 2) Start the floppy disk 3) System Emergency Repair Disk 4) backup of the original system hardware configuration file 5) 6) a calm and clear mind. OK. Join the counter failure group and start!
1) press the power key to start our trip.
　　
　　
2) First, the system starts self-check (post). If a fault occurs before the self-check is completed, consult your hardware supplier J. Fortunately, the system passed the self-check. What? "Missing Operating System "! What should I do?
　　
　　
Diagnosis: This is the most common error after the post is completed. You are lucky. Let's try to recall the pre-boot phase described above. The fault may be caused by the following reasons:
　　
　　
I) The system partition is not activated or failed to be activated. Please use the fdisk tool to activate the solution.
　　
Ii) if the Boot Sector of the system disk is damaged or configured incorrectly, use Windows 2000 to install the disc, run the installer, and use the built-in automatic system recovery function to repair the Boot Sector.
　　
By the way, although this is not a terrible MBR damage, it is also necessary to back up the MBR in a timely manner. It can be easily implemented using tools such as KV 3000.
　　
　　
3) Next, "ntldr is missing "! What should I do?
　　
Diagnosis: This is easy. Use your boot floppy disk to start the boot system, and copy the System File ntldr to the root directory of the system disk. Copy the C root directory for multiple systems.
　　
　　
4) The next failures will be varied, but we all know that the system should read boot at this time. the INI file determines the system location to boot, so if the boot. the INI file has a problem. The simplest way is to copy the boot from the boot disk. INI to the System Disk root directory.
　　
　　
5) if a problem occurs in the hardware configuration file, we can select the original backup configuration file from the configuration file menu to boot the system, or press the L key to call lastknowgood's previous successful configuration boot system. This generally solves related system setup errors.
　　
6) if it does not work, try to see if it can enter the security mode. If it can be logged in, we can use the Hardware Device Manager to eliminate some hardware conflicts, at this time, be sure to display hidden devices. They are likely culprit. Be sure to carefully identify these hidden devices and delete drivers that do not exist or are no longer in use to avoid conflicts. With the addition and deletion programs in the control panel, we can also try to delete programs that may cause system instability. Try to import the previously backed up registry file. We can also use this to repair many minor registry damage faults.
　　
　　
7) if you cannot log on to the security mode or even have a blue screen, it is likely that the system kernel cannot be smoothly initialized and loaded. Most of the causes of such serious faults are the loss of critical system files. Start the boot system with a Windows CD, run the installation program, and select the quick system repair program to try to repair the system. If the quick fix fails, the program will require you to use the Urgent Repair Disk, use the disk you have prepared to try again.
　　
　　
8) for troubleshooting, see table 4 boot. some of the switch options in the INI file use the modified boot. the INI file customizes the boot system to help you locate faults more accurately.
　　
　　
　　
9) during the login process, we may also encounter various software faults, which are not fatal but often annoying. Please try to identify these software or services, in the Start> program> Start Menu, or in the Registry Editor
　　
　　
In the sofeware/Microsoft/Windows/CurrentVersion/run branch of the HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER directory tree, we can view the programs that we have started and delete the programs that are critical to closing the suspicious applications that we have started. Using the Control Panel> Management Tools> Event Viewer in computer management, we can also get a lot of prompts about the cause of the fault. If the service loaded by the system fails, in the computer management> service, set the related service items to manual start, and try to re-run the installation or uninstallation program of the related software to fix similar errors.