original run. There were five SUM(INPUTS) != SUM(OUTPUTS) error during
the run. Historically, five errors during a run means there is less than a 50%
chance the final LL result will be correct.
Now I have to try and figure out what safety checks can be added to prevent false alarms.
So far, I have 2 changes planned:
1) Prime95 does not tell the server how many errors occurred for an LL test
with a prime result. I'll fix this. Knowing their were 5 errors would have raised
red flags earlier on.
2) I'll change prime95 to NOT delete the save files when a new prime is found.
When a prime is reported, I'll ask for the save file and rerun the last 30 minutes
of the test. I think this would have helped in this case. This measure also
deters a hacker. It might be easy for a hacker to spoof a prime report - but
he'll have difficulty generating a save file that reports the number as prime after
the final 30 minutes of LL testing.
There is still a chance this really is prime, we'll know on Friday.
_________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
