Mersenne Digest      Saturday, September 11 1999      Volume 01 : Number 624




----------------------------------------------------------------------

Date: Thu, 09 Sep 1999 19:57:49 -0400
From: George Woltman <[EMAIL PROTECTED]>
Subject: Mersenne: Prime95 version 19 - better late than never

Hi all,

Sorry for the delay in releasing v19.  It is now available for
mersenne mailing list members to beta test.  If all goes well,
it will be officially released to all GIMPSers in a few weeks.

You can get the new version at ftp://entropia.com/gimps/p95b.zip
To upgrade prime95, stop and exit the current version.  Optionally
make a backup of the directory containing prime95.  Unzip the
new version on top of the old version.  Start the new prime95.

Next time you contact the server, it will broadcast a welcome message
to you.  Let me know if there are any problems with this new feature.
The message will be deleted prior to the final release of v19.  This
feature gives us an effective way to inform you of new versions and
important bugs or news.

Save files are upward compatible from previous versions, but not 
backward compatible.  Thus, do not try this beta if you are in a dual-boot
environment.  The Linux and NT service versions will be available soon.

I'd like to thank the excellent work of the QA team.  They located
many bugs, bringing you a higher quality beta.  The QA team included
Ken Kriesel, Brian Beesley, Tom Cage, Jean-Yves Canart, Bryan Fullerton,
Marc Getty, Steinar H. Gunderson, Eric Hahn, Alex Healy, Paul Landon,
Greg McIntyre, Lawrence Murray, Paul Victor Novarese, Ethan M. O'Connor,
Rick Pali, Shane Sanford, Brian Schroeder, Gordon Spence, Joth Tupper,
Guillermo Ballester Valor, David Willmore, and Lucas Wiman.

And, of course, thanks to Scott Kurowski for his v19 enhancements to
the Primenet server.

Here is the relevant excerpt from whatsnew.txt:

1)  Faster - in some cases as much as 10% faster!.  The FFTs were recoded
    for improved memory and TLB efficiency.  Furthermore, optimizations
    specific to the Pentium Pro and later processors were added.
2)  New FFT lengths.  The program can now test exponents as large as
    79.3 million.  Also, smaller FFT lengths are supported for use in
    ECM and P-1 factoring.
3)  More conservative FFT breakpoints.  This could actually result in
    some exponents being slower to test in this version.  However, the
    chance of a fatal rounding error has been reduced.
4)  P-1 factoring has been added.  Although it is not very practical for
    large exponents because of a slow GCD routine, it can be used to
    find new factors of exponents below a few million or so.
5)  ECM can now run on large exponents.  Once again, the slow GCD routine
    and high memory requirements might make this impractical for large
    exponents.
6)  ECM and P-1 factoring now support save files.  Very handy on lengthy runs.
7)  ECM and P-1 factoring lets you specify the amount of memory to use.
    In some cases, more memory can improve execution speed slightly.
8)  A bug in guessing the CPU speed on initial install has been fixed.
9)  The preferences dialog now has an option to pause prime95 when a laptop
    is running on its battery.
10) Error checking has been improved slightly.
11) Factoring is now "layered".  That is, prime95 now factors to 2^52, then
    2^53, 2^54, and so forth up to the appropriate limit.  The factoring
    output lines have been changed to show percent complete in the current
    "layer".
12) A bug in running two or more self or torture tests in the same directory
    has been fixed.
13) Trial factoring above 2^64 is now supported.
14) More trial factoring is now done to take into account the cost of
    double-checking.
15) Title now contains percent complete when LL testing.  By default, the
    percent complete value is now displayed to 2 decimal places.  You can
    change this by setting PercentPrecision in prime.ini to a value
    between 0 and 6.
16) Affinity and service name settings moved from prime.ini to local.ini file.
    Prime95 will automatically move these settings for you.
17) An option to get only 10,000,000 digit numbers to run primality tests
    on has been added to the Test/Primenet dialog box.  See
    http://www.mersenne.org/prize.htm for rules on claiming the EFF award
    for finding a 10,000,000 digit prime.
18) The Advanced/Clear primes menu choice has been deleted.
19) The prime95 icon turns yellow when the program is idle.  After an
    error such as ILLEGAL SUMOUT, the icon will blink for 10 seconds.
20) The User Information dialog box allows you to request newsletters and
    form a team user ID where the team members cannot alter the team name.
21) A bug in the reporting of error counts in the results.txt file has
    been fixed.
22) The server can now broadcast important messages to the prime95 client.
    Prime95 will blink the icon until prime95 is activated and then it will
    display the message.

Finally, here is the timings table from my PII-400:

        V18 timing      V19 timing      old P-90 timings
        ----------      ----------      ----------------
