Discussion Locked

invalid boot.ini error in c: windows

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

hello, I just replaced a bad motherboard, and it was booting fine.

However, I am using an XP 1800+ CPU, and it was only recognizing as a 1150 mhz cpu. So, i went into bios, and changed the settings, to try and get it to recognize as its normal Mhz rate. The only options it had was to change the CPU clock. (min 100, max 132) Im not very good at figuring out what exactly the best setting for the 1800+ would be.. so i just started trying different settings...

Well, now I am just getting the error "Invalid boot.ini file C:/windows" I am lost.. i dont know how to repair the boot.ini at all.. any help would be great.. It will not boot into windows with safe mode or "last known good configuration"

Thanks

12 replies

by wcp

There must be a jumper on the motherboard that set the CPU frequency (or motherboard FSB). Make sure to set it to 133MHz.

by zekeallmon

Also, just so everybody knows, i did go back to bios and load the default settings. Back to where they were before i started messing around.. still no help.

by csmith

Set the base clock back to 100Mhz.
There are two problems here.
The base clock also determines the memory access speed.
Sounds like there is a stick of PC100 RAM hiding in the system. (Can be a mismark problem.)
The Ratings of an AMD processor are the equivalent speed rating to Intel.
The clock is slower.
AMD processors are more efficient per clock.
Thus, if both processors were compared at the same clock rate, the AMD would way outperform the Intel.
So, AMD gives a rating to show the equivalent clock necessary on an Intel.
Kind of confusing, but there are enough people out there, that only have enough knowledge to read the clock speed, so this seems to be necessary.
This can also be a MB/BIOS problem.
When you get this MB working again with the "1150Mhz" cpu speed, run a testing utility, to see how fast the system really is.
You may get a big suprise on the upside or downside.
Regards, Chris

by zekeallmon

Thank you chris. your answer didnt immediately help me with the cpu recognizing, but the emails that we sent back and forth shed light on things i had not thought of.. thank you very much.

by zekeallmon

Thank you... This article is what helped me out. It wasnt exactly what was in that article that helped me, but it was in the Recovery console and repairing the boot.ini. Since, you were the first to answer correctly in this field.. you win... GOOD GAME...

by w2ktechman

if none of those fixes the problem, try doing an os repair. Boot.ini should reside in c:\ not c:\windows. ntdetect.com might be corrupt somehow giving a bad file location.
Also, if a repair doesnt work, if you can, try copying boot.ini to c:\windows.

by rcom

Boot from the Windows CD. When you see the "Welcome to Setup" message, press R to start the Recovery Console.
Type the administrator password.
At the command prompt, type bootcfg /list.
The entries in your current Boot.ini file are displayed on the screen.
Type bootcfg /rebuild.
Follow the on-screen instructions.

The following is an example of how to add a Windows XP installation to the Boot.ini file:
You receive a message that is similar to the following:

Total Identified Windows Installs: 1

[1] C:\Windows
Add installation to boot list? (Yes/No/All)
When you receive the message press Y.

You receive a message that is similar to the following:

Enter Load Identifier

This is the name of the operating system.
type the name of your operating system

You receive a message that is similar to the following:

Enter OS Load options

The instructions that are displayed on your screen may be different depending on the configuration of your computer.
When you receive the message in step e, type /fastdetect, and then press ENTER.
Type exit, to quit Recovery Console.

http://support.microsoft.com/?kbid=330184

by zekeallmon

GOOD GAME.. you are off of injured reserve, and back into the line up as Small forward.. go TEAM!! ( see above to realize im not THAT crazy...)

This discussion is closed to new replies.