dbarrow
07-23-2006, 02:21 PM
http://www.informationweek.com/shared/printableArticle.jhtml?articleID=189400897
...The Rebuild command--technically a software "switch" used with XP's Bootcfg tool--automatically searches a hard drive for valid startup information and files, letting you choose the correct ones. This has the effect of removing and repairing any references to whatever invalid, missing, or corrupt startup information was preventing normal booting. ...
* MUST READ and SAVE article for anyone who does repairs.
This is a new one on me and one I never heard of before.
Being in the process of new build on son's new machine, I decided to give it a try. Still fiddling with the overclock on it and having some difficulty with a fresh install testing different CPU clock speeds, I decided to cut corners a bit.
I took an Acronis image of E: OS partition off daughter's machine and restored it to this machine using Acronis boot cd.
Naturally, it had no existing bootcfg and wouldn't start.
Ran the above procerdure accordingly and it fired right up without any complaints!
Be sure to read and grasp the whole article, including page 2...
...When the Recovery Console option is offered ("Press R to start the Recovery Console"), do so. You may be asked which Windows installation to enter, in which case type the number of the Windows installation you wish to work on (usually "1").
When prompted, enter the Administrator's password for that Windows installation.
At the command prompt, type "Bootcfg /Rebuild" (without the quotes) and hit enter. Windows will then scan the hard drive, looking for valid Windows installs and startup information.
The exact verbiage will depend on your setup, but after a few moments you'll see a prompt that says something like:
Total Identified Windows Installs: 1
[1] C:\Windows
Add Installation To Boot List?
Assuming the information you see is correct, enter "Y" for yes, and Bootcfg will start the process of rebuilding the boot list to include the indicated Windows installation. Along the way, it will repair most "Missing or corrupt HAL.DLL," "Invalid Boot.Ini," "Windows could not start...," and similar errors.
After a moment, you'll be asked to "Enter Load Identifier." This is the name of the operating system that will appear in boot menus. For consistency with the standard nomenclature used by Microsoft, enter "Microsoft Windows XP Professional" or "Microsoft Windows XP Home Edition" without the quotes and hit enter.
Next you'll be asked to "Enter OS Load Options." For normal installations, enter "/Fastdetect" (without the quotes) and hit enter.
In most cases, that's all it will take. You can type "Exit" to leave the Recovery Console and reboot the PC, which should then start normally. ...
...But none of these "edit from within Windows" options is available when Windows won't boot, which is why the Recovery Console's little-known Bootcfg /Rebuild command is so important and useful. If you know about this command and how to use it, you can potentially save yourself literally hours and hours of manually reinstalling or rebuilding a failed operating system! ...
*NOTE additional links at the bottom of page 3
...The Rebuild command--technically a software "switch" used with XP's Bootcfg tool--automatically searches a hard drive for valid startup information and files, letting you choose the correct ones. This has the effect of removing and repairing any references to whatever invalid, missing, or corrupt startup information was preventing normal booting. ...
* MUST READ and SAVE article for anyone who does repairs.
This is a new one on me and one I never heard of before.
Being in the process of new build on son's new machine, I decided to give it a try. Still fiddling with the overclock on it and having some difficulty with a fresh install testing different CPU clock speeds, I decided to cut corners a bit.
I took an Acronis image of E: OS partition off daughter's machine and restored it to this machine using Acronis boot cd.
Naturally, it had no existing bootcfg and wouldn't start.
Ran the above procerdure accordingly and it fired right up without any complaints!
Be sure to read and grasp the whole article, including page 2...
...When the Recovery Console option is offered ("Press R to start the Recovery Console"), do so. You may be asked which Windows installation to enter, in which case type the number of the Windows installation you wish to work on (usually "1").
When prompted, enter the Administrator's password for that Windows installation.
At the command prompt, type "Bootcfg /Rebuild" (without the quotes) and hit enter. Windows will then scan the hard drive, looking for valid Windows installs and startup information.
The exact verbiage will depend on your setup, but after a few moments you'll see a prompt that says something like:
Total Identified Windows Installs: 1
[1] C:\Windows
Add Installation To Boot List?
Assuming the information you see is correct, enter "Y" for yes, and Bootcfg will start the process of rebuilding the boot list to include the indicated Windows installation. Along the way, it will repair most "Missing or corrupt HAL.DLL," "Invalid Boot.Ini," "Windows could not start...," and similar errors.
After a moment, you'll be asked to "Enter Load Identifier." This is the name of the operating system that will appear in boot menus. For consistency with the standard nomenclature used by Microsoft, enter "Microsoft Windows XP Professional" or "Microsoft Windows XP Home Edition" without the quotes and hit enter.
Next you'll be asked to "Enter OS Load Options." For normal installations, enter "/Fastdetect" (without the quotes) and hit enter.
In most cases, that's all it will take. You can type "Exit" to leave the Recovery Console and reboot the PC, which should then start normally. ...
...But none of these "edit from within Windows" options is available when Windows won't boot, which is why the Recovery Console's little-known Bootcfg /Rebuild command is so important and useful. If you know about this command and how to use it, you can potentially save yourself literally hours and hours of manually reinstalling or rebuilding a failed operating system! ...
*NOTE additional links at the bottom of page 3