Note that the work request was for GPU work - that\'s for a NVidia or ATI graphics card.

That computer really has been turning in a lot of completed models and doing an impressive amount of work.

Unless you plan to run work from a CUDA project on that graphics card, stick with BOINC 6.2.19 for the time being. You\'ll see from the project News thread (top of the Number Crunching section) that this is what the CPDN moderators are advising for the time being.

So far as I can tell there is no way to contact anyone, anywhere,via email if I have a problem. ( wotht he experitment and model) but I am forced to post and hope a person with authority notices it. The contact support is a webring. impossoble to contact and impossible to leave.
If i wanted to mention my experiment wanted to stop workign, for example/ or if i kept getting a main servers are down call again later message for the first time in 5 years. ubless of course it\'s some sort of club that i wandered into and should never have been let into?

5) So, has the founder updated his email address on his Account page? (It\'s an option near the top.)

I think the main problem is that the Team Founder made a new account. So changing his email address to the old address doesn\'t automatically make him TF.

He needs to log in with either the old account, or with the account key of that old account, before he can make any changes. Since he can\'t request the account key to be sent to him as the old email address is defunct, that\'s giving him the problem. Had he not made a new account, but just changed the email address on the old account, there wouldn\'t have been a problem.

So as the 3rd option he just has to wait another 3 weeks until the option to take over the team is given free to him.

Why 2 months? To give team founders time to react. What if someone is on vacation or in the hospital for some time? There\'s also a 3 month wait after which you can try again, if you get waved off by a TF or miss the window at which you can take over as TF.

So:
If you want someone to just go in and click \"approve\", prove, in a way that will \'stand up in a court of law\', that both the \'old\' and \'new\' person\'s that you mention are, indeed, one and the same.

PS
Why isn\'t the team founder posting here, either instead of, or as well?
This could be considered as suspicious.

Did the founder recieve an email?

No, he doesn\'t have that email address anymore.

If the team founder does not respond to your email challenge within 2 months time, then the team founder option will be given to the person who sent the email.

Did someone follow the transfer team link?

Did the founder recieve an email?

If the founder receives that mail, he\'ll know which address he used to create the team, and can use the procedure to retrieve the password.

Nice! I think someone else on my team is fixing this. Thanks guys, glad the project updated to include that feature for us.

If the founder receives that mail, he\'ll know which address he used to create the team, and can use the procedure to retrieve the password.

What I find a little odd is the change in the speed of the model recently, from 1.425s/ts to 1.53 at the most recent trickle, which is often a sign of PC instability (or, alternatively, that the model is running on a different PC to the one it started on).

Hi Sangamon, fancy meeting you here!

No need to worry about that message, it should disappear again in a day or so. It is benign, if annoying.

If it lasts for a few days, you can shut down BOINC and do a system reboot. That usually gets everything resynched again.

But, whatever you do, DON\'T PRESS THE RESET BUTTON! This will delete your model(s)!

There\'s a post by Thyme Lawn on the php forum here

http://www.climateprediction.net/board/viewtopic.php?t=5097

and suggestions from Dagorath on this forum

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=4951

Perfect, thanks!!

And just because a model gets re-issued does not mean that you can\'t continue with it; it just means that the researchers will get a second opinion on that dataset.

There\'s a post by Thyme Lawn on the php forum here

http://www.climateprediction.net/board/viewtopic.php?t=5097

and suggestions from Dagorath on this forum

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=4951

As long as you\'re only running one project, then you can simply ignore this (it\'s harmless). However if you\'re running multiple projects, it will interfere with scheduling and work fetch. In that case, you can (with care) edit the various XML files to reset the dates - I don\'t have a link to the instructions, but they\'ll be on this forum somewhere.

My computer was having trouble with its integrated network card, so I replaced the motherboard. Boinc has rescheduled the deadline for my climateprediction.net task from 12/13/2007 3:45:52 PM to 12/13/1901 3:45:52 PM. Will this correct itself on the next trickle-up? Or is this work-unit now expired and worthless?

Different error:

Model crashed: umshell1.f: U_MODEL: Illegal combination of submodels

Haven\'t seen that one before but wonder whether the Run was restarted from a backup taken while the Model was running? Or from a backup taken of only the CPDN sub-folder?

chances are it resulted from an unstable parameter mix. (A guess
on my part, but there have been too many recently not to suspect parameters. No biggie, though, the scientists also have to see what *doesn\'t*
work. [I know, small consolation.])

Simply move the entire boinc folder, then reinstall boinc into the same folder. This sets the proper Registry values and does nothing to harm your work in progress.

I\'m getting a new system soon, but if possible I\'d prefer to carry over the WU my old PC is in chewing on. Would a simple folder copy of Boinc files work, or will the naturally changeing machine ID cause problems?

Not the end of the world if it doesn\'t work, but since the WU\'s do take quite a bit of time it would be nice to be able to finish the one I\'ve already started.

As far as I know it\'s only the founder who can do that... :-(

Both. But it\'s unlikely to happen for several reasons.