Computer is running Seti@home classic project, another seti@home project on BOINC. And one climateprediction project on BOINC. First download got a \"wrong state\" error prompt. Then next download gets \"computation error\" prompt. The downloads were supposed to last some 1000 hours to completion. But next thing I see, computer is uploading finished computation, and one computation error to boot! what\'s the matter?

Make sure you're running version 4.x of BOINC.
also note that climateprediction.net is not supported on Win98 & NT platforms
I think you might have a version 3.x client_state file.
maybe this wasn't deleted after upgrading or installing version 4.x.

My problem is very similar to JimMaz's. I've got an Inspiron 8600 laptop running WinXP SP1, BOINC Beta 4.05, all 3 projects and also SETI Classic command-line with SETIDriver and SETISpy (let me know what else you need).

I didn't start running climateprediction until after seeing a comment about it in the SETI realm. I believe it wouldn't let me start working on a WU until after I'd installed the v4 client. Much to my dismay, all three projects I've started have produced one trickle's worth of data each, then shortly thereafter said 'Computation error' and died.

I haven't seen that Visual Fortran error at any time, though. Is this still related?

Corgi

> My problem is very similar to JimMaz's. I've got an Inspiron 8600 laptop
> running WinXP SP1, BOINC Beta 4.05, all 3 projects and also SETI Classic
> command-line with SETIDriver and SETISpy (let me know what else you need).
>
> I didn't start running climateprediction until after seeing a comment about it
> in the SETI realm. I believe it wouldn't let me start working on a WU until
> after I'd installed the v4 client. Much to my dismay, all three projects I've
> started have produced one trickle's worth of data each, then shortly
> thereafter said 'Computation error' and died.
>
> I haven't seen that Visual Fortran error at any time, though. Is this still
> related?
>
> Corgi
>

Also - read the FAQ:

Timeslicing between BOINC projects
If you are time slicing make sure you've set your preferences to have Leave applications in memory while preempted? set to yes (the BOINC default is no). CPDN checkpoints every 144 timesteps, and if you don't leave it in memory any calculations you've done since the previous checkpoint will have to be redone when CPDN starts up again. If other applications require the memory CPDN may get swapped out, but that's a much smaller overhead than you'd get if you were preempted at 143 timesteps!


Timbo