Invalid boot.ini file

[Charles Ancira]

I have used the prescribed procedures (MS 330184) to
correct this problem but have not succeeded. When I
type "bootcfg /list" it says there is nothing to display.
When I type "bootcfg /rebuild" it goes through all the
motions but when I get to the end it tells me "failed to
add selected boot entry to the boot list". No reason is
given and I can't find anything in the knowledge base
that explains what to do next. Anybody have a suggestion?
Please respond by email. Thanks.
Charlie

 

[Doug Knox MS-MVP]

Once you're in Windows, go to Control Panel, System, Advanced, Startup and
Recovery, Settings. In the System startup section, click the Edit button.
This will open BOOT.INI in Notepad.

A basic BOOT.INI for a single IDE hard disk system with XP installed on C:
looks like this:

[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"
/fastdetect

 

[Larry(LJL269)]

Doug - I got 3-4 boot.ini's on C: 1 in PM pgm folder, 1
of form boot.ini.xxx where xxx was something that made
me guess it was a backup,... Perhaps 1 of them is
usefull.

Thanks- bye- Larry


On Thu, 2 Oct 2003 17:43:50 -0400, "Doug Knox MS-MVP"

|Once you're in Windows, go to Control Panel, System, Advanced, Startup and
|Recovery, Settings. In the System startup section, click the Edit button.
|This will open BOOT.INI in Notepad.
|
|A basic BOOT.INI for a single IDE hard disk system with XP installed on C:
|looks like this:
|
|[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"
|/fastdetect


Any advice given is my attempt to show appreciation for all
the excellent help I've received here but I'm no MVP so it
may only apply NUGS. Personal attacks, nitpicking & criticism
of anything but content will NOT be responded to. Those
posters should spend their time taking the test @
http://www.nimh.nih.gov/publicat/ocdtrt1.htm

 

[Doug Knox MS-MVP]

Larry,

The only BOOT.INI file you're concerned with is the Hidden one in the root
directory of your boot drive. If it doesn't exist, create a new one.

Follow the directions I gave you earlier to access it. This will ensure you
get the correct one.

 

[Larry(LJL269)]

Yea- since I dual-boot XP, I just started to consider
what I'd do if boot.ini got corrupted on either system.
Didnt want to have to figure out those hierogliphics
twice

Think I can get CSafe to store it with Registry each
day and archive 8 days. I know u can for autoexec,
win.ini, and 5 others but they dont list boot.ini.
Maybe they figure u can do it with Recovery Console as
u outlined. Another Q 4 TS

Comments/suggestions/corrections appreciated.
Thanks- Larry


On Fri, 3 Oct 2003 22:49:02 -0400, "Doug Knox MS-MVP"

|Larry,
|
|The only BOOT.INI file you're concerned with is the Hidden one in the root
|directory of your boot drive. If it doesn't exist, create a new one.
|
|Follow the directions I gave you earlier to access it. This will ensure you
|get the correct one.


Any advice given is my attempt to show appreciation for all
the excellent help I've received here but I'm no MVP so it
may only apply NUGS. Personal attacks, nitpicking & criticism
of anything but content will NOT be responded to. Those
posters should spend their time taking the test @
http://www.nimh.nih.gov/publicat/ocdtrt1.htm

 

[Doug Knox MS-MVP]

Larry,

There is only one BOOT.INI file, with entries for each system. Unless
you're adding operating systems on a frequent basis, you should only need
one backup copy, stored in a safe location. You can also use Recovery
Console and use the BOOTCFG /REBUILD command to scan your system for OS's
and recreate it in an emergency.

 

[Larry(LJL269)]

On Sat, 4 Oct 2003 08:41:27 -0400, "Doug Knox MS-MVP"

|You can also use Recovery
|Console and use the BOOTCFG /REBUILD command to scan your system for OS's
|and recreate it in an emergency
Good to know. I did get CSafe to store it with Registry
each day and archive both for 8 days.

Having a safe copy is easy. Finding & installing it
'under fire' is hard part. I try to keep number of
approaces/apps I use to minimum in such situations.

Thanks for ur help in yet another PC learning
experience. Larry

Any advice given is my attempt to show appreciation for all
the excellent help I've received here but I'm no MVP so it
may only apply NUGS. Personal attacks, nitpicking & criticism
of anything but content will NOT be responded to. Those
posters should spend their time taking the test @
http://www.nimh.nih.gov/publicat/ocdtrt1.htm