80K     0.038           0.036
96K     0.047           0.0445          0.272
112K    0.058           0.0548          0.332
128K    0.0645          0.0604          0.371
160K    0.086           0.083           0.481
192K    0.104           0.0982          0.589
224K    0.1266          0.1193          0.699
256K    0.141           0.1316          0.778
320K    0.190           0.1726          1.024
384K    0.2292          0.2107          1.244
448K    0.278           0.2520          1.498
512K    0.3102          0.2808          1.680
640K    0.409           0.372           2.470
768K    0.4963          0.453           3.074
896K    0.5985          0.536           3.796
1024K   0.670           0.600           4.202


Please report any problems to me.

Enjoy,
George

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Thu, 9 Sep 1999 21:43:54 -0400 (EDT)
From: Lucas Wiman  <[EMAIL PROTECTED]>
Subject: Mersenne:  Factors of DecMega

Scott/all,

I downloaded the newest beta for Prime95V19, and set it to ask for 10,000,000
digit Mersennes.  In my worktodo.ini file, I got the line:
Test=33219379,32

This surprised me!  I had tested this number to 2^47, and Alex Kruppa had
tested it to at least 2^55 (further investigation revealed 2^60).  You should
update primenet's files pertaining to this off of those at
http://www.informatik.tu-muenchen.de/~kruppa/M33M/index.html

- -Lucas Wiman

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Thu, 09 Sep 1999 22:37:08 -0400
From: George Woltman <[EMAIL PROTECTED]>
Subject: Mersenne: Re: Factoring in version 19

Hi,

At 09:43 PM 9/9/99 -0400, Matthew Smith wrote:
>I love the new beta.  It's much faster and accomodates my PIII.  But why is
>it factoring my most recently assigned number, and not the one I was working
>on before I upgraded?

That's normal.  The new version does more factoring than the old version.
It is factoring the second number so that if it does have a factor it
can get you a new exponent to test and keep your "days of work queued up"
greater than 10.

Regards,
George

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Thu, 09 Sep 1999 22:44:18 -0400
From: George Woltman <[EMAIL PROTECTED]>
Subject: Mersenne: Test/Status in version 19

Hi all,

One more thing.  The timings in prime95 have been recalibrated to my
PII-400 instead of my old, deceased P-90.

What does that mean?  The short explanation is that you should not
believe the estimates given in Test/Status.  Over time these estimates
will become accurate again.

Why is this?  When version 18 estimated my PII-400's speed it underestimated
by 40%.  Over time, the RollingAverage value in local.ini grew to 1400
to compensate for the poor guess and give accurate estimates in Test/Status.
Well in version 19, prime95 accurately guesses my PII-400's speed and
applying the rolling average of 1400 makes it bring in the expected completion
dates by 40%.  It won't take too long for the rolling average to come
down to close to 1000 -- or you can edit your local.ini file my hand and
set the RollingAverage to 1000.

I hope that wasn't too confusing...

Regards,
George

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Fri, 10 Sep 1999 01:14:22 -0500
From: Ken Kriesel <[EMAIL PROTECTED]>
Subject: Re: Mersenne: Prime95 version 19 - better late than never

At 07:57 PM 1999/09/09 -0400, George Woltman <[EMAIL PROTECTED]> wrote:
>Hi all,
...
>I'd like to thank the excellent work of the QA team.  They located
>many bugs, bringing you a higher quality beta.  The QA team included
>Ken Kriesel, Brian Beesley, Tom Cage, Jean-Yves Canart, Bryan Fullerton,
>Marc Getty, Steinar H. Gunderson, Eric Hahn, Alex Healy, Paul Landon,
>Greg McIntyre, Lawrence Murray, Paul Victor Novarese, Ethan M. O'Connor,
>Rick Pali, Shane Sanford, Brian Schroeder, Gordon Spence, Joth Tupper,
>Guillermo Ballester Valor, David Willmore, and Lucas Wiman.

I count 24 bugs found (excluding items I'd categorize as wishlist items, 
misunderstandings about the expected behavior or the program, and those
errors that were not reproducible).

Omitted from the above list of QA team members was Arthur M. Coucouvitis.

To all the QA team members:
Thanks for all the time and thought contributed.
The task is large, with numerous new features, and 67 FFT lengths by my count.
I plan to continue the qa process after v19 moves from prerelease status
through beta to general release, until every FFT length has at least one
successfully double-checked exponent, or a later prime95 version is released.
I hope you will continue with us.



Ken

