>Iteration: 164000 / 8410531 [1%]. Clocks: 115665753 = 0.496 sec.
>
>Might be nice to display the percentage out to an accuracy that changes
>every hundred iterations. Hmm, looks like that's an integer of the
>percentage, not rounded. Guess it doesn't matter. For the one I'm
>working on it looks like 3 decimal places would be needed to see a >change
every 100 iterations.
v19 allows this by manually adding 'PercentPrecision=' to the
PRIME.INI file (Prime95 must be stopped and exited before
editing, and then restarted). The valid range after the '='
is 0 to 6, therefore you can have it say:
Iteration: 164000/8410531 [1.949936%]. Per iteration time: 0.496...
Iteration: 164100/8410531 [1.951125%]. Per iteration time: 0.496...
Mind you, even at the limit of v19 (79.3M), setting it to a
value of 4, and having screen outputs at every 100 iterations,
will still cause the value to increase (although by 0.0001%)
Eric Hahn
P.S. At the 79.3M range, you'll probably not want to set it
at 100 iterations... Per iteration time on 266MHz PII with
64MB RAM is 58.781 seconds!!! (Yes, it's true, but I'm also
just checking to see if anybody's awake :))
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
