Hello,
I've been trying to get the SETI/Boinc fine tuned for runing onone of my ASUS Win 10 laptops. If I set the options to work when nothing else is really running, it works as expected...after X amount of time the processor starts the various tasks (determined by percentage of CPU usage and CPU cores), as long as the mouse or keyboard isn't molested. If the preferences are set to always run, it does just that...runs continuously as it should based on the CPU/GPU options.
Where my problem comes in is that, when running based on preferences, the system will begin to process normally after X amount of time, but roughly 60 seconds after the last mouse or keyboard movement, the program suspends processing and displays a message " Suspended - Computer is not in use " , followed by a bunch of keys. The only way I can keep this going is to set the preferences to "Run Always", which makes it necessary to juggle processor time and percentage in order to get decent computer performance. "Run based on Preferences" is preferred since I can use the CPU/GPU when needed for SETI and free them up when needed by other programs. I've looked at every option I can think of but nothing seems to allow it to run after a minute has passed. I know there are other options, but nothing seems to make a difference or change the timeout to anything other than 60 seconds. Setting the time period for the mouse/keyboard will change the time period before processing starts, but 60 seconds after last keyboard/mouse input and processng gets suspended. I have never seen this particular error message before. Any thoughts?

Jim

---

Set "Suspend when no mouse/keyboard input in last N minutes" to 0 or ---

Also make sure you set the preferences in the right place. Local preferences in BOINC Manager override web preferences. You can check which ones you use by going Options, Computing preferences. Here it says at the top which prefs you now use. Mind that pressing OK or Save will apply local preferences.

---

Thank you for the reply. The preferences are set to Local (as opposed to web based). The mouse/keyboard was reset to various values ranging from 0 , .1, and 1. The GPU processor begins working after about 10 seconds (depending on the value in the box, typically .2 ). Everything proceeds as normal until roughly 1 minute/60 seconds passes, when Computation stops processing and displays the message mentioned in the original msg:
"Suspended - Computer is not in use(.187 CPU)"
I haven't seen this message before and I can't figure out what the problem could be. I'm not using any screen savers and the problem happens regardless if the preferences are set to always run and to ignore mouse/keyboard timeouts or not. The system seems to work properly until 60 seconds elapse, regardless of any settings or values listed in the preferences. If I choose to allow the system to "Run Always" (listed under ACTIVITY), then the 60 second issue doesn't happen...only when the system is set to run based on preferences do I see the 60 second suspension.
Its confusing, especially with 2 different areas that influence processing actions. For some reason, I timeout after 60 seconds but only if not set to run always. [/quote]

---

Hi, have you any anti-virus program who wait inactive time to scan for viruses ? and then makes the computer active ?

---

Please post the contents of the global_prefs.xml and global_prefs_override.xml files in the data directory. You can open these files in Notepad, no need for an XML editor.

The BOINC data directory is a hidden directory, default at C:/Programdata/BOINC/

---

Here are the requested files:

Global_Prefs

<global_preferences>
<source_project>http://setiathome.berkeley.edu/</source_project>
<source_scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</source_scheduler>

<mod_time>1452909830</mod_time>
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>90</cpu_usage_limit>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>0</run_if_user_active>
<run_gpu_if_user_active>0</run_gpu_if_user_active>
<idle_time_to_run>1</idle_time_to_run>
<suspend_if_no_recent_input>1</suspend_if_no_recent_input>
<suspend_cpu_usage>65</suspend_cpu_usage>
<work_buf_min_days>4</work_buf_min_days>
<work_buf_additional_days>2</work_buf_additional_days>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<disk_interval>60</disk_interval>
<disk_max_used_gb>25</disk_max_used_gb>
<disk_min_free_gb>6</disk_min_free_gb>
<disk_max_used_pct>30</disk_max_used_pct>
<ram_max_used_busy_pct>80</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90</ram_max_used_idle_pct>
<leave_apps_in_memory>1</leave_apps_in_memory>
<vm_max_used_pct>25</vm_max_used_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
</global_preferences>

and the 2nd file, Global_Prefs:

[quote]<global_preferences>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>0</run_if_user_active>
<run_gpu_if_user_active>0</run_gpu_if_user_active>
<idle_time_to_run>0.200000</idle_time_to_run>
<suspend_cpu_usage>65.000000</suspend_cpu_usage>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>1</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>4.000000</work_buf_min_days>
<work_buf_additional_days>2.000000</work_buf_additional_days>
<max_ncpus_pct>80.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>30.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>25.000000</disk_max_used_gb>
<disk_max_used_pct>30.000000</disk_max_used_pct>
<disk_min_free_gb>6.000000</disk_min_free_gb>
<vm_max_used_pct>25.000000</vm_max_used_pct>
<ram_max_used_busy_pct>80.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
<max_bytes_sec_up>0.000000</max_bytes_sec_up>
<max_bytes_sec_down>0.000000</max_bytes_sec_down>
<cpu_usage_limit>90.000000</cpu_usage_limit>
<daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
</global_preferences>

Any insight is appreciated. I either crunch numbers or work on the computer...they don't seem to play well together as it currently stands.

Jim

---

Okay, confirm for me please. The first one is the global_prefs.xml file, the second the global_prefs_override.xml file?
I ask this specifically, because the local preferences will only override web preferences that are available in both places. There aren't override preferences for all of the web preferences available in the local preferences. So only some values used in the global_prefs_override.xml file will be used to override values set by the web site preferences (in global_prefs.xml). When there is a value in global_prefs.xml but not in global_prefs_override.xml, the preference value from global_prefs.xml will be used.

Which in the case of the above is: <suspend_if_no_recent_input>1</suspend_if_no_recent_input>
This preference is in the global_prefs.xml file, but not in the global_prefs_override.xml file and thus isn't overridden.

This value will suspend computing after a set time out, because it is the line for Suspend when no mouse/keyboard input in last N minutes that I referenced in my first answer. Uncheck this value at https://setiathome.berkeley.edu/prefs.php?subset=global, or when leaving it checked, set it to zero (0). Then allow for BOINC to contact the project to get those renewed preferences in.

---

I want to thank everyone who helped me to figure out this confusing issue. It is working properly now with no problems with the timeouts now. I would have thought that the file in question would have re-written itself to reflect the harmony between global and local preferences, but hey...its working!! :)

Thanks again,

Jim

---