Classic fault full contact

Installation startup, faults Fault 1. Installation prompt unknown hardware error [Fault phenomenon] After installing Windows XP SP3, restart the computer, prompt "C0000135 unknown hard [Fault analysis] According to the English prompt, it is unknown hardware error The system cannot be installed properly. Under normal circumstances, we generally consider that a hardware device is not compatible with Windows XP SP3, but in fact, if some hardware drivers or software in the original Windows system have compatibility conflicts with SP3, it may cause the installer. Can't work normally or blue screen. [Troubleshooting] Format the system disk C disk, first install Windows XP SP2, note that the hardware driver is not installed at this time. After the SP2 installation is completed, install the SP3 program to upgrade Windows XP from SP2 to SP3. Fault 2. Boot.ini file error [Fault phenomenon] When booting into Windows XP, a pop-up dialog box prompts "Boot.ini file is illegal" and cannot enter the system. [Fault Analysis] The cause of the Boot.ini file being illegal is caused by the loss of the boot.ini file or the file format error. Just restore a boot.ini file or rewrite the correct boot.ini file to solve the problem. [Troubleshooting] First, on other computers with Windows XP installed, click the “Start → Run” command, enter “"c:\\boot.ini” and press Enter to open the boot.ini file. Save the boot.ini file as a file with the same name and copy it to the damaged boot.ini file to overwrite the damaged boot.ini file. If you can't find another computer with Windows XP installed at one time, you can open Notepad and enter the following:

Program code [boot loader] timeout=30 default=multi(0)disk(0) Rdisk(0)partition(1)\\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

After the input is complete, save this file as “boot.ini” and save it to the C drive, overwrite the original boot.ini file, and then restart the computer. If you can't enter the system, you can use Windows PE to boot and modify the boot.ini file of the C drive in Windows PE. Or use the boot disk to boot into the DOS or Recovery Console, enter "Copy Con C: \\ boot.ini", press Enter, press the above Boot.ini file content and format, enter line by line, enter a line to enter once, all After the input, press the shortcut key “Ctrl+Z”, then the prompt of ^Z will appear, then press Enter, prompt “1 file(s) copied”, the boot.ini file is successfully established, and the system is automatically restarted. Normal entry. Hint: If the system prompts that the hal.dll file cannot be found at boot time and cannot enter the desktop and safe mode, this failure is mainly caused by an error in the boot.ini file. According to the above method, using the normal boot.ini to overwrite the problematic boot.ini file or rewriting the boot.ini file can also solve the problem. Fault 3. The system login user password is forgotten [Fault phenomenon] Some people often change the Windows XP system login password yesterday when they use the computer. Today they forget the password and lock themselves in the “outside”. [Troubleshooting] Restart the computer, press the F8 key to bring up the advanced boot option menu, select “with the command line security mode", click “administrator” to enter the command line mode. Enter the command: <quo;net user system login user name 123456 /add”, forcibly change the password of the system login user to “123456”. Or enter the command "net user aaaa 123456 /add"; create a new user aaaa (password is 123456), and then enter the "net localgroup administrators abcdef /add" option to promote the user aaaa to the system administrator. Restart the computer, you can use the changed password “123456” normal login system. Note: The above method cannot retrieve the password, only the password. If the hard disk uses EFS encryption, it will destroy EFS encryption and cause data loss (it is strongly recommended not to use EFS encryption to avoid unnecessary trouble). Fault 4. Windows XP restarts when it enters the system. [Failure] Because the kernel32.dll file is missing or corrupted, Windows XP restarts after half of booting, there is no way to enter the system. [Fault Analysis] For this type of situation, you can solve the problem by replacing it with normal files or returning it back. [Troubleshooting] Put the Windows XP installation CD into the CD, start the recovery console, at the command prompt, type cd system32 and press Enter; then enter ren kernel32.dll kernel32.old and press Enter; then enter the map and Enter; finally enter expand x:i386kernel32.dl_ and press Enter (“x:” is the drive letter), extract the kernel32.dl_ file from the CD to the hard disk and replace the corrupted kernel32.dll file. Enter “exit” and press Enter to restart the computer to start Windows XP normally.