Hi gencha,

That option is actually designed to do exactly that. Stop work when you stop using the computer, for those who like their computer to go to sleep automatically it will do so.

Reversing that change is correct and then untick the "While computer is in use", and set the delay you want the computer to resume computing after you stop using mouse/keyboard/joystick. Of course, your computer needs to connect to the server to learn of the new setting.

I'd advise against 0.1 minutes. That's 6 seconds. You might experience delays as it takes BOINC time to resume... fetch the tasks from disk. With this option also recommend to select "Leave application in memory when suspended". This way the tasks resume lossless [requires your computer to have about 0.5GB RAM per job, so a duo core needs to have 1GB]. If do don't select that option the tasks jump back to the last saved checkpoint and with 6 seconds resume you would be hitting the maximum number of restarts very quickly [100]. After 100 BOINC thinks that a task is broken. Best time is somewhere in the 3-5 minute range. If you experience delay in computer response, increase the value.

Let us know

--//--

errata: Many just let BOINC run while in use. There's an option to tell BOINC to stop if you need more than an X percent of the CPU time. Recommended [WCG] setting is 50%. I've got it after lots of testing on my Linux box on 40% [else the heavy CEP2 break if I use more]. The field to set and select is "While processor usage is less then XX %"

maybe try, within Boinc manager in the advanced view- click the advanced tab, preferences, and clear, then reconnect and reread settings from the server?

"Update" did the trick. Now I'm running again. Thanks for your help :)

There's been several mentions recently of the "Do network communication". That's not telling a client to initiate any specific project connection. The wiki says "Force a retry of any project deferred communications.", but frankly I've never noticed doing anything and have never thought of it as anything but establishing that it can communicate. If one looks in the message log, it's not recording any action. Maybe Ingleside knows which log flag would force a recording of that user action, so there is feedback.

Five minutes later...

Ah, lights came on testing with a project that has a 6 minute deferral after a manual update: With "Do network communication", the deferrals of all projects get canceled and normal scheduling cycle resumes... the counters clear. That's something, but not a particular push to fetch work ... removes networking delays when a project was down or the ISP was not cooperative, more so the project I tested on went back to sleep as it is set the "No work fetch".

--//--