SiliconAddict said:
Um yes it does. I've done this on several P3 laptops. As long as the BIOS supports the CPU speed and the clock speed it should work perfectly fine.
And even if it doesn't, you are sometimes OK.
It's been a while since I built a PC, but the last time I did, the clock speed is a function of the FSB speed and a multiplier. The multiplier is configured by 3 or 4 pins on the chip which are toggled on/off either with motherboard jumpers or firmware settings.
The problem with a processor that the BIOS doesn't recognize is that the mapping from the multiplier-pins to actual multipliers isn't the same for every model chip. (e.g. on-off-on may be a 3.5x multiplier on one chip and a 6x multiplier on another.)
If the BIOS supports the chip, it identifies it (via the CPUID instruction, I assume) and will use a lookup table to present you with a convenient list of available multipliers. It will also use this lookup table to figure out what to display for a clock speed on the POST screen.
If the BIOS doesn't support the chip, then you may not see an accurate list. You'll have to do your homework to figure out what it thinks your chip is so you can select the multiplier that sets the correct pins. And the speed displayed by POST may end up being wrong.
Of course, there are sometimes other things in the correct BIOS (like power management schemes) that can come to bite you even if you get the clock speed configured correctly.
I did this years ago (back in the 486 days) to put an AMD 120MHz chip (40MHz x3) into a motherboard that didn't support it. I had to figure out the jumper settings on my own, and the BIOS reported 100MHz (33MHz x3) on the POST screen, but it worked and benchmarks showed that it really was running at 120MHz.
On more modern systems (P2 and P3), I didn't have to do this, because BIOS updates were always available. (It's much easier to update flash than ROM.)
But having said all this, it's probably something I'll never have to do again.
Modern PC motherboards almost always have BIOS updates available to keep pace with all compatible chips. And there's no way I'd risk voiding my AppleCare to try it on a Mac.