 |
|
Message boards : Number crunching : NEW BOINC VERSION
Message board moderation
| Author | Message |
|---|---|
 JIMSend message Joined: 31 Dec 07 Posts: 1152 Credit: 22,363,583 RAC: 5,022 |
Did I read something in this forum last weeks that said they were going to release a new version of the Boinc manager today? |
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
No. You would have read that on the BOINC/dev board. Where it's still listed as a test version. But it's probably not Monday there yet. Edit And they've just put up 7.2.27 for testing for Windows, so no, They're not there yet. :) |
 Send message Joined: 28 Mar 09 Posts: 126 Credit: 9,825,980 RAC: 0 |
7.2.28 is out now as the current version. If you're using a 6.x or earlier version please heed the warning about not being able to go back (unless you back up your client_state files). BOINC blog |
|
Send message Joined: 24 Feb 06 Posts: 47 Credit: 782,082 RAC: 0 |
If you're using a 6.x or earlier version please heed the warning about not being able to go back (unless you back up your client_state files). What does 'not able to go back mean'? thanks |
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
A lot of the program has been re-written from scratch. The part that affects "going back" is the client_state.xml file, BOINC's "to do" list, which is now completely different to the way it was in version 6. So it will be completely useless to version 6, and therefore all of the information needed by the reverted to BOINC 6 will be missing. You can only "go back" if you made a complete copy of everything from version 6 BEFORE you changed to version 7. And even then, work done in version 7 will not be recorded in the old version 6 copy of client_state.xml. It may be necessary to hand craft a new copy of the version 6 file, based on data in the version 7 file. I don't know. Whatever IS involved in "going back" is going to be "messy". If people just want to play around with 7, perhaps the way to do it is with completely new work that can be either completed before "going back", or just dumped. In which case also, completing ALL work in progress on version 6 should be done first as well. Then you can have a blank slate going forward and going back again. |
|
Send message Joined: 28 Mar 09 Posts: 126 Credit: 9,825,980 RAC: 0 |
What does 'not able to go back mean'? thanks The client_state files have different elements in them between version 6 and version 7. If you're already running a v7 client you'll be fine, its just the older ones have different elements. You can actually go back its just that you'll lose any work the v7 client has in progress if you revert back to v6. If the projects have "resend lost tasks" enabled you might get them back that way. I personally never bothered and just upgraded old to new and then familiarised myself with it. Things like work fetch are a bit different between the v6 and v7 clients so you might want to adjust them once you've upgraded. A common complaint is also about the messages tab. The v7 client has an "event log" which opens in a separate window and shows the same stuff the messages tab used to show. BOINC blog |
MikeMarsUK Send message Joined: 13 Jan 06 Posts: 1498 Credit: 15,613,038 RAC: 0 |
... A common complaint is also about the messages tab. The v7 client has an "event log" which opens in a separate window and shows the same stuff the messages tab used to show. Yes, the missing messages tab is very irritating (extra clicks needed to find it), but apart from that, the version of 7 I am on seems OK. I'm a volunteer and my views are my own. News and Announcements and FAQ |
|
Dave Jackson Send message Joined: 15 May 09 Posts: 4540 Credit: 19,039,635 RAC: 18,944 |
Yes, the missing messages tab is very irritating (extra clicks needed to find it), but apart from that, the version of 7 I am on seems OK. Yep, I took a while to find it. still now running 7.2.28 without issue so far :) |
|
JIM Send message Joined: 31 Dec 07 Posts: 1152 Credit: 22,363,583 RAC: 5,022 |
Yeah, I installed 7.2.28 on both of my machines the day after it was released. No problems. Both hadcm3n and hadam3p WU�s running just fine. |
|
Send message Joined: 31 Aug 04 Posts: 391 Credit: 219,896,461 RAC: 649 |
7.2.28 seems to run ok - had one model just now fail with error I can't interpret - but likely not new version fault. Other models other machines continue OK with 7.2. |
|
JIM Send message Joined: 31 Dec 07 Posts: 1152 Credit: 22,363,583 RAC: 5,022 |
I see that there is another new version of the Boinc Manager, 7.2.33. After running on my 2 machines for the last 24 hours I can report that all seems to be going fine. No problems to report. Is this related to the long awaited Boinc server software upgrade that was rumored to be going to take place in November? |
|
Send message Joined: 5 Sep 04 Posts: 7629 Credit: 24,240,330 RAC: 0 |
No. That's just a BOINC bug fix. |
Byron Leigh Hatch @ team Carl ... Send message Joined: 17 Aug 04 Posts: 289 Credit: 44,103,664 RAC: 0 |
yes I am also running BOINC 7.2.33. I can also report that all seems to be going ok, No problems to report. |
|
Send message Joined: 28 Mar 09 Posts: 126 Credit: 9,825,980 RAC: 0 |
The main difference between .28 and .33 was suppressing of image display within notices. One particular project had issues that caused the client to crash. BOINC blog |
|
Send message Joined: 15 Feb 06 Posts: 137 Credit: 35,338,894 RAC: 13,030 |
I now have 7.2.33 working in Windows 8.1. However, I had to clear my old BOINC completely from my registry before it would install. I also had a problem getting it started. When I tried to start it, it told me "the BOINC client has exited 3 times in the last 3 minutes". It would not start properly. I had to start it by using "Run as Administrator" before it would start and run correctly. |
©2024 cpdn.org