Ken Kriesel, PE <[EMAIL PROTECTED]>
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Fri, 10 Sep 1999 10:18:12 +0100
From: Michael Oates <[EMAIL PROTECTED]>
Subject: Mersenne: Big problem with Prime95 version 19

George,

Typical the only machine I did NOT backup the files on and it goes nuts on me...

Running on a Pentium Pro 200
My user id is MOates

I started up the new version, it connected to the server and started to get new 
numbers to
factor it stopped at 14 more numbers before I could stop it, by that time it had 
stopped
getting new numbers to factor on it's own. I now have about 2 years of numbers to LL 
test
!!! It was not ready to get any more numbers, I already had enough work for over 1 
month
(DaysOfWork=14 in prim.ini)

Before this happened I had a few numbers to factor and one to test and the worktodo.ini
was...

Factor=10440383,55   <- it was half way through this one
Factor=10440433,55
Factor=10440461,55
Factor=10440509,55
Factor=10440511,55
Test=7206811,62

It is now...

Factor=10440383,55
Factor=10440433,55
Factor=10440461,55
Factor=10440509,55
Factor=10440511,55
Test=7206811,62
Test=7657963,63
Test=7666349,63
Test=7672111,63
Test=7678291,63
Test=7678961,63
Test=7679383,63
Test=7679561,63
Test=7680259,63
Test=7680527,63
Test=7681369,63
Test=7681691,63
Test=7681693,63
Test=7682111,63
Test=7683017,63


Another Problem
===============

Another problem reared it's head as soon as it started to factor 7206811,62 (even 
though
it was half way through factoring 10440383,55 before)
Prime95 kept contacting the server every 10-15 secs for "Updating computer information 
on
the server"

An extract from the prime.log shows what was happening from when I first started with
v19...

Welcome to GIMPS Prime95 v19, with remote message notification. -- George & Scott
Updating user information on the server
Updating computer information on the server
Sending text message to server:
UID: MOates/Mike, UID: MOates, User: Michael Oates, [EMAIL PROTECTED]
Getting exponents from server
Sending expected completion date for M7657963: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7666349: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7672111: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7678291: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7678961: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7679383: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7679561: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7680259: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7680527: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7681369: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7681691: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7681693: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7682111: Sep 11 1999
Getting exponents from server
Sending expected completion date for M7683017: Sep 11 1999
Updating computer information on the server
Updating computer information on the server
Updating computer information on the server
Updating computer information on the server
.
.
etc

Notice how the expected completion date is the same date !

I had a look at the other .ini files to see if anything was amiss, in the local.ini 
there
is a line...
BroadcastID=1

Surly that should normally be 0, and no matter what I did - restarting Prime95 or 
editing
the value directly to 0 it still contacts the server every few seconds, in fact every 
time
it outputs a line to the window.

Help !!!

First how can I get rid of all those numbers to test I only wanted the one "7206811,62"

Any other ideas as to how I get this working again without messing up any work already
done.

Even if I had made a backup, there would still be all those numbers to sort out on the
server.


Another issue
=============

While I am here, there is still a problem (that was with v18.1) that as soon as Prime95
(or mprime on linux) tries to contact the server via proxy (WinProxy) starts to bring 
up
the connection (via dialup) but before the dialup completes Prime95 gives the error...

ERROR: Primenet error 29

The proxy dialup continues and establises a working internet connection. I can then
manually get Prime95 to contact the server. So it is using the proxy, but it's as 
though
there is not enough time allowed before the internet connection is made. (with ISDN 
this
delay is only about 2 secs) I did make a report on this a few days ago, and maybe it 
has
not yet been acted on. I was just hoping the new version would work. Note that I have 2
networks, (home & work) one uses ISDN the other modem, they both have the same problem.

Sorry for the long email, but I am sure you can't have too much info when sorting 
problems
out like this. If you want any more info just ask.

Thanks,

Mike,

- -- 
ATLAS CELESTE - Bevis Star Atlas - & "The CD-ROM"
       http://www.u-net.com/ph/mas/bevis/
Astronomy in the UK    http://www.u-net.com/ph/
_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Fri, 10 Sep 1999 15:06:08 -0400
From: George Woltman <[EMAIL PROTECTED]>
Subject: Mersenne: Re: Big problem with Prime95 version 19

Hi,

At 10:18 AM 9/10/99 +0100, Michael Oates wrote:
>Sending expected completion date for M7657963: Sep 11 1999
>Getting exponents from server
>Sending expected completion date for M7666349: Sep 11 1999

The new version is fast - but not that fast!

I've fixed a bug that occured sometimes when the first line
in the worktodo.ini file is a "Factor=" line.

To those affected, download version 19 again and see if it
doesn't return those excess exponents at some point.  Let me
know by private email if that did not fix the problem.

