But, even if that is not so, why not, as a compromise, set Activity/Run Based On Preferences and set (for this computer only) at Advanced/Preferences.../Processor Usage to fixed times when you want it to run SETI in your normal "resting hours". This can be done for every day the same, or for each day of the week individually. Then, on the odd occasion that you do "overtime", you can set Activity/Suspend and revert to Activity/Run Based On Preferences when you finish. As I said, it's a compromise, but if all else has failed.....

Keith
P.S. You'll need to download and upgrade to 5.10.26 to use the time scheduling, as it was not working , if I remember correctly, in 5.10.24 (or was it 5.10.20) and earlier. This may possibly also correct your original problem even with no changes in settings, so it's worth updating before anything else..

Do you set the "Day of Week Override" to the times you want it to run or the times you want it to NOT run?

And I'm wondering if this will work, since it seems to ignore the preferences.

Actually, I tried that...the daily settings do not save, nor does the computer use them. If I run the client it works fine, but installing as a service on Mac OS X only seems to allow the option to run constantly or never run...no in-between.

What am I missing here?

As I mentioned earlier, this option does not work on earlier versions of BOINC Manager, so make sure you're updated, preferably to 5.10.26. Earlier versions discarded amendments immediately after adjustments were made. From your reply above, it seems as though you are running an older version of BOINC Manager 5.10.xx when you say it "does not save".

The exact formatting required is shown by hovering the cursor over the entry box. The ON time is first and OFF time second. So, it looks strange to do, as I have done, to "switch off" by ticking Tuesday and entering "22:00-17:00" to stop network activity during weekly outages.

Keith

P.S. You can confirm that it works correctly by putting a temporary entry in for the current day-of-week as, say, "23:00-01:00" and then go to the messages panel where you will see the relevant message immediately. As an example, here is an extract from my Tuesday message panel:

Tue 23 Oct 17:00:00 2007||Suspending network activity - time of day
Tue 23 Oct 19:34:44 2007|SETI@home|Computation for task 21mr07ab.17658.1299.13.6.126_0 finished
Tue 23 Oct 19:34:44 2007|SETI@home|Resuming task 21mr07ae.14665.4571.5.6.54_0 using setiathome_enhanced version 527
Tue 23 Oct 22:00:00 2007||Resuming network activity

P.P.S. Just checked, and it appears you are still running 5.10.20, which explains it. Just update from the SETI@home website Download/AllVersions and 5.10.27 is now available. It's so much easier now. You don't even have to quit BOINC Manager to do so, but do make sure that all completed tasks are uploaded first with an "update" from the Projects panel. Don't panic if you see "suspended" in the Tasks panel, as that is a routine CPU benchmark test which takes exactly one minute.

Keith

But, even if that is not so, why not, as a compromise, set Activity/Run Based On Preferences and set (for this computer only) at Advanced/Preferences.../Processor Usage to fixed times when you want it to run SETI in your normal "resting hours". This can be done for every day the same, or for each day of the week individually. Then, on the odd occasion that you do "overtime", you can set Activity/Suspend and revert to Activity/Run Based On Preferences when you finish. As I said, it's a compromise, but if all else has failed.....

Keith
P.S. You'll need to download and upgrade to 5.10.26 to use the time scheduling, as it was not working , if I remember correctly, in 5.10.24 (or was it 5.10.20) and earlier. This may possibly also correct your original problem even with no changes in settings, so it's worth updating before anything else..

Do you set the "Day of Week Override" to the times you want it to run or the times you want it to NOT run?

And I'm wondering if this will work, since it seems to ignore the preferences.

But, even if that is not so, why not, as a compromise, set Activity/Run Based On Preferences and set (for this computer only) at Advanced/Preferences.../Processor Usage to fixed times when you want it to run SETI in your normal "resting hours". This can be done for every day the same, or for each day of the week individually. Then, on the odd occasion that you do "overtime", you can set Activity/Suspend and revert to Activity/Run Based On Preferences when you finish. As I said, it's a compromise, but if all else has failed.....

Keith
P.S. You'll need to download and upgrade to 5.10.26 to use the time scheduling, as it was not working , if I remember correctly, in 5.10.24 (or was it 5.10.20) and earlier. This may possibly also correct your original problem even with no changes in settings, so it's worth updating before anything else..

I have the latest version of BOINC installed on a Macbook (Intel Core Duo), and set it to run as a service. In the preferences, I set it to run after the computer has been idle for 5 minutes...but unless I manually start it, BOINC never starts (regardless of how long the Macbook is idle).

With the Mac plugged in, I've got power management set to never sleep the machine, and I've tried reinstalling BOINC.

Any ideas?

You mean (to confirm) OSX System preferences Energy Saver is set to "Never" sleep?

It's worth checking to see the settings in BOINC Manager main menu Activity.
I keep mine on "Run Always" and "Network activity based on preferences".

You may also find it useful, assuming you have broadband, to set Advanced/Preferences/NetworkUsage/Tuesday to "22:00-17:00" as this will stop repeated requests for task download/upload to SETI when the regular weekly outage for maintenance is taking place.
I think these times are correct as UTC. but if they are local time you may need to revise accordingly.

Under Advanced/preferences the options only apply to "this computer" only over-riding other settings made elsewhere.

Hope this may help

Keith

Yes, it's set to "Never" in the power management settings.

I didn't want to have it running "Always", as I only want to run BOINC when I'm not using the computer. Which is why I set it to run as a service and to run after the computer has been idle for 5 minutes.

In BOINC go to the Advanced menu and select preferences. Clicking the Clear button and then updating the BOINC client will use the accout preferences. My Mac Pro was using the default preferences when I migrated my login to it from a G5 tower.

Taras

OS X has such clean tasking that I am unable to tell if Bionc is up or down by the way my system functions. Once I thought Bionc was the source of a slow down, but it turned out to be a fragmented disk. Set it to always run and if you haven’t, look at this thread some time. http://setiathome.berkeley.edu/forum_thread.php?id=39135

I have the latest version of BOINC installed on a Macbook (Intel Core Duo), and set it to run as a service. In the preferences, I set it to run after the computer has been idle for 5 minutes...but unless I manually start it, BOINC never starts (regardless of how long the Macbook is idle).

With the Mac plugged in, I've got power management set to never sleep the machine, and I've tried reinstalling BOINC.

Any ideas?

You mean (to confirm) OSX System preferences Energy Saver is set to "Never" sleep?

It's worth checking to see the settings in BOINC Manager main menu Activity.
I keep mine on "Run Always" and "Network activity based on preferences".

You may also find it useful, assuming you have broadband, to set Advanced/Preferences/NetworkUsage/Tuesday to "22:00-17:00" as this will stop repeated requests for task download/upload to SETI when the regular weekly outage for maintenance is taking place.
I think these times are correct as UTC. but if they are local time you may need to revise accordingly.

Under Advanced/preferences the options only apply to "this computer" only over-riding other settings made elsewhere.

Hope this may help

Keith

I also had this problem a while ago with Mozilla with BOINC 4.25 under XP. The only thing that helped was installing Firefox. I tried everything else short of reinstalling Windows :(

One of Windows' undocumented features I'm afraid :/ It probably does'nt have to be Firefox, any _new_ browser installation should work.