Pre-start phase 1. POST process - boot self-test: This is after each computer's power is turned on, the first thing to do. Post will check the hardware, whether there is memory, a keyboard, and SCSI card, etc. Although this is a nuclear operating system unrelated process, he is the first step to ensure the normal start of the system. 2. Once the self-test is complete, the calculation is about to look up the startup device, and put the MBR-Main Boot Record (main boot record) Typically fault: After boot, "Operating System Not Found", prompt "Invalid Partition Table" These error messages have been destroyed because MBR is destroyed; Solution: Start with system boot disk (floppy disk or installation CD) Computer, then execute the following command: fdisk.exe / mbr fdisk / mbr This command can write the main bootrigage and partition table without condition on the hard disk, and does not have the DOS boot sector-dobr-dos boot record, file allocation table and The directory area is initialized; that is, after executing the FDISK / MBR, the main boot program and partition table can be reconstructed without damaging the original data information on the hard disk; he can start the hard disk of the infected guiding area virus. To the role of the virus; FDISK is the standard command in MS-DOS, Windows 95/98 / ME, Windows NT / 2K / XP users, can use the following method to repair the main boot record: Start the system failure recovery console, in the command The prompt is input to the fixmbr, press the Y key at the time of warning information, and finally enter the exit exits the fault recovery console; 3. Calculate is about to find the active partition, the leading sector, and put it into memory; 4. Start call NTLDR, NTLDR is a system loader. He is a key part of the second phase; Plus: Mbr, or the abbreviation of Master Boot Record, meaning in Chinese means the main boot record, the hard disk 0 track first sector is called MBR, his size is 512 bytes, and this area can be divided into two parts: I, pre-boot district (pre-start zone), accounting for 446 bytes: II, the second part is the Partition Table area (partition table) 64 bytes, The area is equivalent to a small program, and the role is to determine that the partition is marked as an active partition, then read the startup area of the partition, and run the code in the area. The last two bytes are an identifier, used to indicate The end of this sector, its binary value is 0x55AA.1. After the NTLDR starts running, it first change the real mode of the processor to 32-bit smooth memory mode; explained: real mode and 32-bit smooth memory mode: Both It is the address of the computer system. Real mode refers to 16-bit mode, running is stable. Smooth Memory mode has a significant advantage in addressing range and speed. 2. Start a small file system (for example, FAT, NTFS) to access files from disk; 3. Subsequently, NTLDR will access the first file: boot.ini File, and according to the contents of the file display the boot menu on the screen; 4. If the user selects not a Win2K (or WinXP) operating system, then NTLDR will call bootsect.dos, hand it over to her, and start the system operated Otherwise, NTLDR will run NTDETECT.COM file; a typical fault After selecting other operating systems, an error message appears: I / O Error Accessing Bot Sector Filemuti (0) Disk (0) Rdisk (0) Partiton (1) This situation is due to the fact that the start-up partition is not found, the installer will originally installing the plurality of operating systems. When you install Win2k on an existing operating system, such as Win98, the installer will Some launch partitions (generally 0 partitions) are saved to bootsect.dos, then the installer puts the Win2K start partition on the 0 partition. Therefore, bootsect.dos is created during the start-up process, cannot be lost like other lost Like the file, you can copy it from the disc, then how to solve this situation? Re-generate a boot partition for the original operating system. For WIN98, just use Win98 boot disk start the system, then enter the command prompt SYS C:, create bootsect.dos: a, put the Win2K installation disc into the optical drive, start the computer; b, after the welcome screen, press the R key; C, when the installer runs to the repair task, Select "Check the Start Sector" option, then move the light bar to "Continue (execute the selected task)", press the Enter; D, follow the installation wizard to continue, and finally see the "Installer has completed the repair" prompt;
E, RESET; 5. NTDetect.com will collect information about computer hardware, including: computer ID number, adapter card type, graphics card, keyboard, mouse, floppy disk, COM port, and parallel ports, etc. Once information is collected, NTDetect.com will pass the information to NTLDR and write information to the HKEY LOCAL MACHINEHARDWARE branch in the registry; you can see: 3 very important files in the startup phase: NTDetect.com, Boot.ini and Bootsect.dos This process is also a place where multiple operating systems often have problems; a typical fault computer starts: No startup menu appears; this is to set the time of the display operating system list to 0 seconds. Solution is , My computer, attribute, advanced, start-up failure, display operating system list ... (Modify time value) Typical fault When the computer starts: NTLDR is missing, Press Any key to restart ... NTLDR file lost, There is an error that causes this fault, and other similar faults, NTDetect.com is missing .., etc., using the following solution: - Use the Win2K installation CD, this file is stored below the i386 directory of the system installation CD, therefore, Just copy it to the hard disk; A, put in the Win2K disc, start the Win2K installation; b, when the welcome interface, press R; C, Win2K repair option interface, press R; D, when prompted to select the repair option At the time, press M; (Manually Repair) E, select Verify the Win2K system file; f, choose to continue (execute the selected task), then enter the return, g, emergency repair disk interface: If you have an emergency repair disk, insert Emergency repair disk, restore the installation according to the prompt, reset; h, if there is no emergency repair disk, press L, use CD, use the console: Enter the MAP, write down the optical drive letter where the Win2K installation disc is, input: Copy L: i386TLDR C: Tips whether it is overwritten, y; input exit restart;
1. At this stage, NTLDR will call ntoskrnl.exe and pass hardware information collected by NTDetect.com to it, and there is also a HAL.dll file. If you have multiple hardware configuration files, when you run Step by step, you will see the information that requests the hardware configuration file on the screen. In addition, NTLDR will also call all the device drivers that start the start value of 0x0 from the registry. If you are in the boot.ini file "/ SOS "parameters, generally behind" / fastdect ", then you will see a list of call devices; an error message appears when the typical fault starts:" Ntoskrnl.exe missing or corrupt on bootup "(Ntoskrnl.exe lost or corrupted) If there is One of the following circumstances, NTOSKRNL.EXE error occurs: - Newly added a hard disk or change the original partition, for example: deleting a partition of a partition or merged the original partition, can cause boot.ini The DEFAULT value of the [Bot Loader] in the file is lost or invalid, so that the file required to start during the startup process; the ntoskrnl.exe file is deleted or damaged; the solution uses the boot disk to start the operating system, edit the boot. INI file, the prosecution with the following lines of similar orders: MUTI (0) Disk (0) RDisk (0) Partition (1) Winnt = "Microsoft Windows 2000 Professional" / fastdect this line is in the first IDE hard disk On the first partition of RDisk (0), Partition (1) has Win2K, you can find the value in your own boot.ini file according to this law; if you don't find an error, please put the Win2K installation CD in Optical drive, then command line input: expand x: i386toskrnl.ex_ c: toskrnl.exe Enter, prompt file has been released, removed, reset; typical fault hal.dll is missing ... This fault is because of lack of hal.dll The file is caused, the solution is: a, start the fault recovery console; B, input: expand x: i386hal.dl_ c: windowssystem32hal.dllc, enter EXIT, Enter; 2. Initialization. This step will be the kernel The hardware driver called in the previous step is initialized .plus: hal.dll, is an abbreviation of the English hardware abstraction layer, hardware abstraction layer, this technology For the excuse between the driver and the hardware, it is possible to prevent the application from directly accessing computer system memory, CPU, and hardware devices (such as sound cards and graphics cards), so that the system can run across multiple hardware platforms; the service call phase will start this stage. Session Manager (SMSS.exe), session management will read the list of programs that must be called, in the box of the registry, then set the memory page and start the Win32 subsystem; Win32 subsystem boot phase once the Win32 subsystem is started, Winlogon.exe will automatically run local security (LSAss.exe) and display the login dialog. Then follow the service controller Screg.exe, the service controller will check the service item that starts 0x2 in the registry, then Calling these services, the service value of 0x3 means that the service that needs to be manually started, the value is 0x4 means disabled; the user login phase is the user login stage, once the user can log in to the system, then the entire startup process has ended, success After logging in, the current setting is also automatically saved as "Last Configuration -last KNown Good" for later use; how to start the fault recovery console 1. Use the Win2k CD to start the computer; 2. Press R; 3 in the welcome interface. Press c to select the use of the failed recovery console to fix the win2k installation; 4. Enter the serial number before the Windows you need to fix, enter; 5. Enter the administrator password, enter
