...and some rhetorical fighting...

I modified the foundership change page so that it now just says it's disabled and to contact me if you have a legitimate request. [...] I'll take the requests case by case and decide on what action to take.

Peter, I checked with BOINC. They said it's up to Rosetta, that the transfer option has been enabled with BOINC.

Of course, Rosetta sends you an email, confirming that you've applied for the position, and stating you need to wait 60 days for the current team founder to respond to their email query.

Then, every time you log in, and look at your team page, it tells you that you've applied for team founder, and on what date you can make that transfer, if the current founder does not respond.

Only after the 60 day wait, only when you click on the "assume founder" button, are you informed that the team founder transfer has been disabled.

You don't have to worry about me slowing down, Peter. ;)

Not only that, he would gain access to the email address's our team members have trusted me with. I'm sure some of the lawyers in my team could sort some sort of charges out against you if it did happen, on privacy grounds.
Pissed off and upset with Rosetta@home :(

Please, please, please notify us of new versions in
Rosetta Application Version Release Log.

By full cycle do you mean one whole day/ 24 hours?

The log file is going to be huge. Updates every couple of seconds due to CPU throttling (set at 85%)

Or is this what you were expecting:

Thu 16 Oct 2008 11:09:25 AM PDT||[cpu_sched] Suspending - CPU throttle
Thu 16 Oct 2008 11:09:25 AM PDT|rosetta@home|[cpu_sched] Preempting hombench_mtyka_foldcst_simple_foldcst_simple_t305___4612_2720_0 (left in memory)
Thu 16 Oct 2008 11:09:25 AM PDT|rosetta@home|[task_debug] task_state=SUSPENDED for hombench_mtyka_foldcst_simple_foldcst_simple_t305___4612_2720_0 from suspend
Thu 16 Oct 2008 11:09:26 AM PDT||[cpu_sched] Resuming - CPU throttle

Tue 14 Oct 2008 09:11:13 AM PDT|rosetta@home|Restarting task hombench_mtyka_foldcst_simple_foldcst_simple_t305___4612_2720_0 using minirosetta version 134
Tue 14 Oct 2008 09:30:10 AM PDT|rosetta@home|Restarting task hombench_mtyka_foldcst_simple_foldcst_simple_t305___4612_2720_0 using minirosetta version 134

Removed some lines to save some space here, but the same messages repeat

Found my default cc_config.xml
I assume you mean you want us to switch to

<cpu_sched>[b]1[/b]</cpu_sched>
    <cpu_sched_debug>[b]1[/b]</cpu_sched_debug>

This is about problems with Minirosetta v1.34 as there does not appear to a "thread" for it!

My very personal theory is that the text "max # of error/total/success tasks" is misleading and should read "max # of error/total/success results".

By the way, I doubt that we may conclude from "max # of error/total/success tasks" = 1, 2, 1 that Rosetta should not send out more than 2 replications of the same task.

By the same interpretation we should have to conclude that Rosetta terminates a task upon receiving one result with "Client error/Compute error". It doesn't,

it terminates upon receiving more than 1, that is 2, error results.

And Rosetta is perfectly capable of accepting more than 1 (again = 2) success results under ordinary circumstances, giving proper credits to everyone.

You could try to use the mentioned debugging flags for a couple of minutes, whether it will reveal something...

Where is this cc_config.xml file located? I can't seem to find it.

<cc_config>
<log_flags>
<cpu_sched>1</cpu_sched>
<cpu_sched_debug>1</cpu_sched_debug>
<checkpoint_debug>1</checkpoint_debug>
<task_debug>1</task_debug>
</log_flags>
</cc_config>

This issue of reissuing a task to someone that may not receive credit for it has been on the BOINC "to do" list for over a year. Here is a link to the trac item: Server reissues task more then "total" specified

minimum quorum 1
initial replication 1
max # of error/total/success tasks 2, 2, 2

You could let them run but then the other user crunches but gets no credit.
Check each one, if the task has been reassigned I personally would abort them so as not to hurt the new guy.

The WU has been reassigned because your computer did not finish before the deadline which seems to be ten days. Actually, once the WU hsa been reassigned, there is a race: the first of the two computers to report will get credit, and the second will get a Validation Error and no credit.

Ths should definitely not happen until the second guy's deadline will pass!! (If it does, it is BOINC server-side error, which should get reported and repaired. The second guy is given a promise to be able to crunch the reassigned WU until his new deadline.)

minimum quorum 1
initial replication 1
max # of error/total/success tasks 1, 2, 1

You should abort tasks that have passed the deadline.

You could let them run but then the other user crunches but gets no credit.
Check each one, if the task has been reassigned I personally would abort them so as not to hurt the new guy.

The WU has been reassigned because your computer did not finish before the deadline which seems to be ten days. Actually, once the WU hsa been reassigned, there is a race: the first of the two computers to report will get credit, and the second will get a Validation Error and no credit.

not when BOINC is installed in the protected mode (as a service).

You say 'protected mode', thing is I installed Boinc mgr in its standard form, I did not select anything different than the defaults. So is 'protected mode' the default? If so, how do you change it so that 5.98 will show the graphics?

Can anyone explain why I might be getting this kind of repeating error?

9/28/2008 11:17:09 PM|rosetta@home|Task hombench_mtyka_foldcst_boinc_test3_foldcst_simple_t302___4585_718_0 exited with zero status but no 'finished' file
9/28/2008 11:17:09 PM|rosetta@home|If this happens repeatedly you may need to reset the project.
9/28/2008 11:17:09 PM|rosetta@home|Restarting task hombench_mtyka_foldcst_boinc_test3_foldcst_simple_t302___4585_718_0 using minirosetta version 134
9/28/2008 11:17:50 PM|rosetta@home|Task hombench_mtyka_foldcst_boinc_test3_foldcst_simple_t302___4585_718_0 exited with zero status but no 'finished' file
9/28/2008 11:17:50 PM|rosetta@home|If this happens repeatedly you may need to reset the project.
9/28/2008 11:17:50 PM|rosetta@home|Restarting task hombench_mtyka_foldcst_boinc_test3_foldcst_simple_t302___4585_718_0 using minirosetta version 134
9/28/2008 11:18:31 PM|rosetta@home|Task hombench_mtyka_foldcst_boinc_test3_foldcst_simple_t302___4585_718_0 exited with zero status but no 'finished' file
9/28/2008 11:18:31 PM|rosetta@home|If this happens repeatedly you may need to reset the project.

This is only an excerpt of the series of messages. I've had a few WUs do this recently.

The task is being restarted each one hour. Your cpu_run_time_pref seems to be 3 hours, so it is probably something different.

The task is still not reported. Could you please try to add <cpu_sched> and/or <cpu_sched_debug> (and possibly also <task_debug>?) to your cc_config.xml and let the client reread it (BOINC Mgr / Advanced / Read config file) without stopping the client?

Don't confuse the WU runtime preference, with the other BOINC prefernces such as how frequently to switch between applications.

Basically, the message about restarting is an indication that the task was suspended and is now beginning to run again. Your BOINC preferences basically dictate what conditions would suspend a running task. The simplest being that another task from another project begins running.

If you've included all of the messages, then that is not the case here.

Perhaps you have set up BOINC to not run while the computer is in use? If so, then each time to step up to use it, BOINC suspends the tasks. Then once the machine is idle for the configured period of time, it resumes what it was doing.