Invisible wrote:

> - Build a new BOOT.INI file: bootcfg /all
> 
> - This last command spends a few hours scanning all your HDs looking for 
> anything that looks like a Windows installation. It then gives you an 
> interactive prompt asking which ones to add to the boot menu.

Actually, that's "bootcfg /add" or /rebuild.

And, for whatever reason, it doesn't work. After a while it crashes out 
with an error message about an unreadable filesystem or something.

Interestingly, it seems that placing NTLDR and NTDETECT.COM onto the 
drive is sufficient to make it boot. When you boot the system, it says 
"INVALID BOOT.INI; BOOTING FROM C:\WINDOWS". I'm guessing this only 
works for certain cases. Since by Windows installation is your standard 
"the OS is in the standard place on the first HD", it Just Works(tm).

Weirdly, once Windows has loaded there is apparently no way to recreate 
a correct BOOT.INI file. However, cut-and-pasting the example one from 
M$'s website seems to have fixed things nicely.

Wee, my PC works again! :-D

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message