Is there actually a recommendation which BOINC Version at least is needed for SETI@home Beta?
I read about that it should be at least BOINC V7.0.25.
But it should be used better the still current DEV-V7.0.28 - yes?
This is meant if BOINC run stock?
Or with an app_info.xml file it could be used also e.g. BOINC V6.12.34?
Thanks :)
EDIT: Just changed the icon of the title. ;)
Hi Sutaru,
While I don't use Boinc V7 myself, I believe there are problems with the current recommended 7.0.25 , which meant it really should not have been 'recommended'. I'm told 7.0.28 is much better, even though not made it to recommended yet, is a far better choice.
For the sakes of testing on seti@home beta project I think it depends whether you want to find problems with seti software, or problems with Boinc software, or Both. With seti-beta delayed while project staff are up to something else important (don't know what, but it must be good) I think testing out 7.0.28 for Boinc might be a good idea.
When stock 6.98 / x41y comes out soon, testing that will be the new priority, along with AKv8c following, so a 'known good' Boinc setup would be the choice.
Jason
I have 1 machine running 7.0.28 and the other 2 running 6.12.43.
The other 2 will be updated eventually, but I am waiting for them to start working on 7.1.x first as that usually means they have most of the major bugs worked out.
If I upgrade my current BOINC V6.12.34 to V7.0.28, I need to note something special?
Because it's V6.x to V7.x, e.g. maybe before upgrade it's needed to uninstall V6.12.34 first?
Or something other?
It's possible to downgrade easily from V7.0.28 to V6.12.34 if maybe wanted?
Thanks :)
Quote from: Sutaru Tsureku on June 18, 2012, 04:32:20 PMIt's possible to downgrade easily from V7.0.28 to V6.12.34 if maybe wanted?
I think no (but could be wrong). That's probably the major sticking point.
Jason
Correct. Upgrading from BOINC v6.12.34 to v7.0.28 is simple, with no uninstall needed (though a few project preference settings get forgotten until the first update with the new BOINC).
But once you've upgraded, you can't downgrade easily from v7 to v6.
For a few minutes I upgraded to BOINC V7.0.28 from V6.12.34.
Always I up-/ or downgrade I uninstall the previous installed version first.
Sure is sure... ;)
If uninstallation, no WUs are lost. ;)
You can't downgrade easily because some client_state.xml entries are not backwards compatible.
Downgrading would kill the cache.
The major point to observe when moving from v6 to v7 BOINC is to swap the cache settings around.
Where you had a setting of 'connect every' 0.5 and 'keep additional' 3 [or whatever you actually have] you need to switch to a setting of
'keep at least' 3 and 'keep up to ... more' 0.5 i.e. swap the numbers around.