Question about PC Desktops
Fix the problem
Best Method would be this one, if you have the Windows Disk.
Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file: 1. Use the Windows XP CD-ROM to start your computer. 2. When you receive the message to press R to repair Windows by using the Recovery Console, press the R key. 3. Select the Windows installation that you want, and then type the administrator password when prompted. 4. Type bootcfg /rebuild, and then press ENTER. 5. When the Windows installation is located, the following instructions are displayed: Add installation to boot list? (Yes/No/All)
[Type Y in response to this message.]
Enter Load Identifier:
[This is the name of the operating system. Type Windows XP Professional or Windows XP Home Edition.]
Enter OS Load options:
[Leave this field blank, and then press ENTER]. After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.
After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.
Posted on Nov 11, 2008
Tips for a great answer:
Below is a listing of the full error message that may be related to this error.
Windows NT could not start because the below file is missing or corrupt:
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or just disconnecting the keyboard from the computer.
Before trying any of the below recommendations it's recommend that you load the last known good configuration.
Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and its drive and partition is properly configured in the [boot loader] and [operating systems] section.
Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue.
Microsoft Windows NT and Windows 2000 users:
To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
Missing or corrupt ntoskrnl.exe file
If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
Windows NT installed on a partition bigger then 7.8GB
If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below.
OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.
If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you reinstall Windows.
Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.
Mar 02, 2012 | Gateway GT5026E PC Desktop
on May 03, 2010 | PC Desktops
on Dec 27, 2009 | PC Desktops
Jan 11, 2010 | HP Compaq Presario SR2020NX PC Desktop
Nov 30, 2008 | PC Desktops
Nov 30, 2008 | PC Desktops
Oct 18, 2008 | PC Desktops
Oct 09, 2008 | Dell OptiPlex GX110 PC Desktop
Sep 14, 2008 | PC Desktops
Aug 15, 2008 | Acer PC Desktops
140 people viewed this question
Usually answered in minutes!