The next update of the DOS-script is available (see first post).

New/Changes:
- Some *.lua-files and code-lines deleted: not needed anymore (no changes on server-side!)
- Cancelling pairs is slightly different
- Some additional scripts for invoking server/client for personal run or changing WUCacheSize in many subfolders
- Supporting cLLR V3.8.1

[b]Important:[/b]
[strike]
V0.73 will not work with cLLR-version 3.8.0 and lower
and
V0.72 will not work with cLLR V3.8.1!
[/strike]

Sorry! Not correct!
Should read only:
V0.72 will not work with cLLR V3.8.1!

Trying to catch up...
 

Great!

Another question.
The old LLRnet had a file "llr-guiconfig.txt" and it was necessary to set the line "["port"]=xxxx" to a different value for each folder/core. Is there an equivelent setting that has to be changed in this package?

[B]edit re. kar_bon's answer below[/B]

4 cores running on port 3000 :smile:

[QUOTE=Flatlander;217306]The old LLRnet had a file "llr-guiconfig.txt" and it was necessary to set the line "["port"]=xxxx" to a different value for each folder/core. Is there an equivelent setting that has to be changed in this package?[/QUOTE]

No. Because LLRnet only submit results to the server and get new pairs, there's no need for any GUI-support.
As mentioned in the ReadMe.txt the files 'gui.lua', 'gui.bat' and 'llr-guiconfig.txt' not needed any more!

[quote=Flatlander;217306]Great!

Another question.
The old LLRnet had a file "llr-guiconfig.txt" and it was necessary to set the line "["port"]=xxxx" to a different value for each folder/core. Is there an equivelent setting that has to be changed in this package?

[B]edit re. kar_bon's answer below[/B]

4 cores running on port 3000 :smile:[/quote]

And you already have an n>800K prime on port 3000! How'd you pull that off? :-) I think Vaughan has had at least 2 quads on there for several weeks and hasn't found one in a long time. (sorry Vaughan) Regardless, congrats on a nice prime!

It's nice to see you back. :smile:

[QUOTE=gd_barnes;217339]And you already have an n>800K prime on port 3000! How'd you pull that off? :-) I think Vaughan has had at least 2 quads on there for several weeks and hasn't found one in a long time. (sorry Vaughan) Regardless, congrats on a nice prime!

It's nice to see you back. :smile:[/QUOTE]

This was the 75th pair tested by Chris on this drive!

My prime on the 6k-Minidrive for n=1M-2M was the 97th pair!

Congrats.

[QUOTE=gd_barnes;217339]... I think Vaughan has had at least 2 quads on there for several weeks and hasn't found one in a long time. (sorry Vaughan) Regardless, congrats on a nice prime!

It's nice to see you back. :smile:[/QUOTE]
Yes that was right. They have been confiscated from me by my son and he's crunching Folding@Home on them until I can get my hands on 'em again :max:

[quote=vaughan;217431]Yes that was right. They have been confiscated from me by my son and he's crunching Folding@Home on them until I can get my hands on 'em again :max:[/quote]
Couldn't you have at least convinced him to wait until after the rally? :cry: Perfect timing, that... :wink:

As reading in the Sierpinski/Riesel Base 5 thread there seems problems with V0.73 like stopping testing with the script.

PLEASE!

I cannot improve that script if I got no special problem descriptions and test-cases to reproduce such issues!

Post your problems here! But reports like "The script stopped working!" is nothing to find and solve any errors!

Information like operating system, version of Win/Unix, number of clients, overclocked would help, too!

Problems, but caused by my actions.
 

I have been having problems. Initially I thought the software was buggy but having reconsidered my steps I think this is all my fault.

I had 4 clients in 4 folders.

Symptoms:
After running for a while with a WUCacheSize = 10, I exited all 4 clients with ctrl-c to change it to WUCacheSize = 2.

iirc for one or two clients I chose to 'stop' the script at the question instead of 'continue'. My bad. :sad:
I think this confused the software. Two of the clients have been testing k*2^808/809xxx-1 repeatedly while the other two clients moved on to k*2^815/816xxx-1 some hours ago. Also, when stopping the clients later, one of the clients did not offer the stop/continue choice but just stopped. After a reboot (iirc) [edit: no, I didn't], I left the 4 clients running overnight.

I just stopped the clients this morning. One of the clients said 'Caught signal terminating. A duplicate file name exists, or the file cannot be found. Resuming LLR test of ...' Another ctr-c was successful.

I have now started again with 4 new folders and everything appears fine.
Here is a link to the original 4 folders in case you do see something else. (Copies of some files were made by me so I could examine their contents without interrupting the clients.)
[URL="http://www.sendspace.com/file/t8ezrf"]http://www.sendspace.com/file/t8ezrf[/URL]

(Windows XP, SP 3. Q6700 at stock speed, 2.66GHz.)

[B]edit:[/B]
Just remembered. I had also set "set op_Iterations=1000" for a while then reverted back to "set op_Iterations=10000". But one of the clients refused to revert back to 10000.

The only issue I can see is for client 4: the script tested the same 10 several times!

To change an option, stop the script (CTRL-C) and say 'Y' to the question to stop the batch.

Edit the option in the do.bat (texteditor) and start again by calling 'do' again.

The option is set at the beginning, so CTRL-C, editing the do.bat and answering 'N' to stop batch won't work. More: it will not correctly anymore!

- I've set WUChacheSize to 5 and op_Iterations=10000 and run do.bat
- stopped the script
- edited in 'do.bat' op_Iterations to 15000
- edited in 'llr-clientconfig.txt' WUCacheSize to 2
- calling 'do.bat' again
-> llr displays 15000 iterations immediatly and after finishing the remaining of the 5 pairs, llrnet reserves 2 pairs only

So> stop the script and start again and all is fine!

PS: Stopping the script with CTRL-C during LLR is testing a pair, will cause problems if you answer to continue the script! cLLR was terminated, too but the script will go on the next steps, so the workfile.txt is renamed in workfile.bak and an error like file not found will occur!

[quote=kar_bon;217563]PS: Stopping the script with CTRL-C during LLR is testing a pair, will cause problems if you answer to continue the script! cLLR was terminated, too but the script will go on the next steps, so the workfile.txt is renamed in workfile.bak and an error like file not found will occur![/quote]
To summarize: when stopping the latest (v0.73) script, do you always have to answer "N" to the "Terminate batch job? (Y/N)" prompt? And is this new in v0.73? (Because I believe I answered "Y" a few times to earlier versions with no apparent ill effects.)