With 500 hrs done and less then 100 to go, CPDN decided to quit on me again.
It looks that I'll never get any WU's done.

I've detached CPDN on my main PC.
I still have 1 PC running, and will let it go to the end (probably not), and then I'll stop that one 2.

If someone has news of a more stable version of the CPDN client, give me a shout.

Oh, and don't give me the 'your system is unstable' lecture, because both systems are top of the line, standard-running, virus- and malware- free systems.

Am I angry?
No, just dissapointed that i waisted so many hours of CPU-time without any contribution to science.

Good luck to the rest of you.

---

I am almost to the same point

All other projects (Seti and Pirates for now, LHC and Predictor before they shut down) are rock solid.

I don't think that I've ever gotten farther than about 40% when CPDN throws a Fortram Error or a program exception or for some reason trashes the current WU and downloads another.

The only thing that CPDN really has going for it is that right now, it and Seti are the only ones with work to do. There for a while, they were the only project that actually was giving out work

---

Hi Sting and Ken

Have a look at what I wrote in answer to Steve in his Exit Code -5 thread further down this same message board. What Tolu says there is v. significant.

I'm now back on classic cpdn, which is working perfectly just as it did before I tried boinc. I will stick with this until boinc becomes more Athlon-compatible or until I need a new processor. What I don't know is whether you can run boinc (for Seti etc) and cpdn classic simultaneously.

The matter has been extensively discussed on the classic forum. See the 1 in 8 thread. Or, for my experiences in allegorical style, the Server in Switzerland still Down thread.

---

__________________________________________________

> I will stick with this until boinc becomes more
> Athlon-compatible or until I need a new processor.

It's mysterious though, because I've had no trouble at all running either classic or BOINC flavours with an Athlon CPU, Nor, it seems, have most others, though I realise it's no consolation to those who can't.

---

> What I don't know is whether you can run boinc (for Seti etc) and cpdn classic simultaneously.

There are a couple of ways it could be done (the first definitely works, the second might).

1) On multi-processor systems (including P4 HT) change the general preferences to restrict the number of processors that BOINC uses. You need to restart BOINC after updating preferences before this takes effect.

2) When I tested CPDN classic and BOINC on the same system the classic version stayed idle if it started up after BOINC. After suspending and resuming BOINC the processing power was shared equally. Testing was on a P4 HT and if might be different on an Athlon.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

> Hi Sting and Ken
>
> Have a look at what I wrote in answer to Steve in his Exit Code -5 thread
> further down this same message board. What Tolu says there is v.
> significant.
>
> I'm now back on classic cpdn, which is working perfectly just as it did before
> I tried boinc. I will stick with this until boinc becomes more
> Athlon-compatible or until I need a new processor. What I don't know is
> whether you can run boinc (for Seti etc) and cpdn classic simultaneously.
>
> The matter has been extensively discussed on the classic forum. See the 1 in
> 8 thread. Or, for my experiences in allegorical style, the Server in
> Switzerland still Down thread.
>

But all my machines are Intel based PIII/P4/P4M, so at least in my case, it's not related to Boinc on an Athlon

---

Hi everybody

Not all Athlons seem to be boinc-incompatible, and I don't pretend to have the slightest idea why. However, my machine not only rejected every single boinc model (even after I'd applied all the advice I could find on the boards, read the entire boinc-cpdn manual, and upgraded to 4.13), but also produced impossible climates in every model even in 1811-12.

There has been discussion elsewhere about how 2 machines running the same model with the same parameters can occasionally produce divergent results. Those results, however, only diverge in phase 2 or 3, which means that some small difference is gradually compounded. My machine produced rubbish from the outset. The reassuring thing is that the calculation errors were detected and the models automatically truncated.

Why models don't sit stably on some Intel systems probably has a different cause. I can only recommend consulting the aforementioned manual, as it does explain lots of points that are not immediately obvious.

Meanwhile, classic continues to perform flawlessly...............

---

__________________________________________________

So what you are saying is while the classic CPDN is working correctly (never used that one), the BOINC version is flawed?

---

> So what you are saying is while the classic CPDN is working correctly (never
> used that one), the BOINC version is flawed?
>

