Exploring 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, and the problem is always at a loss. 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 question: When you want to upgrade the Win9x made with Clone to WindowsXP, then it is easy to appear Tip: NTLDRismissing.

Of course, to meet this situation, the following requirements must be met:

a) The system/boot partition is the FAT32 file system.

b) The computer starts up 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.

Solution: 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 on the root directory of the C drive.

2, I /O error, Win9X failed to start

This problem is generally caused by the mistake to delete the important file bootsect.dos on the root directory of the C drive to start Win9x. 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.

Solution: Start the computer with a Win9X boot disk containing SYS.COM, 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 is illegal

This problem is generally caused by the loss of the boot.ini file or the incorrect format. 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

[operatingsystems]

multi(0)disk(0)rdisk(0)partition(1)\\Windows="MicrosoftWindowsXPProfessional"/fastdetect

4, can not find the HAL.DLL file, start abort

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 because of you Windows XP is not installed on the C drive, so 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) Start using the Win9X boot disk and edit the file using the EDIT.EXE command. 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 am here not introduced.

4), created later on another computer, copied to the computer damaged root directory of C source files can be covered.

5, the installation of Simplified Chinese version of WindowsXP in the start menu is not in English when prompted

generally due to the C: \\ bootfont.bin lost cause, but a later version of the English version of Windows if you install, so this phenomenon is normal. If not, extract bootfont.bin from the Windows XP installation CD to the root directory of the C drive.

6, after the installation Windows2000 can not start WindowsXP

Symptoms: After installing Windows2000 try to start WindowsXP, you may receive the following error message:

" StartingWindows. ..

Windows2000couldnotstartbecausethefollowingfileismissingorcorrupt:.. \\ WINDOWS \\ SYSTEM32 \\ CONFIG \\ SYSTEMdstartupoptionsforWindows2000, pressF8

YoucanattempttorepairthisfilebystartingWindows2000SetupusingtheoriginalSetupfloppydiskorCD-ROM

Select & rsquo; r & rsquo; 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.

Solution: To solve this problem, start the computer with Windows 2000, 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 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. The way, I hope to help you solve the problem as soon as possible.