Today I installed Windows XP after I just replaced my
motherboard and processor. I hadn't noticed when I
installed XP that my processor speed was set at 1.15ghz
and not 1.53 (the correct speed) in the bios, but once XP
was installed, it seemed like it was too late to adjust
it. Everytime I changed it in my bios, XP would not
boot. I have an Asus A7M266 Motherboard with an Athlon
XP 1800+ Processor. If anyone can help me, it would be
Right, I understand that it doesn't care, but, to my understanding, any adjustments (specifically the motherboard) to the hardware configuration of your computer would make XP believe that you are "pirating" the software because it does not have the same configuration as when it was installed. Maybe that's wrong, but that is what I was told.
Here are the steps that I went through to change the speed:
Hit del at startup
Went into AwardBIOS Setup Utility
The first line reads "Current CPU Speed [1150 mhz]"
The second line reads "Operating Frequency Setting [1150 mhz] (and this is where you can adjust it to 1533 mhz)
Once I do that, it reboots and tries to start up XP, gives me System Halt errors and whatnot, and I can't go any farther until I set it back to 1150mhz.
Another thing I noticed was when I boost the CPU speed up, it boots the FSB (?) Frequency from 100 to 133.
I'm not sure if that helps or not, I'm just not sure what to do from this point. Thanks
First of all you can't change the clock speed (frequency) unless you unlock the CPU by jumping the resistors. It's locked otherwise. Thats why the FSB goes from 100 to 133 - thats the only way to adjust the frequency without unlocking.
Secondly, the errors you're getting don't sound like XP's WPA mechanism denying access. I'm not sure what is says if it wants you to re-activate, but the errors you describe sound like instability errors.
Is there a way to adjust the FSB in smaller incriments? i.e. make it 110 instead of 100? This way it would prove or disprove whether it's WPA or instability errors.
If it's instability, please post more details about your system, including RAM, mobo, processor etc.
<i>It's always the one thing you never suspected.</i>
Gee, I'm getting old, I can't even remember the mobo's I use to have. Anyway that sounds like one I had, making that mobo about a year+ old. I remember flashing the BIOS though, and that was just to support a TB1400. Hmm wonder if that mobo will even support an XP CPU. Do you recall seeing XP support when you bought it? Anyway I agree w jlanka on flashing your BIOS for XP support. If Asus sight doesn't have a flash for you, you can try setting your BIOS to 133x11.5.
1. My Revision is already 1007 (the highest they had on the website), so I figured that should be fine.
2. The company that I bought the board and CPU from had the two as a combo, I'm not sure they would sell me a board that wouldn't support the CPU, do you?
Some places will sell their out dated crap any way they can. That mobo is over a year old, and has several BIOS updates. It sounds like you have the latest ver., but something doesn't sound right. Because you should see support for the XP CPU and that would look like 1500, 1600, 1700,1800. The 1800 being what you want, to give you the 1533MHz. Now if you don't see these settings then something's is wrong, or is not true support. Maybe an early BIOS would read the XP CPU correctly, and when they flashed the BIOS skipping a few of them, something got left out. I don't know, but you should see a 1800 setting.
Interesting. Today I recieved and fitted an Abit KG7 mobo that I had ordered for my new AXP 1600+. The BIOS that came with it didn't even know about AXPs and was dated 08/10/2001. Anyway, after a flash to the latest BIOS xx/xx/2002, I'm running fine now.
allow me to share with you my experience. i have the same board and processor however i was using 98se and came across a similar problem. the asus a7m has the "jumper free" bios feature. when i couldn't get it to cooperate i disabled it and jumped manually to the settings you needed as well. i got the computer to bootstrap load and it indicated the 1.533 freq change showed all the hdd/fdd and pci parameters screen etc. but then hung up or 98 wouldn't load. i couldn't get a boot off of the a: drive and i swapped several fdds and cables and still no boot. i rotated the boot sequence tried swapping AB drives and still no luck the bios is r1003 but with out the fdd i can't begin to flash.
i don't believe this is an os problem. and it is apparent to me that the a7m will support the xp1800 else it wouldn't have registered the manual jump settings?
if you try the manual override be absolutely sure you set the cpu voltage core to no more the 1.5v do this first of all in your jumper journey. i hate burning up processors.
My only guess is that since you were running on a 100FSB and now 133FSB is thinks you have a new system or something and is halting you because of that. I've had to reinstall XP because of a new mobo/processor, but not just a supposibly new processor.
Only thing is I've OC'ed my 1600+ so everything thinks it's a 1700+ and it didn't yell at me, I don't know.
Simply put, for whatever reason your system cannot run at 133FSB. CPU speed is FSBxMultiplier. Your multiplier is 11.5x100=1150mhz.
I would check the RAM. Borrow PC2100 RAM from someone and replace it with what they gave you (they might have given you non-PC2100 RAM).
The ASUS AWARD Bios usually gives you the option of selecting one of the two CPU speeds (basically asking you if you want 100 or 133FSB), in this case 1150 or 1530. If you're selecting 1530 without touching the multiplier setting (which won't boot without an unlocked CPU) and the Bios is updated, check that RAM. Good Luck!
<font color=purple><i>Smokey McPot - Your Baby's Daddy</i></font color=purple>