[QUOTE=heliosh;487427]How can I manually do a PRP-CF?[/QUOTE]

I do this, but it's a bit tricky and you have to know what you're doing.

You can create worktodo lines in the appropriate format, filling in the appropriate known-factor strings, and daily monitoring new factor discoveries in order to do any necessary updates.

If you are doing double-checks, you have to tailor it further to make sure you're matching the residue type of the previous result (Type 1 or Type 5).

It's tedious to fill in the lists of factors by hand, it's best to automate that part.

Is there a particular exponent or range of exponents that you wanted to do?

[QUOTE=GP2;487433]
Is there a particular exponent or range of exponents that you wanted to do?[/QUOTE]
Just the exponents for which I found a factor. (For example M8929 right now)

It is assigned to Oliver Kruse automatically, but since it needs 2 tests, you can run this line in worktodo for a type 5 test:
PRP=N/A,1,2,8929,-1,99,0,3,5,"196439,2555359872029449,1115430961341245177793296572392840751"

Ok, thanks.

[QUOTE=heliosh;487435]Just the exponents for which I found a factor. (For example M8929 right now)[/QUOTE]

If it's a small exponent like that, then mprime itself will do an instant PRP test and output " is a probable prime!" if applicable, in the results.txt file.

This works at least up to the low 20K range. Unfortunately, that instant PRP test result isn't sent to Primenet.

An alternative is to go to [url]http://factordb.com[/url], enter "M8929" into the search box, then enter your new factor into the "Report factors" box, then click on the red link to the new cofactor. Usually factordb will do a quick automatic PRP test for such small cofactors.

Hello everyone!


Could there be a bug in the 64-bit linux build?


I've got errors of this form:


[QUOTE]
FATAL ERROR: Rounding was 0.4846425222, expected less than 0.4
Hardware failure detected, consult stress.txt file.

[/QUOTE]


The checksum of the download is correct.


Where can I find core dumps?

[QUOTE=soeglii;488444]Hardware failure detected, consult stress.txt file.[/QUOTE]Is your system overclocked? Or otherwise overheating?

This version comes with time between network retries set at 70 minutes. I sometimes unplug the network cable, mprime retries every 2 minutes to contact the server. I've set the network retries at 60 and at 120 minutes. It stores and reports those values but still retries every 2 minutes.

Can someone reproduce this with mprime current version?

[QUOTE=tha;489806]This version comes with time between network retries set at 70 minutes. I sometimes unplug the network cable, mprime retries every 2 minutes to contact the server. I've set the network retries at 60 and at 120 minutes. It stores and reports those values but still retries every 2 minutes.

Can someone reproduce this with mprime current version?[/QUOTE]

Yes. It would seem that if network itself is not connected (LAN disconnected / wireless off), it would try every 2 minutes. The retry value is only considered if network connection is there, but site is not reachable (bad internet connection, site down, etc.).

I don't think this behavior is consistent with Windows version.

[QUOTE=soeglii;488444]I've got errors of this....[/QUOTE]You should use PRP-test with Gerbicz error check option instead of LL tests for finding primes, if this error occurs and your Residue at double checks often didn't match. Most errors should be eliminated by PRP testing.



[URL]https://www.mersenne.org/download/whatsnew_294b7.txt[/URL]

p95 not counting PRP exponents toward odds of finding a prime
 

In Prime95 V29.4b8 Win64, I have two systems with multiple workers, which are running a mix of PRP and LL first time test or DC. Both systems seem to be only counting LL tests, not PRP, toward the odds of finding a prime in the listing produced by (Test, Status). Systems running only LL appear normal. A system running only PRP (Prime95 V29.4b7 Win32, or V29.4b8 Win64) does not report any odds of finding a prime.

I had thought that Prime95 would report the combined odds of all PRP and LL tests in the worktodo file finding a prime.

Is this a known issue, or intended behavior?