During pre-boinc climate prediction I finally quit after two weeks with no trickle and no answer about what the problem was. (I don't mind risking 10 or even 100 hours, but not three months. It also made me nervous the talk of searching for files in the hard drive to manually upload.) I am now giving boinc climate another chance. After a few hours the first boinc climate crashed. I downloaded another boinc climate. BOINC now won't download any other projects and I am only running climate. Would it help to go to 4.19? Wait for a new boinc version? Wait for a fix from climate? I do not mind if I am not updated every day with a trickle on this project, but I should have something within a week or so. If I can't resolve this within 2 weeks or so I will give up all together on climate. Months of computing time is just too valuable to risk.

---

Months of computing time is just too valuable to risk.

I gave up a long time ago just to much time involved and it dosn't play nice with
others!

---

Would it help to go to 4.19? Wait for a new boinc version? Wait for a fix from climate?

Climate is having problems once again. Reverting back to an earlier version of BOINC won't help as they are having yet another problem with the trickles where they upload but aren't being credited by their system.

I'm going to complete the WU I have from them but will drop the Climate Prediction project after it's done as they have had too many problems with crediting work since I joined the project. I lost count of how many trickles of mine that have been lost or they reversed out at a later date.

---

To truly explore, one must keep an open mind...

I'm suprised there's no Earthquake Predicition boinc project.

I'm suprised there's no Earthquake Predicition boinc project.

There will be I'd bet!

---

CPDN's unfortunate problem, server glitches notwithstanding, is that the WUs are so HUGE! Even with a one year deadline they manage to send a recent client version into Earliest Deadline First mode.

Without going into a rant about the client's scheduler, it might be an idea to have a feature in the manager to turn that off, and let it go into strictly-by-resource-share computing.

---

CPDN's unfortunate problem, server glitches notwithstanding, is that the WUs are so HUGE! Even with a one year deadline they manage to send a recent client version into Earliest Deadline First mode.

Without going into a rant about the client's scheduler, it might be an idea to have a feature in the manager to turn that off, and let it go into strictly-by-resource-share computing.

Well this thread made me look at CPDN. It restarted my WU from the beginning. I was more then half way through my WU and now it's a 2% complete.. Yes it is the same WU. Sorry but it is detached..

---

I'd rather speak my mind because it hurts too much to bite my tongue.

American Spirit BBQ Proudly Serving those that courageously defend freedom.

I gave up a long time ago just to much time involved and it dosn't play nice with others!

It's always played well with others on my machine, although I'm sure it might not be the case on a slower machine. I'm currently running CPDN alpha, which has even longer running WUs and a shorter deadline. Even it hasn't sent my CC into EDF. (CC 4.45)

I gave up a long time ago just to much time involved and it dosn't play nice with others!

It's always played well with others on my machine, although I'm sure it might not be the case on a slower machine. I'm currently running CPDN alpha, which has even longer running WUs and a shorter deadline. Even it hasn't sent my CC into EDF. (CC 4.45)

Not surprised yours is doing fine... it's a top-of-the-line Athlon. But for me, even with a 1900+ from just a couple years ago, it's in EDF mode.

---

[font='fixedsys,courier']Both.

It seems that CPDN + BOINC Manager = CPDN crash unless you copy all of CPDN's *.dylib files into /opt/something/or/other, which is really stupid because this doesn't happen when you use BOINC Menubar.

The whole schpiel is here.[/font]

---