On Tuesday 05 November 2002 21:40, George Woltman wrote:
>
> I'd actually recommend not doing the P-1 again.  If you are using enough
> memory to run both P-1 stages, then the bug did not affect stage 1 but did
> affect stage 2.
>
> If you run only stage 1 of P-1, then the bug would cause no factors to be
> found.
> In this case, you might consider re-running P-1 again as Brian suggests
> (but only if you used 22.10 dated after Sept 28).
>
> >  I did this on my own system & have been rewarded with _two_ factors
> > found -
>
> This is way above expectations!   Nevertheless, I'm always happy to get the
> factors.

Sure, I was surprised too. Anyway this is what I got:

{system 1}
[Wed Oct 30 21:00:54 2002]
UID: beejaybee/slug1, M8589491 completed P-1, B1=40000, B2=420000, WY2: 
DE3C48D7
...
[Tue Nov  5 10:15:49 2002]
P-1 found a factor in stage #1, B1=40000.
UID: beejaybee/slug1, M8589491 has a factor: 42333443925749970809

{system 2}
[Thu Oct 31 23:12:50 2002]
UID: beejaybee/caterpillar, M8564431 completed P-1, B1=45000, B2=618750, WY2: 
DDB16BFB
[...]
[Tue Nov  5 12:44:02 2002]
P-1 found a factor in stage #2, B1=45000, B2=618750.
UID: beejaybee/caterpillar, M8564431 has a factor: 9592239270614293063

There's no particular reason to suspect that a glitch on either system caused 
a factor to be missed on the first run. I did have a couple of problems with 
cabbage in the summer which turned out to be due to a UPS overload, but 
that's fixed now.

Regards
Brian Beesley
_________________________________________________________________________
Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

Reply via email to