is there any way to tell if a cpu is working with out getting into the bios

[Booh]

I recently got an I-will kk266-r board and 1.2 ghz processor from new egg and am having problems getting it up and running I think that I may have a bad component but I dont know how to tell if its the mobo or processor the processor is putting out heat does that mean that it is working or just that its making heat.

 

[Sochin]

Booh,

What specifically is happening to you? I'm interested in learning more about the nature of your problem because I just bought the same board from the same company, and my system isn't working ideally either.

Here's my deal: I run a Duron 850 off the KK266-R with 256MB of Corsair PC150 SDRAM on one DIMM. I planned to overclock, so I unlocked the CPU; it was tough, but I think I did a clean job. But any time I start the computer up with the FSB jumper on the 133MHz+ pins, the thing won't POST. It starts, it spins up the hard drive, checks the floppy drive, but it won't initialize the display or finish booting. I've tried just about everything I can think of to make it work at 133Mhz FSB: Slowing the RAM timings (always remembering to set the memory bus to "Host Clk&quot, taking the multiplier down ahead of time, jacking up the core voltage, and repeating all of these steps on three different versions of the BIOS... None have worked.

So if your system acts like mine does when the 133MHz FSB is enabled, either we're both idiots or we're entitled to get our money back. Any other Iwill customers out there having the same bad trip?

 

[Sochin]

I think we're actually both idiots.

I was reading another thread started by someone having a similar problem, and one post to it pointed to this article, which I had read but forgot about. Basically it says that this Iwill board (and a few other KT133A boards) with a 133MHz FSB jumper initialize at 133MHz using the default multiplier, so in order to POST your CPU has got to be able to handle running at 133*default multiplier until the BIOS can sort things out using the settings you provide. The article shows a way to change the default multiplier on the CPU, similar to unlocking it.

So best of luck to you in getting it to work. I know what I'll be doing tonight...

 

[etech]

I was having a similar problem.
Tbird AXIAR 1G B

I had some old silve conductive paint that had dried up. I thought it would still work to unlock the bridges so a little toulene and acetone and it was liquid again. To make a long story short the bridges do not seem to be connected. I had set the multiplier at 7.5 and put the jumper on 133. It booted at 133. I had trouble getting the system to start though. It would power on but the monitor would never get a signal.

The quick solution was to uplug the case and press the power button, then it would start up. I finally went back to 100Mhz and set the memory to host+33. I finally remembered to set the multiplier back to default and tried to overclock again. No problems and seems stable at 1.33

Check your unlocking.