[QUOTE=Uncwilly;560332]Are you sure that you did not just get a Cert assignment? That should not last more than an hour or 3, depending on your machine.[/QUOTE]

This bug repeated itself on a different computer. I downloaded v30.3b6 on a separate computer, directly from Mersenne.org (not from a flash drive). when I restarted P95, it gave me a new PRP assignment.

[code]PRP=XXX,1,2,332316437,-1,79,2[/code]

Any progress in making version 30.* build * available for Mac OSX yet?

[QUOTE=bayanne;561546]Any progress in making version 30.* build * available for Mac OSX yet?[/QUOTE]

There was a link to a command line version that some have reported worked OK. Try [url]https://www.dropbox.com/s/xo7psmmjfkb52pr/p95v303b6.MacOSX.tar.gz?dl=0[/url]

Since v30.3 my computer bank is completing only 75% of the PRPs that it did in v29.6. They spend a large amount of time doing other peoples CERT work. Is there a setting to ask the server for just PRP and skip all these CERTs for other peoples PRPs?

[QUOTE=simon389;561706]Is there a setting to ask the server for just PRP and skip all these CERTs for other peoples PRPs?[/QUOTE][c]Test | Worker Windows...[/c] uncheck: [c]Get occasional proof certification work[/c]

Alternately, set [c]CertWork=0[/c] in [i]local.txt[/i]

You can also see under [c]Options | Resource Limits... | Advanced...[/c] the setting [c]Certification work limit (% of CPU time)[/c] if you want to do some Cert work but less than you're currently getting. With default settings your CPU shouldn't spend more than 10% of it's time doing Cert.

Advanced Resource Limits & Settings Dialog
 

Please consider the attached image. This seems to be a Windows 7 Pro issue [U]only[/U]. Clicking the "OK" button in the upper right corner produces the inset message. Clicking "OK" on this message highlights the value in the dialog beneath in blue. I have this shaded in bright yellow. The only way out is to click "Cancel" on the larger dialog. I have learned where most of the setting involved are in [I]prime.txt[/I] and [I]local.txt[/I], so I adjust them manually.

[QUOTE=storm5510;561843]Please consider the attached image. This seems to be a Windows 7 Pro issue [U]only[/U]. Clicking the "OK" button in the upper right corner produces the inset message. Clicking "OK" on this message highlights the value in the dialog beneath in blue. I have this shaded in bright yellow. The only way out is to click "Cancel" on the larger dialog. I have learned where most of the setting involved are in [I]prime.txt[/I] and [I]local.txt[/I], so I adjust them manually.[/QUOTE]

I have the issue on Windows 10, too. It seems to be caused by the program limiting the size of the "Emergency memory" to at most quarter of the total RAM available but has some rounding issues (or issues when getting the size of installed RAM) so it won't allow exactly 2 GB when having 8GB total, but only 1.99951 GB. Or in my case, 7.97949 GB out of 32 GB, instead of 8GB.

I'll bet $1.99 that if you typed 1.99 over that 2 that the program would take it.

[QUOTE=PhilF;561846]I'll bet $1.99 that if you typed 1.99 over that 2 that the program would take it.[/QUOTE]

I have tested it, you're absolutely right. If you put in a number which is in the range required by the error message, it will accept it, but it will round it to one decimal place.

In my case, 8 is bad, as well as 7.9999, 7.999, 7.99. 7.98 is still bad, but 7.97 is good, and it gets rounded to 8 when I apply the setting and open it again. 7.95 gets rounded to 7.9.

I'll also round the maximums to the nearest tenth.

Windows 10 did not give me any problems. I just checked. It is set to 1. I have never tried any fractional values, like 1.5. In this case, I would have gone into [I]local.txt[/I] and set the value to 1536. For some reason, I always use powers of 2 for things of this type, although I do not know why. Regardless, I am pleased a few here paid some attention to this. :smile: