Running 4.45 on two machines, both with Seti and ClimatePrediction set for 50% resource sharing. On the desktop PC, switching between applications takes place every hour. On the laptop PC, a CP report deadline of 15 Oct 2006 seems to prevent switching:
09/11/2005 13:00:00|climateprediction.net|Deferring computation for result 1ex1_100086669_0
09/11/2005 13:00:00|SETI@home|Resuming computation for result 16ja04aa.28310.19505.167318.75_1 using setiathome version 4.18
09/11/2005 13:00:06||Suspending work fetch because computer is overcommitted.
09/11/2005 13:00:06||Using earliest-deadline-first scheduling because computer is overcommitted.
(I forced the switch by suspending/resuming work)
Time is now 16:15, so no switch for 3 hours.

---

It's very doubtful that the earliest deadline first mode (panic mode) is brought o n by CPDN. Since its deadline is in October 2006, it's Seti@Home that is running in EDF mode at this moment.

How many work units do you have for Seti?
What is your setting on the connect every X days in your preferences?
And the big question is how fast your computers are. What are they? Speed of CPUs? Amount of L2 cache? Operating system? Using an optimized client/science application?

---

Hi Jord:
Desktop: AMD Athlon 3500+, 1024MB memory 976 KB Cache XP Home SP2
Laptop: AMD Athlon 1600+, 384 MB memory 976 KB cache XP Home SP2
Connect every 0.1 days (same on both)
When I posted there were two SETI work units. There are none now. Latest messages for laptop are:
10/11/2005 10:54:00|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
10/11/2005 10:54:00|climateprediction.net|Requesting 0 seconds of work, returning 0 results
10/11/2005 10:54:01|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
10/11/2005 10:54:02||Suspending work fetch because computer is overcommitted.
10/11/2005 10:54:02||Using earliest-deadline-first scheduling because computer is overcommitted.
10/11/2005 11:40:35||request_reschedule_cpus: project op
10/11/2005 11:40:35|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
10/11/2005 11:40:35|SETI@home|Requesting 0 seconds of work, returning 0 results
10/11/2005 11:40:37|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
10/11/2005 11:40:39|SETI@home|Deferring communication with project for 10 minutes and 4 seconds

---

Did you just change over to 4.45 or has it been longer that you ran it? Is the laptop doing anything at this moment, or is it playing dead in the water (aka not crunching at all ;))?

---

Been running 4.45 since Oct 13, initially with SETI; only started dual projects on 2 Nov.
Currently, CP is preempted and 1 SETI WU is running.
Messages since booting laptop are:
11/11/2005 08:31:58||Starting BOINC client version 4.45 for windows_intelx86
11/11/2005 08:31:58||Data directory: C:\\Program Files\\BOINC
11/11/2005 08:31:59|climateprediction.net|Computer ID: 244387; location: home; project prefs: default
11/11/2005 08:31:59|SETI@home|Computer ID: 94132; location: home; project prefs: default
11/11/2005 08:31:59||General prefs: from SETI@home (last modified 2005-11-10 13:44:57)
11/11/2005 08:31:59||General prefs: no separate prefs for home; using your defaults
11/11/2005 08:31:59||Remote control not allowed; using loopback address
11/11/2005 08:31:59|climateprediction.net|Deferring computation for result 1ex1_100086669_0
11/11/2005 08:31:59|SETI@home|Resuming computation for result 14ja04aa.23090.3873.897148.211_0 using setiathome version 4.18
11/11/2005 08:31:59||Suspending work fetch because computer is overcommitted.
11/11/2005 08:31:59||Using earliest-deadline-first scheduling because computer is overcommitted.
Local time is now 1000.

---