• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Best program to OC automatically on startup.

homestarmy

Diamond Member
I have just rebuilt a PC for a friend's son, and in doing so, I had to reset the BIOS. The 2600+ Athlon XP now shows as a 2000+.

There is place in the BIOS to change the FSB to fix the issue. I have been in and out of it in every nook and cranny and even updated the BIOS as well, no luck.

I cannot understand how this is possible, but it appears my only fix is to use a utility to change the FSB on startup.

What would be best? Something that could run as a system process and not have a system tray icon would be best. One that could be password protected in the System Tray could work well also if possible.

Thanks!!
 
try s2kctl...don't know if your mobo supports its though...alot of cheap mobo with via/sis chipsets doesnt and can't be overclocked with it...if you're using nforce then theres definitely no problem
 
Looking into it, I found it was a KM 266 or something ending in 266. Maybe I imagined that it was a 2600+, or I saw it from an angle (I have my 19" test monitor way up high, not at the best angle, and thought I saw 2600+.

Did they make a Barton core, 2000+ @ 1.53GHz?
 
um...no, the lowest they went was at least like..2500 or something like that, yeah something is wrong, but the bartons ran at a minimum of 333. i had a 3200 barton.
 
Originally posted by: homestarmy
Did they make a Barton core, 2000+ @ 1.53GHz?

No. It looks like you were right to look for a way to adjust/reset the FSB. It's currently running on a 133(266)MHz FSB, with the default 11.5x multiplier, to give 1.53GHz. The CPU's default FSB is 166(333), to give 1.93GHz - i.e. a Barton 2600+

The mobo might be forcing a 133(266)FSB instead of the CPU default 166(333) because of a hidden or cryptically labelled setting in BIOS (or even a jumper if it's an old-school board). Alternatively it could be that the BIOS does not recognise the Barton core or 166(333)FSB: what date is the BIOS you're using?

 
It must be a cryptically labeled setting, because I have looked EVERYWHERE!

Even though it is a KT266 (or k something 266), it is still possible for it to run at 333? My memory is not so good, I cannot remember about the older chipsets.

It should not be a jumper setting, as I didn't change any on the motherboard, except to reset the BIOS. I'll have to find a manual for the motherboard if possible and look further into it.

Thanks for confirming that I am not going crazy!
 
Back
Top