@Max
I think you mean the other way round.
[QUOTE=kar_bon;217563]...
To change an option, stop the script (CTRL-C) and say 'Y' to the question to stop the batch.
...[/QUOTE]

[quote=Flatlander;217597]@Max
I think you mean the other way round.[/quote]
Actually, I did mean it the way I wrote earlier...I was a little confused as to whether Karsten was saying we need to use "Y" or "N" when stopping the script (comparing your quoted section with mine), hence my request for clarification.

You should always answer 'Y' to stop the batch after pressing CTRL-C!

I did it every time and I never encountered any issue when continuing the script by calling 'do' again!

[quote=kar_bon;217604]You should always answer 'Y' to stop the batch after pressing CTRL-C!

I did it every time and I never encountered any issue when continuing the script by calling 'do' again![/quote]
Oh, duh...now I get it. Chris was right, I was getting confused: since the question is phrased as "Terminate batch job? (Y/N)", answering "Y" is the same as saying "don't continue". Silly me. :rolleyes:

Thanks, that makes sense now.

Is it possible to make it pause while a laptop is on battery power, like the GUI LLR?

[QUOTE=Flatlander;217748]Is it possible to make it pause while a laptop is on battery power, like the GUI LLR?[/QUOTE]

This is only possible, if an option from DOS-based script can determined the laptop is on battery or not! Don't know if this exist.

[QUOTE=kar_bon;217749]This is only possible, if an option from DOS-based script can determined the laptop is on battery or not! Don't know if this exist.[/QUOTE]

So then it's not possible to just tell the command line version of LLR to pause when on battery like you can tell the GUI version that?

I have not yet tested/needed the option RunOnBattery=0 from the GUI-version with the command line version but will do this.

If this option works with cLLR, too, it's only possible by setting this option on top of the DOS-script like for the option "OutputIterations"!

I've been testing v.073 for a couple of weeks now and have not had a single problem. I have it set up on over 50+ cores with 1 local server being hit by 24 cores. I've tried to break the canceling logic and can't. I even survived a power outage last evening with nothing lost. This is all on Windows Vista 32 bit and 64 bit systems. I like it. Just thought I'd let everyone know it's being banged on pretty hard. Ian

Hi
I wonder if you could look at the attached and tell me if my clients are shutting down properly.
You can see that two clients generated an error (no workfile.txt) when I pressed ctrl-c. Is it safe to continue again with the same folder or will I get errors?
Image and folders:
[URL="http://www.sendspace.com/file/coak60"]http://www.sendspace.com/file/coak60[/URL]

(Just in case, I have since run 'do -c' on each folder and started with 4 new ones.)

[QUOTE=Flatlander;218017]You can see that two clients generated an error (no workfile.txt) when I pressed ctrl-c. Is it safe to continue again with the same folder or will I get errors?
[/QUOTE]

Please tell me what system you use? Overclocked?

This did not happend yet on my C2Q w/OC.

If you start the script by calling 'do' again, you will get an error!

Please rename the 'workfile.bak' back to 'workfile.txt' and you can start the batch again without errors!

The script seems go further to quick until the BREAK will stop it, so this happens:

- break while cLLR is crunching
- write time/date stamp to lresults.txt
- no prime found -> rename workfile.txt workfile.bat
- goto start
- there is a z* file so goto do_cllr
- no workfile.txt found (because renamed) -> error

Perhaps a 'waits 1' could help here after the line calling 'cllr.exe'.

Please try this.