"Brian J. Beesley" wrote:
> On 6 Mar 00, at 6:43, Matthew Temus Smith wrote:
>
> > Funny you should have that problem. My main computer is
a Pentium III
> > desktop overclocked to 600MHz. Once I got mprime
(that's the Linux
> > client) to do 9739909 in exactly .200 sec/iter. Now the
best I can get is
> > .223 sec/iter. Maybe I have a similar problem. Killing
proccesses
> > doesn't seem to help.
>
> Did you change the CPU speed in Options/CPU? The iteration
timing in
> mprime (and Prime95) is calculated from the number of CPU
cycles
> multiplied by the cycle time derived from the CPU speed
entered here.
> If you change the processor speed physically then the
program doesn't
> know... If the iteration timing _in CPU cycles_ changes
without you
> changing the CPU speed, then maybe the memory detection at
boot time
> is inserting extra wait states - because you lost the
NVRAM config,
> or because the memory chips (or chipset) won't take the
faster bus
> without the extra waits.
>
> Regards
> Brian Beesley
Well, my CPU speed is correctly flagged in Options/CPU as
601 and always has
been. I overclocked a long time ago. I don't know about
extra wait states at
boot time or NVRAM config. Is there a way to check this?
Matthew Smith
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