Well, actually many people did have problems running the classic model. There's nothing to suggest that BOINC is any worse, but it is the most demanding task that most people will ever put their machines through.

---

Hi Sting

No, I'm not saying that the boinc version is flawed. I agree with Andrew that cpdn is a particularly demanding task 1. because the model itself is complex and 2. the model has to stay put without crashing out for so long (6 weeks+ on my machine working 24/7, though other people with newer, more powerful machines crunch much faster). Lots of people are crunching the boinc version effortlessly.

What I am saying is that I spent quite a lot of time learning exit the model and turn off the machine without losing it, then thinking that my continuing problems were due to version 4.04, and finally concluding when I still had problems with 4.13 that my Athlon and boinc don't like each other and require extended therapy. Other people who have come into cpdn-boinc at a later stage can maybe learn from this experience, not spend so much time losing models, and take quicker remedial action.

They will sort out this problem of models crashing, but I've no doubt it will take time. I'm sure that many problems don't surface until after projects are launched. Beta-testing isn't enough, because the people who sign up are experts, not typical of users like me.

---

__________________________________________________

> They will sort out this problem of models crashing, but I've no doubt it will
> take time.
>
No problem.
I'm ready to try again when they've sorted out the problems.

I'll check in from time to time.

---

Most of the crashes on my machines have been associated with heavy video / CPU usage by another program, usually a video game. I have had one crash when Norton AV was running.I have had no crashes under moderate usage situations such as browsing, emailing, or non video intensive games. Civ III is fine. battlefield 1942, Warcraft III, or Zoo Tycoon are not.

I have changed my Boinc preferences to Suspend CPDN when the user is active. I am still keeping BOINC in memory.

I have no idea whether or nor this will result in an improvement in my success ratio but am going to give it a fair run.

---

In reply to the following:

> Hi Sting
>
> No, I'm not saying that the boinc version is flawed. I agree with Andrew that
> cpdn is a particularly demanding task 1. because the model itself is complex
> and 2. the model has to stay put without crashing out for so long (6 weeks+ on
> my machine working 24/7, though other people with newer, more powerful
> machines crunch much faster). Lots of people are crunching the boinc version
> effortlessly.
>
> What I am saying is that I spent quite a lot of time learning exit the model
> and turn off the machine without losing it, then thinking that my continuing
> problems were due to version 4.04, and finally concluding when I still had
> problems with 4.13 that my Athlon and boinc don't like each other and require
> extended therapy. Other people who have come into cpdn-boinc at a later stage
> can maybe learn from this experience, not spend so much time losing models,
> and take quicker remedial action.
>
> They will sort out this problem of models crashing, but I've no doubt it will
> take time. I'm sure that many problems don't surface until after projects are
> launched. Beta-testing isn't enough, because the people who sign up are
> experts, not typical of users like me.
>

did You have a look at Your log-files. Do You just happen to have the same problem as me. Take a look at my post.

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

ChrisD

---

> I'm now back on classic cpdn, which is working perfectly just as it did before
> I tried boinc. I will stick with this until boinc becomes more
> Athlon-compatible or until I need a new processor. What I don't know is
> whether you can run boinc (for Seti etc) and cpdn classic simultaneously.
>
You can run CPDN-Classic and BOINC simultaneously. They usually share the resources nicely 50-50.

ChrisD

---

> You can run CPDN-Classic and BOINC simultaneously. They usually share the
> resources nicely 50-50.
>
> ChrisD


This would bear the risk of a -5 error :-/

last WU is nearing competion (only 50 hrs to go)
I keep getting
climateprediction.net - 2005-01-31 08:47:50 - Result 3cl9_100177857_0 exited with zero status but no 'finished' file
climateprediction.net - 2005-01-31 08:47:50 - If this happens repeatedly you may need to reset the project.
climateprediction.net - 2005-01-31 08:47:50 - Restarting result 3cl9_100177857_0 using hadsm3 version 4.04

What will happen if i choose to reset the project?
Will I lose the WU again?
Can I keep going without resetting?
[edit] BOINC 4.13, and no I'm not upgrading now ;)[/edit]

---

Just ignor that message and keep going without resetting.

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.