Holy Crap, it worked

[Gabriel]

Here I am typing on my new PC, with the KX7 and gig of PC2700, and Barton 2500, without doing anything to the BIOS, or reformatting and reinstalling. WCPUID still doesn't recognize it, but at least it is seeing what it is putting out. It's runnin at 36C right now, so I think I can push her with the air cooling a bit. Let me know if you have any suggestions (especially you Mike since this was your board) I did all the settings you suggested in the BIOS with 11x Mult and the 5:2:1 I would be curious to see where else I can go.

Thanks again all,
Gabe
http://www.polarisconcepts.com/firstrun.bmp

[Synthohol]

there is a newer wcpuid out, i had to d/l it or my 2100+ wasnt recognized, it gave me unknown something errors.
search oda's site for newer prog.
good luck:)
im running ver 3.1

[Synthohol]

this may be better. dont search, here it is:)

[mdzcpa]

Great news Gabriel!

Since your running that CPU at stock speeds at 166 x 11, I'd just start nudging up the FSB a little and see how far you can go. However, getting too far from 166mhz will start to stress your other components a little as you do not have any higher AGP/PCI divisors to use, nor do you want to stress 1 gig of 2700 memory spec'd only to run at 166mhz.

Have you tried changing the multiplier to 11.5 or 12?

If you can do this, than you can OC the chip and keep the FSB at 166 and not overclock the rest of the system. This would be optimal for your use.

Those xp 2500s are great overclockers. I just had one do 2.1ghz on stock voltage with the OEM HSF. Unfortunately the customer wanted to run it stock at 1.833mhz :(

Anyway, try upping the multiplier. Do not be afraid to add a wee bit of core and voltage along the way:) Just keep your eye on the temps.

[Gabriel]

In case you thought any less, I have learned to tinker in my short days here at LN, and I have managed some decent settings on air cooling, without any hiccups (fingers crossed) Pullin 2023 MHZ at a 169 FSB with a 12 Mult and no problems, although it is very hot in this room. WCPUID is seeing the chip as what it is, but WIN XP still is saying "Unknown Processor" Whatever, at least I am gettin a good read on the chip. I ran burn in on Sandra all night last night, and got up this mornin and it was still goin, so it can't be all bad. Thanks again for the assistance all.

Gabe

[mdzcpa]

Ahhh...sweet! You're already well on your way...good work:D

[Synthohol]

M$ has an AMD cpu update to fix that problem, look in windows update on the M$ site to d/l it :D