Im doing some research right now but I think I might need to revert back to that older BIOS. This current bios really doesnt have much for over clocking. The biggest performance boost so far was a manual change to the AGP Driving control from EA to maxed out at FF. I also dropped my CAS Latency from 2.5 to 2. Both of these settings were unstable before cooling was applied.
By the way thanks Nick!
So you are dealing with an older rig. I have not seen AGP drive control in many years. I think the last time was around 2003.
Older system interface terms such a AGP Drive Control with their hex values instead of reading the video card BIOS and tuning that by the video card manufacture setup. That AGP/DC setting is available in your BIOS for that reason. Later motherboards and BIOS designs were collaborated on between the manufactures so the user did not have to deal with that. Enabling things such as FAST WRITES or AGP 3.0 Calibration automatically made those changes.
Sometimes the latest BIOS is not the best. And, there are people out there who write and edit hacked BIOSes for motherboards. Another handy tool was WPCREDIT/WPCRSET which allowed direct Windows editing of the chipset registers and would also allow being set at boot. The old AMD systems were tweaked that way. Promise RAID efficiency and speed could be dramatically increased using that interface along with setting CPU and AGP values not available in the BIOS.
As I said, the FSB/memory speed is the key to a clock. GHz is important but the trick is to get the memory talking to the CPU at the speed the CPU wants it. Older systems are very restricted in that area. To get the memory discussing FS9 at the speed the CPU wants to talk about it, means your memory wants to be chatting at about 533Mhz, at least. Older memory and motherboards wont do that soothe goal is to get the memory and FSB up as high as you can, and with that the GHz as high as they will go at the same time with the focus being on the FSB/memory.
The memory timing and sub-timings are also very important, but, the difference between CAS2 and CAS 2.5 when CAS2.5 will allow the memory be run at a much higher speed makes the decision about where that is set. If you were able to run the memory 200MHz higher because you raise CAS to 3, then that would be better than running CAS2 @ default.
It
