1. NTLDR is missing When you upgrade from Win9X to Windows XP
1), Clone later: When you want to upgrade Win9x made with Clone to Windows XP, then It is easy to get a hint: NTLDR is missing. Of course, to meet this situation, the following requirements must be met: a) The system/boot partition is the FAT32 file system. b) The startup of the computer uses the INT-13 interrupt extension to start. Generally, mainstream computers are using this method. c) Because at Clone, the value of the burned system stored in the FAT32 BiOS Parameter Block (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 FAT32 BPB, and then use the Fixboot command in Windows XP to rewrite the Windows XP startup code. The specific operation is as follows: Start a computer with a Win9X boot disk containing SYS.COM, execute the SYS C: 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: perform Windows XP installation in Win9X, the system will restart after copying the file, and the up or down arrow that has been pressed by the back button has been 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 the root directory of the C drive. Umbrella?/p> 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 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 of deleting 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 Windows XP 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 SYS C: command, and then restart, you will find that Windows XP cannot be started. This does not matter, this is normal. 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: perform Windows XP installation in Win9X, the system will restart after copying the file, and the up or down arrow that has been pressed by the back button has been 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 the root directory of the C drive. Umbrella?/p> 3. Boot.ini file is illegal
This problem is generally caused by missing or incorrect format of the boot.ini file. The format of the boot.ini file is generally of the following type: [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" /fastdetect 4, can not find the HAL.DLL file, start abort
This is due to the boot.ini file in the root directory of the C drive Illegal, causing the default to 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 buy a 嗉飧 嫖姨粞 钢 钢 钢 钢 钢 钢 钢 1 1 1 1 1 1 1 1 1 1 1 1 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用 使用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 COPY CON command. Enter Copy Con C:\\boot.ini under 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 1 file(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 it on another computer, copy the source file to the root directory of the damaged C drive. 5, the installation of the simplified Chinese version of Windows XP is not an English prompt when launching the menu
Generally caused by the loss of C:\\bootfont.bin, but if you install a newer version of the English version of Windows, then this The 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 cannot be started after installing Windows 2000. Symptom: When you try to start Windows XP after installing Windows 2000, you may receive the following error message: "Starting Windows... Windows 2000 could not start because the following file Is missing or corrupt:\\WINDOWS\\SYSTEM32\\CONFIG\\SYSTEMd startup options for Windows 2000, press F8. You can attempt to repair this file by starting Windows 2000 Setup using the original Setup floppy disk or CD-ROM. Select 'r' at The first screen to start repair." Cause: The reason for this problem is that Windows XP does not exist when Windows 2000 was 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 resolve this issue, start your computer with Windows 2000 and copy the NTLDR and Ntdetect.com files from the I386 folder on the Windows XP CD to the root of your system drive.