Error opening the results file - LLR

[em99010pepe]

Just got this:

[Sun Dec 06 21:10:17 2009 - ver 3.7.1]
Error opening the results file ; see result below :
105*2^1284570-1 is not prime. LLR Res64: 2EDD22E61A25CD4F Time : 1911.149 sec.

I tested again the number and got the same residue:

105*2^1284570-1 is not prime. LLR Res64: 2EDD22E61A25CD4F Time : 1716.470 sec.

Anyone ever got this type of error?

Carlos

[Batalov]

People will probably ask you what flavor of Windows this was, and what folder did you put the binary in... Windows is not my cup of tea.
(The system prevents writing to certain folders which it deems protected; it is different for different Windows versions. Universally, you may want to use the whole thing into your "My Documents", I think.)

[em99010pepe]

I'm running LLR in folders:
c:\dc\LLR\core0
c:\dc\LLR\core1
c:\dc\LLR\core2
c:\dc\LLR\core3

Got the error on core0 folder, the rest of the cores didn't get the error.

Carlos

[Flatlander]

I think I got that error once when I left lresults.txt open by mistake.

[VBCurtis]

flatlander has it right- windows by default prevents multiple programs from having write privledges to the same file. If you had it open in notepad, wordpad, or office, windows gives that program exclusive ability to save changes. Other programs can read it, but not save changes.

This is the same reason wordpad sometimes cannot save changes you make to a work file while LLR is running on that file.

rest assured it was not an LLR error.
-Curtis

[Mini-Geek]

Originally Posted by Flatlander

I think I got that error once when I left lresults.txt open by mistake.

I've got it before when a program (used to check for primes in the lresults.txt file) kept lresults.txt open after reading it.
Like others have said, it wasn't really an error in LLR. LLR just couldn't write to the file for one reason or another. Unless it makes a habit of it, it's probably nothing to worry about.

[em99010pepe]

Thank you Curtis.