[QUOTE=Prime95;132184]...the as-yet-unreleased v25.7[/QUOTE]I'm sure I'm not the only one who hopes you'll have some time to finish your fixes and release v25.7 soon (it has been 4+ months since the last release... :cool:)

are there any known problems about factoring or prime testing with this version

I'm not sure if it's intentional, but I noticed in the File|Status dialog, the summary at the bottom that says[quote]The chance that one of the __ exponents you are testing will yield a Mersenne prime is about 1 in ______[/quote]only seems to take into account the assignments that can be displayed in the dialog. I noticed this when I had 2 threads running, one with only a LL and a doublecheck queued up, the other with about 30 ECMs (roughly 1-2 days work) in the queue before another LL+doublecheck. The status dialog showed my chance of finding something in the 2 tests (LL+DC) from one thread, but apparently didn't know about the LL/DC tests in the other thread, because they were beyond the scope of being displayed. When I adjusted worktodo.txt to move them up to the top of the list, the status dialog showed the expected chance for 4 tests.

edit: Maybe the attached screenshots will be clearer than my prose :)
The longer one has 31 ECM tests ahead of the same DC+LL tests in thread #1.

[QUOTE=henryzz;132314]are there any known problems about factoring or prime testing with this version[/QUOTE]

There are no known problems with the math part of the code. Plenty of UI, communication, and memory allocation rough spots.

[QUOTE=James Heinrich;132373]the File|Status dialog, the summary only seems to take into account the assignments that can be displayed in the dialog.[/QUOTE]

I've coded up a fix.

./Mlucas_AMD64_Solaris -s a
 

Hello primers

I have used the program previously but I cannot find a binary for solaris.



Mlucas_AMD64_Solaris

[URL]http://www.hogranch.com/mayer/README.html[/URL]

how do I run it please?

I started with this

./Mlucas_AMD64_Solaris -s a



[code]
INFO: Using real*12 for FFT sincos and DWT weights tables inits.
Using complex FFT radices 5 8 16 16 16
100 iterations of M6400013 with FFT length 327680
Res64: 6B2DF2F4FD779CBC. AvgMaxErr = 0.000000000. Program: E2.8x
Clocks = 00:00:02.690

Clocks = 00:00:04.200

INFO: Using prefetch.
INFO: using 64-bit-double form of rounding constant
INFO: Using subroutine form of MUL_LOHI
looking for worktodo.ini file...
no worktodo.ini file found...switching to interactive mode.
Enter exponent > 10110007
Enter FFT length in K (set K = 0 for default FFT length) > 512
Enter 0 to run a full LL test, any other integer for a self-test > 1
Enter number of iterations for timing test > 100
Enter index of radix set to be used for the FFT:
(See file fft_radix.txt for a list of available choices; enter -1 to get the default) > 1
Enter 1 to enable per-iteration error checking, 0 for no error checking > 0
p is prime...proceeding with Lucas-Lehmer test...
M10110007: using FFT length 512K = 524288 8-byte floats.
this gives an average 19.283308029174805 bits per digit
INFO: Using real*12 for FFT sincos and DWT weights tables inits.
Using complex FFT radices 8 32 32 32
100 iterations of M10110007 with FFT length 524288
Res64: 24AAC84A6CD400BE. AvgMaxErr = 0.000000000. Program: E2.8x
Clocks = 00:00:04.250

INFO: Using prefetch.
INFO: using 64-bit-double form of rounding constant
INFO: Using subroutine form of MUL_LOHI
looking for worktodo.ini file...
no worktodo.ini file found...switching to interactive mode.
Enter exponent > 10110007
Enter FFT length in K (set K = 0 for default FFT length) > 512
Enter 0 to run a full LL test, any other integer for a self-test > 1
Enter number of iterations for timing test > 100
Enter index of radix set to be used for the FFT:
(See file fft_radix.txt for a list of available choices; enter -1 to get the default) > 2
Enter 1 to enable per-iteration error checking, 0 for no error checking > 0
p is prime...proceeding with Lucas-Lehmer test...
M10110007: using FFT length 512K = 524288 8-byte floats.
this gives an average 19.283308029174805 bits per digit
INFO: Using real*12 for FFT sincos and DWT weights tables inits.
Using complex FFT radices 16 16 32 32
100 iterations of M10110007 with FFT length 524288
Res64: 24AAC84A6CD400BE. AvgMaxErr = 0.000000000. Program: E2.8x
Clocks = 00:00:03.999

INFO: Using prefetch.
INFO: using 64-bit-double form of rounding constant
INFO: Using subroutine form of MUL_LOHI
looking for worktodo.ini file...
no worktodo.ini file found...switching to interactive mode.
Enter exponent > 10110007
Enter FFT length in K (set K = 0 for default FFT length) > 512
Enter 0 to run a full LL test, any other integer for a self-test > 1
Enter number of iterations for timing test > 100
Enter index of radix set to be used for the FFT:
(See file fft_radix.txt for a list of available choices; enter -1 to get the default) > 3
Enter 1 to enable per-iteration error checking, 0 for no error checking > 0
p is prime...proceeding with Lucas-Lehmer test...
M10110007: using FFT length 512K = 524288 8-byte floats.
this gives an average 19.283308029174805 bits per digit
INFO: Using real*12 for FFT sincos and DWT weights tables inits.
Using complex FFT radices 16 32 32 16
[/code]
If I remember correctly I used a prime95 program which had an option for over clockers
CPU Torture test.


1) Where is the code for it?
2) how can I port it to solaris AMD64 and OpenBSD amd64 ?

Please?

If you just need to do a torture test you can use the Solaris 9 32-bit Intel executable that I posted in the earlier thread: [URL="http://mersenneforum.org/showthread.php?t=9852"]http://mersenneforum.org/showthread.php?t=9852[/URL].

Server database full or broken
 

I keep getting this error again, but only with one particular result. The error blocks all other communication, leaving several other results unreported, and the client is out of work. The problematic result is from an ECM line added manually via worktodo.add.

[code]
PrimeNet error 13: Server database full or broken
Insert ECM data failed, ECM M2267, B1: 44000000, B2: 4400000000, CR: 50
[Wed Apr 30 12:30:51 2008 - ver 25.6]
Sending result to server: UID: S00113/v17.1, M2267 completed 50 ECM curves, B1=44000000, B2=4400000000, Wd1: 08F80F1C, AID: 147A88E1E897F3C46B2C08FEF2966A22

URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=ar&g=517c44d24e06c2ea60d8895f92dd368f&k=147A88E1E897F3C46B2C08FEF2966A22&m=UID:+S00113/v17.1,+M2267+completed+50+ECM+curves,+B1=44000000,+B2=4400000000,+Wd1:+08F80F1C,+AID:+147A88E1E897F3C46B2C08FEF2966A22%0A&r=6&d=1&A=1&b=2&n=2267&c=-1&CR=50&B1=44000000&B2=4400000000&fftlen=112&ss=41&sh=69978EB4324D3D02283D62265B67B320
RESPONSE:
pnErrorResult=13
pnErrorDetail=Insert ECM data failed, ECM M2267, B1: 44000000, B2: 4400000000, CR: 50
==END==

PrimeNet error 13: Server database full or broken
Insert ECM data failed, ECM M2267, B1: 44000000, B2: 4400000000, CR: 50
[/code]The client needs to get better at recovering from communication problems. I've also seen the CPU identity mismatch error, which also result in the client running out of work.

Error 13 is a "can't happen" error. There are only three possibilites: The database is full (an insert row operation failed) or broken (an update or delete inexplicably failed) or there is a bug in my server code. In the first two cases the client really should try again until the some disk space is freed or the database is rebooted.

In your particular case, it was a bug in my code. It turns out 50 * 44000000 exceeds integer bounds. I added a cast to float and you should be up and running.

A couple of questions about doing P-1 factoring.

If I put this line in my worktodo.txt:

Pminus1=1,227,10069,1,100000,"3698555874044"

v25.6 immediately finds the factor:

[Sun May 04 01:55:20 2008]
P-1 found a factor in stage #1, B1=100000.
227^10069+1 has a factor: 3698555874044

This number has many known factors:
2^2 * 3 * 19 * 120829 * 402761 * 155625706960503133

What's the right way to tell Prime95 about them? Putting them inside one set of quotes separated by commas doesn't seem to work and if I try this:

Pminus1=1,227,10069,1,100000,"2","2","3","19","120829","402761","155625706960503133"

Prime95 crashes immediately.

Also, if I have my memory allowance set too low (at the default), the window is spammed with something like "Insufficient Memory, Memory set to 32MB", making the computer unresponsive for a few minutes. Let me know if you want the exact error message, I can try to do it again. The number this occurred on was 509^150697 - 1, I didn't test it again for the smaller number. This was all using the Windows 64-bit version.

Thanks.

[QUOTE=jbristow;132717]
Pminus1=1,227,10069,1,100000,"2","2","3","19","120829","402761","155625706960503133"
[/QUOTE]

Try Pminus1=1,227,10069,1,100000,10000000,"2,2,3,19,120829,402761,155625706960503133"

According to next post it should also work with ",10000000" removed.