No biggy, I remembered when Sandra had trouble when KT133A was introduced so I just thought something similar was happening.
I don't know of any programs which I am sure read true speeds. Many just seem to read BIOS settings and video driver settings. As the Sandra notes mention the program probably needs to detect the capabilities of the clock generator in order to produce correct results. (I wonder if boards which can lock AGP and PCI have a separate clock generator for these)?
This is going to sound silly but when I wanted to be sure AGP was where I thought it was. I would use an old DOS based 2D benchmark <b>[EDIT - I mean video memory benchmark. It isn't graphical]</b>. Since there is no software acceleration then the benchmark depends on bandwidth, minus video card latencies. If the benchmark number goes up then I knew AGP was running faster. Crude but it let me know when the dividers were changing. I assumed the PCI divider changed at the same time as AGP. On my KT133A board the dividers changed from 2/3 and 1/3, AGP and PCI respectively, to 1/2 and 1/4 at 128 Mhz (I think it was 128 Mhz) and not 133. This explained why I could run FSB at 128 Mhz but not 120-127 Mhz. Even though I had the CPU at the same level of overclock.
The reason I was playing with FSB below 133 Mhz was I found I could run a Tbird 1.0 at slightly over 1.7 Ghz (for a very short time) at 128 Mhz but couldn't go over about 1.68 Ghz with any other FSB speed. (I didn't try every combination; something like 130 Mhz, 133 Mhz, 140 Mhz, 145 Mhz, 150, Mhz, and 154 Mhz were the other ones I tried besides 128 Mhz and lower).
At the time the version of Sandra I had did not detect the correct AGP/PCI/ISA speeds. Come to think of it I don't know if it does now.
<b>I type sixty words per minute. Ten are spelled correctly.</b><P ID="edit"><FONT SIZE=-1><EM>Edited by phsstpok on 10/26/02 03:23 PM.</EM></FONT></P>