Well my small farm is still runnin CC 4.19. While it works great I seem to have the itch to upgrade to CC 4.45. I particularly like the EDF mode I keep reading about on the CC 4.45 release which would help keep my older machines turning things in by their deadline. Anyway, I wanted to get the peoples opinion, is it time for me to move on up? Any quirks that one should know about before beginning this journey? Thanks for any input...

God, yes. Change. Most everyone is running 4.45. I am on 8 boxes and have no issues, although I'm not interested in running umpteen projects at the same time.

---

May this Farce be with You

Well my small farm is still runnin CC 4.19. While it works great I seem to have the itch to upgrade to CC 4.45. I particularly like the EDF mode I keep reading about on the CC 4.45 release which would help keep my older machines turning things in by their deadline. Anyway, I wanted to get the peoples opinion, is it time for me to move on up? Any quirks that one should know about before beginning this journey? Thanks for any input...

Hi,

upgrade to 4.45! The scheduler works great for me. Since i use it, and left it balancing the workload on its own, i am able to participate in 8 active projects without ever missing a deadline ... and that with my computer only switched on ~12/7.

Femue

Any quirks that one should know about before beginning this journey? Thanks for any input...

If you decide to move on, make sure you exit your old Boinc client completely (check in Task Manager or something similar to see everything quit its processes), then uninstall the old client before installing the new one. Any workunits still on your computer shouldn't go lost.

The next thing to do is run it and be patient. Depending on the amount of projects you run per computer, it can take a couple of days for the new scheduler to work as it should. The Statistics tab shows its graphics after about 72 hours.

But if you do run into anything you perceive as a problem, either check in the Boinc Wiki what it means, or else don't hesitate to ask around here.

---

Any quirks that one should know about before beginning this journey? Thanks for any input...

If you decide to move on, make sure you exit your old Boinc client completely (check in Task Manager or something similar to see everything quit its processes), then uninstall the old client ...

... and you may want to make a backup of your BOINC-Directory at this point to be absolutely sure nothing can go wrong. Then carry on with Ageless' advice.

Femue

Well all my machines participate in Seti, Seti Beta, Climate, Protein, Einstein, LHC, LHC Beta and Sztaki. So it seems the concensus is to upgrade. Well, surely someone must have a negative view :)... Anyway, if I recall right I will need to move to a new version of Boincview. I am currently running 0.9.2d to manage everything. Keep the input coming...

Well all my machines participate in Seti, Seti Beta, Climate, Protein, Einstein, LHC, LHC Beta and Sztaki. So it seems the concensus is to upgrade. Well, surely someone must have a negative view :)... Anyway, if I recall right I will need to move to a new version of Boincview. I am currently running 0.9.2d to manage everything. Keep the input coming...

Well ... i use Boincview 1.1.3 and it is stable and i like it a lot because of the different colors (since 1.1.2) that you can link with different result- and project-states ... but i have no farm, so i can't really give the best advice ;-)

Femue

double post - too much "Fiege Pils" ;-)

God, yes. Change. Most everyone is running 4.45. I am on 8 boxes and have no issues, although I'm not interested in running umpteen projects at the same time.

I have run into some problems with 4.45 - might be a case of 4.19 uninstall not cleaning up properly, might be some other variable.

When I set up a new system, I go with 4.45. I also look to shift over to 4.45 when I'm in multiple project mode. Though in some cases the problems installing 4.45 on an existing system have gotten in the way.

---

yea I hate change but I figure eventually they are gonna twist my arm. At the same time their must be a reason they left 4.19 available...

yea I hate change but I figure eventually they are gonna twist my arm. At the same time their must be a reason they left 4.19 available...

Some people have trouble with the versions beyond installing? or something, I can't remember what the problem was exactly. However it was/is serious enough that some computers can not (could not) run the later version.

---

BOINC WIKI

BOINCing since 2002/12/8

If you hate changing, you may want to wait a bit to see what the next recommended version is. 4.45 does have a bug in the calculation of LT and ST debt (seems to have disappeared from 4.72). The connection from the manager to the daemon is less reliable in 4.45 than it is in 4.72.

---

BOINC WIKI

I never had any problems about changing from 4.19 to the next version (wasn't it 4.25 back then???) and I never made any back up. I just uninstalled my client, downloaded the new one and installed it, and my WU's were safe and sound. So just go ahead! :-)

---

"I'm trying to maintain a shred of dignity in this world." - Me

well I have transitioned all my machines from 4.19 to 4.45 with the exception of one, my linux box. When I try a run 4.43 on it I get the following:
[root@dlci boinc]# ./boinc_4.43_i686-pc-linux-gnu.sh
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers

gunzip: stdin: invalid compressed data--crc error

gunzip: stdin: invalid compressed data--length error
tar: Error exit delayed from previous errors

I have no clue as to what this means. I am really hoping someone can help. The last 4.19 worked perfectly. I had a script call it at bootime. Anyway, I notice this one is called "boinc_4.43_i686-pc-linux-gnu.sh" The last binary was called "boinc_4.19_i686-pc-linux-gnu". Not sure why one has the "sh" and the other doesn't. Any help would be greatly appreciated...

Ok well I finally got this to work. I went here http://mkx.feridot.com/boinc/#boinc444 and downloaded the boinc_4.44-i686-p2-linux-gnu optimized binary. I just replaced my old one and it worked. I am not sure why it was version 4.44 and not 4.43 but it worked. It's crazy that the stock 4.43 would not work.