> think there are enough Linux users out there
> to justify it.
here's mine:
xterm -display localhost:0.0 -name mprime -e tail -f results.txt &
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Aaron Blosser wrote:
> [the prime95 icon is ] mostly RED which would have been a good
> "alert" color. Maybe slowly flashing YELLOW or something, or make is
> usually GREEN then YELLOW for messages and RED for big problems.
Is there an "official international math color?"
__
Why factors prime95 only up to 59 bit at exponnent which are for
doublechecking?
The other (9million) are up to 62 bit.
Why is that so?
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
On Sat, 10 Apr 1999 08:41:16 -0600, Aaron Blosser wrote:
>Also, do you plan to optimize the assembly code in any way for the new types
>of CPU's out? AMD's K6-3, Pentium III, etc. It would certainly "seem" that
>some slight tweaking could be done to squeeze out a few extra percent of
>improvemen
Call for Participants
-
After M601 the next smallest Mersenne number is M617, which is on
the 'More Wanted' list of the Cunningham project. I am organizing a
distributed NFS effort to factor M617. Some binaries are available for
x86, alpha, and sparc solaris at ftp://ft
C(2,601-) Factored
--
M601 has been completely factored by the Special Number
Field Sieve (SNFS). It was previously known that
M601 = 3607 * 64863527 * c170
The factor 3607 was found by Riesel in 1957 and the factor
64863527 was found by Brillhart and Johnson in 1960.
> >It also seems that the number of sumout errors [that is, sum(inputs) !=
> >sum(outputs) ]
> >on my AMD K6-2 400 has dropped to zero in the past few days [I think] from
> >about
> >1 every 2 to 3 hours late last week.
> My bet would be overheating or flaky memory - but I certainly
> cannot prov
