Explore the six common startup failures of the XP system.

  
In general, if the system fails, the user will ask a professional or experienced person to help solve the problem. So here to teach some xp system startup problem solving, so you do not have to ask someone else when you encounter problems.
1, NTLDRismissing when you upgrade from Win9X to WindowsXP
1), Clone later problems: When you want to upgrade the Win9x using Clone to WindowsXP, then it is easy to come up with a prompt: NTLDRismissing.
Of course, to meet this situation must meet the following requirements:
a), system /boot partition is the FAT32 file system.
b), the computer is started using the INT-13 interrupt extension. Generally, mainstream computers are using this method.
c), because at Clone, the value of the stored system stored in the FAT32BIOSParameterBlock (BPD) does not match the geometry of the physical drive.
But why can I start Win9X? The reason is this: Win9x ignores the value of BPD when it starts, even if the value is illegal. However, this value is required in Win200/XP. If this value is illegal, the startup will fail.
Resolve: Rewrite the correct value in FAT32BPB, and then use the Fixboot command in WindowsXP to rewrite the Windows XP startup code. The specific operation is as follows: use a Win9X boot disk containing SYS.COM to start the computer, execute the SYSC: command, and then restart, you will find that Windows XP cannot be started. This does not matter, this is a normal phenomenon. Then restart again, use the Windows XP installation CD to boot, enter the Recovery Console, and execute fixboot. If you don't use the Recovery Console, there is another way to do it: Run Windows XP installation in Win9X, the system will restart after copying the file, and the up or down arrow that has to press the arrow keys quickly is started. Then select Windows to return to Win9X, then edit the Boot.ini file, confirm that your Boot.ini file matches the startup of Windows XP on your computer, and finally delete all files starting with $ on the root directory of the C drive.
2), file loss /destruction: This file is located in the root directory of the C drive, we only need to extract this file from the Windows XP installation CD, and then put it in the root directory of the C drive.
2, I /O error, Win9X failed to start
This problem is generally caused by the mistake of deleting the important file bootsect.dos of Win9x on the root directory of the C drive. This file stores the necessary code to start Win9x, and the creation of this file is automatically created when Windows XP is installed. There is no corresponding command in WindowsXP to directly solve this problem. But we can solve it in another way.
Resolve: Use a Win9X boot disk containing SYS.COM to start the computer, execute the SYSC: command, and then restart, you will find that Windows XP cannot be started. This does not matter, this is a normal phenomenon. Then restart again, use the Windows XP installation CD to boot, enter the Recovery Console, and execute fixboot. If you don't use the Recovery Console, there is another way to do it: Run Windows XP installation in Win9X, the system will restart after copying the file, and the up or down arrow that has to press the arrow keys quickly is started. Then select Windows to return to Win9X, then edit the Boot.ini file, confirm that your Boot.ini file matches the startup of Windows XP on your computer, and finally delete all files starting with $ on the root directory of the C drive.
3, Boot.ini file illegal
This problem is generally caused by the loss of the boot.ini file or the format is not correct. The format of the boot.ini file is generally of the following type:
[bootloader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\\Windows< Br>[operatingsystems]
multi(0)disk(0)rdisk(0)partition(1)\\Windows="MicrosoftWindowsXPProfessional"/fastdetect
4, can't find HAL.DLL file, start aborting
This is because the boot.ini file in the root directory of the C drive is illegal, resulting in the default boot from C:\\Windows, but since your Windows XP is not installed on the C drive, the system prompts that the HAL.DLL file cannot be found. The startup thus fails. The solution is to re-edit the Boot.ini file. We have a lot of ways to edit this file. Here are a few easy-to-use instructions for everyone:
1), use Win9X boot disk to start, use EDIT.EXE command to edit this file. After starting EDIT.EXE, just enter the contents of the Boot.ini file in the correct format and save it as a Boot.ini file.
2) Create a Boot.ini file using the COPYCON command. Enter CopyConC:\\boot.ini in DOS and press Enter. Then input according to the format of the Boot.ini file. Press Enter once for each input line. When all the contents are entered, press CTRL+Z and you will see the prompt of ^Z on the screen. At this time, press Enter again, the system will prompt 1file(s)copied. This means the creation is successful.
3), use the bootcfg command in the Recovery Console. Please refer to the Q330184 article for specific usage. I will not introduce it here.
4) After creating on another computer, copy the source file to the root directory of the damaged C drive.
5, the installed simplified Chinese version of WindowsXP is not when launching the menu. English Tips
Generally caused by the loss of C:\\bootfont.bin, but if you install a newer version of Windows, then this phenomenon is very normal. If not, extract bootfont.bin from the Windows XP installation CD to the root directory of the C drive.
6, Windows XP can not be started after installing Windows2000
Symptom: When trying to start Windows XP after installing Windows2000, you may receive the following error message:
"StartingWindows...
Windows2000couldnotstartbecausethefollowingfileismissingorcorrupt:\\WINDOWS \\SYSTEM32\\CONFIG\\SYSTEMdstartupoptionsforWindows2000, pressF8.
YoucanattempttorepairthisfilebystartingWindows2000SetupusingtheoriginalSetupfloppydiskorCD-ROM.
Select’r’atthefirstscreentostartrepair."
Cause: The reason for this problem is that Windows XP does not exist when Windows 2000 is released. The Windows 2000 bootloader does not know that it has been changed in Windows XP. The computer needs to know these changes to load Windows XP.
Resolve: To solve this problem, please start the computer with Windows2000, and then copy the NTLDR and Ntdetect.com files in the I386 folder on the Windows XP CD to the root directory of the system drive.
About the startup failure of the xp system can be divided into many types. Users who are not familiar with the system may be less familiar with these. If you encounter similar problems, you can find a solution based on the corresponding phenomenon. I hope to help you solve the problem as soon as possible.

Copyright © Windows knowledge All Rights Reserved