NTLDR is missing how to deal with boot failure
Fault phenomenon: everything is normal after power-on self-test, but when entering the system, that is, when the system boots, it is stuck and displays
NTLDR is missing, Press CTRL + ALT + DEL to restart.
After thinking, the analysis shows:
1.XP system is the NT kernel, and LDR is the abbreviation of loader commonly used in the operating system, so the failure may be caused by the loss of the system boot file, and the name of the file is NTLDR
2. The computer is stuck when entering the operating system, that is, when the system is booting, so it may be judged that the system cannot be booted and the operating system cannot be entered.
The following is a description of the failure on the Microsoft official website:
I receive a "NTLDR is missing" error message when starting the computer
View products to which this article applies
Article ID: 320397
Last modified: August 15, 2005
Revision: 7.0
symptom
After copying multiple files to the root folder of a boot volume that uses the NTFS file system, you may receive the following error message the next time you start the computer:
NTLDR is missing
Press CTRL + ALT + DEL to restart.
If you delete files copied to the root folder, the master file table (MFT) allocation index will not drop to its original size.
the reason:
This problem may occur if the MFT root folder is fragmented. If the MFT root folder contains multiple files, the MFT becomes so fragmented that it needs to create an additional distribution index. Because the files are mapped to the distribution index alphabetically, NTLDR files may be pushed to the second distribution index. If this occurs, you will see the error message described in the "Symptoms" section of this article.
Generally, files are not written to the root folder. This can happen if a program regularly creates and deletes temporary files in the root folder, or by copying many files to the root folder by mistake.
solution
To resolve this issue, please contact Microsoft Product Support Services to obtain the Bcupdate2 utility. For more information on how to contact Microsoft Product Support Services, please visit the following Microsoft website:
http://support.microsoft.com/selectassist&nbs ... microsoft.com/selectassist)
alternative method
To work around this problem, create a startup disk to start your computer.
For more information about how to create a startup disk on a Microsoft Windows XP-based computer, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
305595 (http://support.microsoft.com/kb/305595/) How to use Windows XP to create a boot disk for an NTFS or FAT partition
For more information about how to create a startup disk on a Microsoft Windows 2000-based computer, click the following article number to view the corresponding article in the Microsoft Knowledge Base:
119467 (http://support.microsoft.com/kb/119467/) How to create a boot disk for NTFS or FAT partition
[QUOTE The conclusion drawn by ourselves and the description on Microsoft's official website, we can use the "compensation method" to repair, that is, copy the original lost file from another system disk or computer, and make it up. Enter the operating system normally.
The following is a solution based on my own experience and online summary:
Step 1: Through the fault recovery console, (assuming that the G drive is the drive letter of the CD-ROM drive) enter
copy G: \ i386tldr c: \ (Enter),
Step 2: Then enter:
copy G: \ i386tdetect.com c: \ (Enter)
At this time, the system should prompt something, enter y ... and then press Enter. (The problem should be solved at this point, the next step is to confirm, the problem is not solved.)
Step 3: Enter c: \ Boot.ini again, if the information in Boot.ini can be displayed normally, then restart, it means that the problem is solved ..
Fault phenomenon: everything is normal after power-on self-test, but when entering the system, that is, when the system boots, it is stuck and displays
NTLDR is missing, Press CTRL + ALT + DEL to restart.
After thinking, the analysis shows:
1.XP system is the NT kernel, and LDR is the abbreviation of loader commonly used in the operating system, so the failure may be caused by the loss of the system boot file, and the name of the file is NTLDR
2. The computer is stuck when entering the operating system, that is, when the system is booting, so it may be judged that the system cannot be booted and the operating system cannot be entered.
The following is a description of the failure on the Microsoft official website:
I receive a "NTLDR is missing" error message when starting the computer
View products to which this article applies
Article ID: 320397
Last modified: August 15, 2005
Revision: 7.0
symptom
After copying multiple files to the root folder of a boot volume that uses the NTFS file system, you may receive the following error message the next time you start the computer:
NTLDR is missing
Press CTRL + ALT + DEL to restart.
If you delete files copied to the root folder, the master file table (MFT) allocation index will not drop to its original size.
the reason:
This problem may occur if the MFT root folder is fragmented. If the MFT root folder contains multiple files, the MFT becomes so fragmented that it needs to create an additional distribution index. Because the files are mapped to the distribution index alphabetically, NTLDR files may be pushed to the second distribution index. If this occurs, you will see the error message described in the "Symptoms" section of this article.
Generally, files are not written to the root folder. This can happen if a program regularly creates and deletes temporary files in the root folder, or by copying many files to the root folder by mistake.
solution
To resolve this issue, please contact Microsoft Product Support Services to obtain the Bcupdate2 utility. For more information on how to contact Microsoft Product Support Services, please visit the following Microsoft website:
http://support.microsoft.com/selectassist&nbs ... microsoft.com/selectassist)
alternative method
To work around this problem, create a startup disk to start your computer.
For more information about how to create a startup disk on a Microsoft Windows XP-based computer, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
305595 (http://support.microsoft.com/kb/305595/) How to use Windows XP to create a boot disk for an NTFS or FAT partition
For more information about how to create a startup disk on a Microsoft Windows 2000-based computer, click the following article number to view the corresponding article in the Microsoft Knowledge Base:
119467 (http://support.microsoft.com/kb/119467/) How to create a boot disk for NTFS or FAT partition
[QUOTE The conclusion drawn by ourselves and the description on Microsoft's official website, we can use the "compensation method" to repair, that is, copy the original lost file from another system disk or computer, and make it up. Enter the operating system normally.
The following is a solution based on my own experience and online summary:
(Step 1) Through the fault recovery console, (assuming that the G drive is the drive letter of the optical drive ...) enter
copy G: \ i386tldr c: \ (Enter),
Then enter:
copy G: \ i386tdetect.com c: \ (Enter)
At this time, the system should prompt something, enter y ... and then press Enter. (The problem should be solved at this point, the next step is to confirm, the problem is not solved.)
Then enter c: \ Boot.ini, if the information in Boot.ini can be displayed normally, then restart, it means that the problem is solved ...
summary of the issue:
The NTLDR file is the boot file of WinXP. It should be backed up when the system is normal.
Description of NTLDR file: NTLDR is a hidden, read-only system file used to load the operating system.
Extraction of NTLDR file: NTLDR file is the boot file of WinXP. When this file is lost, the system will prompt that it is missing and asks to press any key to restart. The file can be extracted under the fault recovery console. This file exists in the i386 directory of the installation CD. The extraction method is as follows:
Enter the system failure recovery console, go to the C drive, enter "copy X \ I386 \ NTLDR" (Note: X here is the drive letter of the optical drive) and press Enter, if the system prompts whether to overwrite, press "Y", and then Enter the exit command to exit the console and restart.
ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼
Attached:
XP system boot process:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system
* If NT / XP is selected, NTLDR runs Ntdetect.com
* For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it.
The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection, and loads the device driver configuration so that the device starts to work at startup
12.Ntldr gives control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
Here are two examples:
Example 1: A few days ago, I took a hard drive with VISTA system and hung it in my host computer with WINDOWS XP. When I found VISTA in the newly added hard drive, I directly pressed shutdown.
When I restarted again, I found that ntldr is missing. So I started with WINDOWS XP and then entered the recovery console. Then, press the "1" key and press Enter to log in to your Windows
Enter your Administrator account and password
Copy the two files to the partition where the system is located, assuming that your CD-ROM drive is the F drive letter. Follow the example below:
copy F: \ i386tldr c: \
copy F: \ i386tdetect.com c: \
Then restart, as a matter of course, this should be able to solve the problem, but I still ntldr is missing after restarting. At first I thought that the failure recovery failed, so I used GHOST to restore the system. After the recovery is complete, ntldr is missing. I do not quite understand. Then I simply use the WINDWOS XP installation disk to install the system. Start as usual and start copying files. But after rebooting again it was damn ntldr is missing to report an error! At this point, my mind started to get a little hot! I suddenly remembered that I had more than one hard drive. Has the boot position of the hard drive been changed? So after booting, press F12 to select the boot directory and select the disk from which the system is installed. As a result, the damn ntldr is missing error no longer appears. So please pay attention, when there are multiple hard drives, we must pay attention to the starting position!
Example 2: The hard disk on a laptop is partitioned and formatted on a desktop computer, and DOS is installed. Enter the WINDOWS2000 installation file. Replace the IBM X22 notebook and install the WIN2000 operating system under DOS. After restarting, NTLDR is missing but running DOS Everything is normal.
According to the analysis, different hard disks are partitioned and formatted on different machines. Different south bridges will write different partition table information, and IBM T21 can only recognize the partitions operated by the 440BX south bridge, resulting in the system not reading NTLDR files correctly , Re-use the IBM T21 partition, formatting and installing the system everything is normal.
Note: The NTLDR file is the boot file of win nt / win200 / WinXP / win2003. When this file is missing, the system will prompt "NTLDR is missing ..." and asks to press any key to restart. It cannot enter the system correctly. So it should be backed up when the system is normal. What is the NTLDR file? How can we fix the failure of the NTLDR file type?
The NTLDR file is a hidden, read-only system file, located in the root directory of the system disk, used to load the operating system.
The general system boot process is this:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system * If NT / XP is selected, NTLDR runs Ntdetect.com. For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it. The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection and loads the device driver configuration so that the device starts to work at startup 12.Ntldr hands control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
The solution to this failure in Windows XP
When this file is lost, we can extract it from the installation CD by:
1. Enter the system failure recovery console.
2. Go to drive C.
3. Enter "copy X: \ I386 \ NTLDR c: \" (Note: X is the drive letter of the optical drive) and press Enter. If the system prompts whether to overwrite, press "Y", then enter the exit command to exit the console and restart That's it.
The solution to this failure in Windows 2003 server
1. Start the computer with the installation disk of Windows 2003 and enter the installation interface of Windows 2003 Server;
2. The interface prompts "To repair the installation of Windows 2003 server, please press R", press R to continue;
3. The failure recovery console prompt "C: \ Winnt, which Windows 2003 installation (to cancel, press Enter)?" Appears, type "1" here, and then press Enter;
4. Type the administrator password and press Enter;
5. Type Copy H: \ WIN2003 \ ENT \ I386 \ Ntldr c: \, and press ENTER (Note: The CD I use is a Windows 2003 2-in-1 CD. If it is another installation disk, you can use the search command to find ntldr The location of the file is generally in the i386 directory. "H:" is my CD-ROM drive letter), if the system prompts you to overwrite the file, type Y, and then press the Enter key Failure phenomenon: power-on self-test everything is normal, but after entering the system , That is, when the system boots, it is stuck and displays
NTLDR is missing, Press CTRL + ALT + DEL to restart.
After thinking, the analysis shows:
1.XP system is the NT kernel, and LDR is the abbreviation of loader commonly used in the operating system, so the failure may be caused by the loss of the system boot file, and the name of the file is NTLDR
2. The computer is stuck when entering the operating system, that is, when the system is booting, so it may be judged that the system cannot be booted and the operating system cannot be entered.
The following is a description of the failure on the Microsoft official website:
I receive a "NTLDR is missing" error message when starting the computer
View products to which this article applies
Article ID: 320397
Last modified: August 15, 2005
Revision: 7.0
symptom
After copying multiple files to the root folder of a boot volume that uses the NTFS file system, you may receive the following error message the next time you start the computer:
NTLDR is missing
Press CTRL + ALT + DEL to restart.
If you delete files copied to the root folder, the master file table (MFT) allocation index will not drop to its original size.
the reason:
This problem may occur if the MFT root folder is fragmented. If the MFT root folder contains multiple files, the MFT becomes so fragmented that it needs to create an additional distribution index. Because the files are mapped to the distribution index alphabetically, NTLDR files may be pushed to the second distribution index. If this occurs, you will see the error message described in the "Symptoms" section of this article.
Generally, files are not written to the root folder. This can happen if a program regularly creates and deletes temporary files in the root folder, or by copying many files to the root folder by mistake.
solution
To resolve this issue, please contact Microsoft Product Support Services to obtain the Bcupdate2 utility. For more information on how to contact Microsoft Product Support Services, please visit the following Microsoft website:
http://support.microsoft.com/selectassist&nbs ... microsoft.com/selectassist)
alternative method
To work around this problem, create a startup disk to start your computer.
For more information about how to create a startup disk on a Microsoft Windows XP-based computer, click the article number below to view the corresponding article in the Microsoft Knowledge Base:
305595 (http://support.microsoft.com/kb/305595/) How to use Windows XP to create a boot disk for an NTFS or FAT partition
For more information about how to create a startup disk on a Microsoft Windows 2000-based computer, click the following article number to view the corresponding article in the Microsoft Knowledge Base:
119467 (http://support.microsoft.com/kb/119467/) How to create a boot disk for NTFS or FAT partition
[QUOTE The conclusion drawn by ourselves and the description on Microsoft's official website, we can use the "compensation method" to repair, that is, copy the original lost file from another system disk or computer, and make it up. Enter the operating system normally.
The following is a solution based on my own experience and online summary:
(Step 1) Through the fault recovery console, (assuming that the G drive is the drive letter of the optical drive ...) enter
copy G: \ i386tldr c: \ (Enter),
Then enter:
copy G: \ i386tdetect.com c: \ (Enter)
At this time, the system should prompt something, enter y ... and then press Enter. (The problem should be solved at this point, the next step is to confirm, the problem is not solved.)
Then enter c: \ Boot.ini, if the information in Boot.ini can be displayed normally, then restart, it means that the problem is solved ...
summary of the issue:
The NTLDR file is the boot file of WinXP. It should be backed up when the system is normal.
Description of NTLDR file: NTLDR is a hidden, read-only system file used to load the operating system.
Extraction of NTLDR file: The NTLDR file is the boot file of WinXP. When this file is missing, the system will prompt that it is missing and asks to press any key to restart. It cannot enter the WinXP system correctly. The file can be extracted under the fault recovery console. This file exists in the i386 directory of the installation CD. The extraction method is as follows:
Enter the system failure recovery console, go to the C drive, enter "copy X \ I386 \ NTLDR" (Note: X here is the drive letter of the optical drive) and press Enter, if the system prompts whether to overwrite, press "Y", and then Enter the exit command to exit the console and restart.
ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼
Attached:
XP system boot process:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system
* If NT / XP is selected, NTLDR runs Ntdetect.com
* For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it.
The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection, and loads the device driver configuration so that the device starts to work at startup
12.Ntldr gives control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
Here are two examples:
Example 1: A few days ago, I took a hard drive with VISTA system and hung it in my host computer with WINDOWS XP. When I found VISTA in the newly added hard drive, I directly pressed shutdown.
When I restarted again, I found that ntldr is missing. So I started with WINDOWS XP and then entered the recovery console. Then, press the "1" key and press Enter to log in to your Windows
Enter your Administrator account and password
Copy the two files to the partition where the system is located, assuming that your CD-ROM drive is the F drive letter. Follow the example below:
copy F: \ i386tldr c: \
copy F: \ i386tdetect.com c: \
Then restart, as a matter of course, this should be able to solve the problem, but I still ntldr is missing after restarting. At first I thought that the failure recovery failed, so I used GHOST to restore the system. After the recovery is completed, it is still ntldr is missing. I do not quite understand. Then I simply use the WINDWOS XP installation disk to install the system. Start as usual and start copying files. But after rebooting again it was damn ntldr is missing to report an error! At this point, my mind started to get a little hot! I suddenly remembered that I had more than one hard drive. Has the boot position of the hard drive been changed? So after booting, press F12 to select the boot directory and select the disk from which the system is installed. As a result, the damn ntldr is missing error no longer appears. So please pay attention, when there are multiple hard drives, we must pay attention to the starting position!
Example 2: The hard disk on a laptop is partitioned and formatted on a desktop computer, and DOS is installed. Enter the WINDOWS2000 installation file. Replace the IBM X22 notebook and install the WIN2000 operating system under DOS. After restarting, NTLDR is missing, but running DOS Everything is normal.
According to the analysis, different hard disks are partitioned and formatted on different machines. Different south bridges will write different partition table information, and IBM T21 can only recognize the partitions operated by the 440BX south bridge, resulting in the system not reading NTLDR files correctly , Re-use the IBM T21 partition, formatting and installing the system everything is normal.
Note: The NTLDR file is the boot file of win nt / win200 / WinXP / win2003. When this file is missing, the system will prompt "NTLDR is missing ..." and asks to press any key to restart. It cannot enter the system correctly. So it should be backed up when the system is normal. What is the NTLDR file? How can we fix the failure of the NTLDR file type?
The NTLDR file is a hidden, read-only system file, located in the root directory of the system disk, used to load the operating system.
The general system boot process is this:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system * If NT / XP is selected, NTLDR runs Ntdetect.com. For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it. The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection and loads the device driver configuration so that the device starts to work at startup 12.Ntldr hands control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
The solution to this failure in Windows XP
When this file is lost, we can extract it from the installation CD by:
1. Enter the system failure recovery console.
2. Go to drive C.
3. Enter "copy X: \ I386 \ NTLDR c: \" (Note: X is the drive letter of the optical drive) and press Enter. If the system prompts whether to overwrite, press "Y", then enter the exit command to exit the console and restart That's it.
The solution to this failure in Windows 2003 server
1. Start the computer with the installation disk of Windows 2003 and enter the installation interface of Windows 2003 Server;
2. The interface prompts "To repair the installation of Windows 2003 server, please press R", press R to continue;
3. The failure recovery console prompt "C: \ Winnt, which Windows 2003 installation (to cancel, press Enter)?" Appears, type "1" here, and then press Enter;
4. Type the administrator password and press Enter;
5. Type Copy H: \ WIN2003 \ ENT \ I386 \ Ntldr c: \, and press ENTER (Note: The CD I use is a Windows 2003 2-in-1 CD. If it is another installation disk, you can use the search command to find ntldr The location of the file is generally in the i386 directory. "H:" is my CD-ROM drive letter), if the system prompts you to overwrite the file, type Y, and then press Enter. The NTLDR file is the WinXP boot file. It should be backed up when the system is normal.
Description of NTLDR file: NTLDR is a hidden, read-only system file used to load the operating system.
Extraction of NTLDR file: The NTLDR file is the boot file of WinXP. When this file is missing, the system will prompt that it is missing and asks to press any key to restart. It cannot enter the WinXP system correctly. The file can be extracted under the fault recovery console. This file exists in the i386 directory of the installation CD. The extraction method is as follows:
Enter the system failure recovery console, go to the C drive, enter "copy X \ I386 \ NTLDR" (Note: X here is the drive letter of the optical drive) and press Enter, if the system prompts whether to overwrite, press "Y", and then Enter the exit command to exit the console and restart.
ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼ï¼
Attached:
XP system boot process:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system
* If NT / XP is selected, NTLDR runs Ntdetect.com
* For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it.
The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection, and loads the device driver configuration so that the device starts to work at startup
12.Ntldr gives control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
Here are two examples:
Example 1: A few days ago, I took a hard drive with VISTA system and hung it in my host computer with WINDOWS XP. When I found VISTA in the newly added hard drive, I directly pressed shutdown.
When I restarted again, I found that ntldr is missing. So I started with WINDOWS XP and then entered the recovery console. Then, press the "1" key and press Enter to log in to your Windows
Enter your Administrator account and password
Copy the two files to the partition where the system is located, assuming that your CD-ROM drive is the F drive letter. Follow the example below:
copy F: \ i386tldr c: \
copy F: \ i386tdetect.com c: \
Then restart, as a matter of course, this should be able to solve the problem, but I still ntldr is missing after restarting. At first I thought that the failure recovery failed, so I used GHOST to restore the system. After the recovery is completed, it is still ntldr is missing. I do not quite understand. Then I simply use the WINDWOS XP installation disk to install the system. Start as usual and start copying files. But after rebooting again it was damn ntldr is missing to report an error! At this point, my mind started to get a little hot! I suddenly remembered that I had more than one hard drive. Has the boot position of the hard drive been changed? So after booting, press F12 to select the boot directory and select the disk from which the system is installed. As a result, the damn ntldr is missing error no longer appears. So please pay attention, when there are multiple hard drives, we must pay attention to the starting position!
Example 2: The hard disk on a laptop is partitioned and formatted on a desktop computer, and DOS is installed. Enter the WINDOWS2000 installation file. Replace the IBM X22 notebook and install the WIN2000 operating system under DOS. After restarting, NTLDR is missing, but running DOS Everything is normal.
According to the analysis, different hard disks are partitioned and formatted on different machines. Different south bridges will write different partition table information, and IBM T21 can only recognize the partitions operated by the 440BX south bridge, resulting in the system not reading NTLDR files correctly. , Re-use the IBM T21 partition, formatting and installing the system everything is normal.
Note: The NTLDR file is the boot file of win nt / win200 / WinXP / win2003. When this file is missing, the system will prompt "NTLDR is missing ..." and asks to press any key to restart. It cannot enter the system correctly. So it should be backed up when the system is normal. What is the NTLDR file? How can we fix the failure of the NTLDR file type?
The NTLDR file is a hidden, read-only system file, located in the root directory of the system disk, used to load the operating system.
The general system boot process is this:
1. The power supply self-test program starts to run
2. The master boot record is loaded into memory, and the program begins to execute
3. The boot sector of the active partition is loaded into memory
4. NTLDR is loaded and initialized from the boot sector
5. Change the real mode of the processor to 32-bit smooth memory mode
6. NTLDR starts to run the appropriate small file system driver. The small file system driver is built in NTLDR, it can read FAT or NTFS.
7. NTLDR reads the boot.ini file
8. NTLDR loads the selected operating system * If NT / XP is selected, NTLDR runs Ntdetect.com. For other operating systems, NTLDR loads and runs Bootsect.dos and passes control to it. The windows NT process ends.
9.Ntdetect.com searches the computer hardware and transfers the list to NTLDR in order to write this information into HKE Y_LOCAL_MACHINEHARDWARE.
10. Then NTLDR loads Ntoskrnl.exe, Hal.dll and system information collection.
11.Ntldr searches the system information collection and loads the device driver configuration so that the device starts to work at startup 12.Ntldr hands control to Ntoskrnl.exe, at this time, the startup process ends and the loading phase begins
The solution to this failure in Windows XP
When this file is lost, we can extract it from the installation CD by:
1. Enter the system failure recovery console.
2. Go to drive C.
3. Enter "copy X: \ I386 \ NTLDR c: \" (Note: X is the drive letter of the optical drive) and press Enter. If the system prompts whether to overwrite, press "Y", then enter the exit command to exit the console and restart That's it.
The solution to this failure in Windows 2003 server
1. Start the computer with the installation disk of Windows 2003 and enter the installation interface of Windows 2003 Server;
2. The interface prompts "To repair the installation of Windows 2003 server, please press R", press R to continue;
3. The failure recovery console prompt "C: \ Winnt, which Windows 2003 installation (to cancel, press Enter)?" Appears, type "1" here, and then press Enter;
4. Type the administrator password and press Enter;
5. Type Copy H: \ WIN2003 \ ENT \ I386 \ Ntldr c: \, and press ENTER (Note: The CD I use is a Windows 2003 2-in-1 CD. If it is another installation disk, you can use the search command to find ntldr The location of the file is generally in the i386 directory. "H:" is my CD-ROM drive letter), if you are prompted to overwrite the file, type Y, and then press Enter
LED Street Lights offer longer operating lifetime, lower maintenance requirements and cost reductions over other bulbs. G-Lights has a wide variety of LED street lights for sale. LED street lights by G-Lights offer a long life span and extreme reliability, both important characteristics for street light selection. When you are interested in installing new LED Street Light, we offer a wide selection of LED street lights to choose from. LED street lighting comes in a variety of light distribution options, which is important in achieving the desired light cast. 5 year warranty provides you a good support for the project.
Led Street Light,Led Street Light Price List,Big Led Street Light,Led Street Light Price
ZHONGSHAN G-LIGHTS LIGHTING CO., LTD. , https://www.glightsled.com