Hope that helps,
George

BTW, the QA group concentrated on the math code not the client
and server interaction.

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Sat, 11 Sep 1999 11:08:35 -0700
From: "John R Pierce" <[EMAIL PROTECTED]>
Subject: Mersenne: error in V19??!?

Whoops!!!

Welcome to GIMPS Prime95 v19, with remote message notification. -- George &
Scott
[Thu Sep 09 20:20:31 1999]
Factoring M6539111 to 2^63 is 13.93% complete.
....
[Fri Sep 10 04:58:58 1999]
UID: jp/p3-500, M6539111 no factor to 2^63, WV1: 3ED32B8A
[Fri Sep 10 06:21:31 1999]
Factoring M6779911 to 2^63 is 14.45% complete.
....
[Fri Sep 10 13:57:40 1999]
UID: jp/p3-500, M6779911 no factor to 2^63, WV1: 41132D24
[Fri Sep 10 15:17:10 1999]
Factoring M8329537 to 2^64 is 8.87% complete.
....
[Sat Sep 11 05:24:12 1999]
UID: jp/p3-500, M8329537 no factor to 2^64, WV1: 4FFD3775
[Sat Sep 11 08:19:02 1999]
Iteration 6700000 / 7817869
[Sat Sep 11 10:34:45 1999]
Iteration: 6742784/7817869, ERROR: ROUND OFF (0.4086303711) > 0.40
Possible hardware failure, consult the readme file.
Continuing from last save file.
[Sat Sep 11 11:04:20 1999]
Disregard last error.  Result is reproducible and thus not a hardware
problem.
Iteration: 6742912/7817869, ERROR: ROUND OFF (0.4086303711) > 0.40
Possible hardware failure, consult the readme file.
Continuing from last save file.


[worktodo.ini is...
    Test=7817869,63
    Test=7888367,63
    Test=6539111,63
    Test=6779911,63
    Test=7468187,63
    Test=8329537,64

local.ini is
    CPUType=10
    CPUSpeed=504
    SelfTest64Passed=0
    SelfTest80Passed=0
    SelfTest96Passed=0
    SelfTest112Passed=0
    SelfTest128Passed=0
    SelfTest160Passed=0
    SelfTest192Passed=0
    SelfTest224Passed=0
    SelfTest256Passed=0
    ComputerID=p3-500
    CPUHours=24
    OldRollingAverage=1386
    LastEndDatesSent=936928821
    RollingStartTime=0
    SelfTest384Passed=1
    RollingAverage=997
    BroadcastID=1



_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Sat, 11 Sep 1999 19:13:45 -0400
From: George Woltman <[EMAIL PROTECTED]>
Subject: Re: Mersenne: error in V19??!?

Hi John,

At 11:08 AM 9/11/99 -0700, John R Pierce wrote:
>Iteration: 6742784/7817869, ERROR: ROUND OFF (0.4086303711) > 0.40
>Possible hardware failure, consult the readme file.
>Continuing from last save file.
>[Sat Sep 11 11:04:20 1999]
>Disregard last error.  Result is reproducible and thus not a hardware
>problem.
>Iteration: 6742912/7817869, ERROR: ROUND OFF (0.4086303711) > 0.40
>Possible hardware failure, consult the readme file.
>Continuing from last save file.

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.

Regards,
George

_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

Date: Sat, 11 Sep 1999 16:55:27 -0700
From: "John R Pierce" <[EMAIL PROTECTED]>
Subject: Re: Mersenne: error in V19??!?

> 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

------------------------------

Date: Sun, 12 Sep 1999 00:42:14 -0500 (CDT)
From: Conrad Curry <[EMAIL PROTECTED]>
Subject: Mersenne: Mailing list archive

  By the end of next week I will remove the mailing list
archive search function.  The index for the archive occupies
1/3 of my disk quota.  Considering how little it has been
used, I can make better use of this disk space.  I hope
someone else would be willing to rebuild the index and host
it.  The mailing list messages up to Feb. 98 can be found
below (about 4.2Mb).

ftp://ftp.netdoor.com/users/acurry/archive1.zip
ftp://ftp.netdoor.com/users/acurry/archive2.zip
ftp://ftp.netdoor.com/users/acurry/archive3.zip
ftp://ftp.netdoor.com/users/acurry/archive4.zip
ftp://ftp.netdoor.com/users/acurry/archive5.zip

  I used swish http://sunsite.berkeley.edu/SWISH-E/
for the search engine.


_________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
Mersenne Prime FAQ      -- http://www.tasam.com/~lrwiman/FAQ-mers

------------------------------

End of Mersenne Digest V1 #624
******************************

Reply via email to