os 10.3.9, Boinc is ALWAYS keeping my processor pegged at 100%. This is the version I downloaded yesterday in order to update from Classic.

Yes, I do have "no" for "do work while computer is in use?"

Yes, I have Updated the project, and Reset the project, after first verifying my preferences. No help at all.

The thread with a similar title told me to verify prefs and Update, and since the thread ends there, perhaps that user had prefs set wrong. Therefore I create this new question thread.

I've run about three thousand units on both my work computer and my home machine, but I do not wish to have my system so sluggish while at work, so ... I'll _try_ to remember to 'Resume' when I go home at the end of the day, but I bet that will get old swiftly.

Any ideas?
Thanks very much! I'd like to continue to help on this project if it's workable....

I've used the "do work" setting of "no" only once, for my daughter's iBook G4, and because she was almost _always_ "using" it if it was powered up, thus getting close to missing deadlines, I changed the setting to "yes", and she never noticed. I've got "yes" on both my Mini and my iBook G3, and see no sluggishness at all on either. Still, the option is there, and if you need it, it should work. I've never heard of the option just flat not working on a Mac, although it's common on Win98...

The best idea I can come up with, other than rechecking your prefs to be sure, and stopping and starting BOINC Manager, then looking in the Messages tab to verify that it's reading the prefs from the right site and venue (home, school, work), is to NOT run BOINC Manager at startup. Instead, set BOINCSaver as your screensaver, with whatever delay you like. It will start BOINC automatically when it detects that it isn't running, so your computer will do BOINC work whenever the screensaver is running, and stop when you move the mouse. If you use the "Options" to set it to go to a blank screen after a fairly short interval, it shouldn't impact your performance by much at all.

We want you contributing too, we'll help however we can!

Sometimes when trying to think of every possible complicated answer and workaround to a problem, I overlook the obvious...

In the Commands menu are options for "Run always" or "Run based on preferences". Would you check those for me?

Sigh... thought of that while eating lunch...

(1) Yes, it was set to "run based on preferences". (Even though I'm a good programmer, I do make dumb little mistakes often enough! ... but not this time I think.)

(2) I did try stopping & starting Boinc, but as Boinc was then stuck in 'suspended' mode for hours, didn't know if that helped until I went home for the weekend & came back ... Boinc running again, but again always at 100%.

Will try (3), not-running Boinc at startup, only as screensaver ... that sounds likely to work ... but first I'm going to try & get some of the work done that they pay me for ... :^)

... thanks for your help ...

==dave

---

I've used the "do work" setting of "no" only once, for my daughter's iBook G4, and because she was almost _always_ "using" it if it was powered up, thus getting close to missing deadlines, I changed the setting to "yes", and she never noticed. I've got "yes" on both my Mini and my iBook G3, and see no sluggishness at all on either. Still, the option is there, and if you need it, it should work. I've never heard of the option just flat not working on a Mac, although it's common on Win98...

The best idea I can come up with, other than rechecking your prefs to be sure, and stopping and starting BOINC Manager, then looking in the Messages tab to verify that it's reading the prefs from the right site and venue (home, school, work), is to NOT run BOINC Manager at startup. Instead, set BOINCSaver as your screensaver, with whatever delay you like. It will start BOINC automatically when it detects that it isn't running, so your computer will do BOINC work whenever the screensaver is running, and stop when you move the mouse. If you use the "Options" to set it to go to a blank screen after a fairly short interval, it shouldn't impact your performance by much at all.

We want you contributing too, we'll help however we can!

How do you set BOINC to not run at startup? The "Options" button in the screen saver does nothing. What is wrong?

---

How do you set BOINC to not run at startup? The "Options" button in the screen saver does nothing. What is wrong?

Hi Howard !

To NOT run BOINC at startup go to System Preferences> Accounts> Login Items, and Uncheck BOINC Manager.

Kevin

<edit> reply to you down below instead of to myself ...

<re-edit> ok, couldn't move it to bottom of page; maybe you'll read it anyway!

---

... run according to prefs never did work as far as not having it run 'always' .. (i do notice unresponsiveness sometimes, and killing boinc did help) ...

... _was_ just trying to remember to change boinc's settings when i went home at night ...

... BUT, finally tried killing boinc manager as startup and only using as screensaver ... and it works fine!

Thanks!


(of course, i can no longer run it at home on my winbox, as it requires too much space on my tiny C partition (even though its main stuff goes to D), but that's another problem entirely that won't get solved until i either re-configure my drive or get a new one for that box, but i don't plan on doing much with windows in the future, so that won't happen....)

---

SETI within BOINC fails to pause when user activity is detected if the setting "Leave applications in memory while preempted" is set to "Yes". Changing this setting to "No" solves the problem. This problem does not occur for other projects: rosetta, LHC, Einstein, climateprediction and Predictor. They all pause when user activity is detected when they are told to stay in memory. This appears to be a bug specific to SETI within BOINC.

---

Thanks Gavin - I have reported this bug to the developers.

Had a similar problem for sometime now. SETI under BOINC does NOT pause even if I select "Suspend" from the BOINC Manager GUI. The task shows up as suspended, the message log reports that the task has been suspended, but "top" doesn't agree; SETI worker still at 100% CPU.
This, however, does NOT happen when using BOINC CLI.

As Gavin said, SETI within BOINC MANAGER fails to pause when user activity is detected if the setting "Leave applications in memory while preempted" is set to "Yes". Changing this setting to "No" solves the problem. So, the problem is specific to BOINC MANAGER and SETI workers, since it seems to work fine with BOINC CLI. The problem persists no matter which worker is used (original non-enhanced, optimized builds, or the new enhanced worker).

---