> This is not a bug. Brian was right that v19 would ordinarily use a 448K
> FFT wheras v18 used a 384K FFT. However, v19 is finishing off your
> exponent using a 384K FFT.
>
> You now see why I was a little more conservative with the FFT crossover
> points. Your 0.4086 error is not much greater than 0.4 and not near
> the 0.5 error that would corrupt your result.
>
> I'd continue onward with your test - you probably would have gotten
> the same error in version 18.
ah. yer right. I looked back in my results.txt and found...
[Sun Sep 05 02:42:01 1999]
Iteration: 4647424/7817869, ERROR: ROUND OFF (0.4007873535) > 0.40
Possible hardware failure, consult the readme file.
Continuing from last save file.
[Sun Sep 05 03:01:47 1999]
Disregard last error. Result is reproducible and thus not a hardware
problem.
this was with v18... Must just be something funky about this particular
candidate, not one other one I've run on this system has triggered this same
error (I've been running prime95 24/7 since June on this box)
[Sat Jun 26 05:38:31 1999]
UID: jp/p3-500, M7636493 is not prime. Res64: B1B90297D4483A26. WU1:
AD93C932,1209352,00000000
[Wed Jul 14 04:06:17 1999]
UID: jp/p3-500, M7636561 is not prime. Res64: 07124E50AF70224A. WU1:
9ADED520,5521093,00000000
[Sat Jul 31 02:52:42 1999]
UID: jp/p3-500, M7636597 is not prime. Res64: D1ED8948161F652F. WU1:
C42D91B1,7404799,00000000
[Fri Aug 20 20:36:32 1999]
UID: jp/p3-500, M7539533 is not prime. Res64: 3CE1193877330039. WU1:
A4347C02,0,80000000
[Tue Aug 24 08:06:32 1999]
UID: jp/p3-500, M7666597 is not prime. Res64: DB189558BA6AD87F. WU1:
0FA06293,6759810,00000000
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
