I have a problem with a system that it goes suspended after 10 minutes. I'm running BOINC 5.10.30 on a AMD X2 Windows XP system. I have the settings set to always run. It goes active once I start to more the mouse and use the system.

One difference with this system is I use it as a server so there's not real keyboard or mouse. I remote desktop into it. I don't logout of the session.

Anyone have this problem before or is this a known problem. I used an older version of BOINC, and I didn't have this problem.

I have the settings set to always run.

This one has me confused a bit. Do you mean you have BOINC set to Always run, or just your preferences set to always do anything Anytime while BOINC is set to Run based on preferences?

If the latter, then please check in the web-based preferences for the new setting of "Suspend work if no mouse/keyboard activity in last x minutes". Check what the time set for it is and if it's 10 minutes, reduce it to its default of 0 minutes.

---

I have the settings set to always run.

This one has me confused a bit. Do you mean you have BOINC set to Always run, or just your preferences set to always do anything Anytime while BOINC is set to Run based on preferences?

I tried with my preferences in the BOINC manager set to work while in use and Activity set to Run always.

If the latter, then please check in the web-based preferences for the new setting of "Suspend work if no mouse/keyboard activity in last x minutes". Check what the time set for it is and if it's 10 minutes, reduce it to its default of 0 minutes.

It might not be 10 minutes exactly. That was just an example. Other times that it goes suspended is when I've put the remote desktop in the background and have a local window up in the foreground. I see it go suspend after a few minutes. Probably less than 10.

I will check my web preferences and change that to see if it helps in any case.

In that case also check what your settings are for:

Suspend work while computer is in use?
'In use' means mouse/keyboard activity in last x minutes.

Watch out, some of these settings can also be set through the preferences override menu in BOINC Manager. To see if you use the preferences in BM, check the (old) messages for something like this: |Reading preferences override file

If you don't have that anywhere, you're not using the preferences in BM.

---

Do work while computer is in use? No
Do work only after computer is idle for: 5.0 minutes
Stop work after computer is idle for: 5.0 minutes

Well, if you use those options, then BOINC won't do anything out-right.
It'll wait for 5 idle minutes (when the CPU is doing nothing else) before allowing any project application to start up. Yet the last setting also says to stop work again after (those?) 5 minutes.

The applications running under BOINC are programmed to use the lowest possible priority possible, so anything with a higher priority will take CPU cycles away from them when they need them. You may want to test setting the "Do work while computer is in use" to Yes.

If that takes too much of your server, though, you'll need to work around that with the other settings. I don't know if WCG has the hour settings specifications as well, where you can set BOINC to do work between x and y hours on a 24 hour clock. You may want to program BOINC to use the time slot when the server is least in use.

---