BOINC v4.13 released.

[Rattledagger]

V4.13 is now released, and the download-page have at last also changed.

This version fixes the problem many had with v4.12 there the core client wasn't responding, and used 100% cpu-usage.

To upgrade, download from http://setiweb.ssl.berkeley.edu/download.php
Stop the old client and install the new over top.

 

[zaph]

dang it!
i just upgraded the herd to 4.12 today
!!

no wonder some people are waiting to switch over
🙁

 

[Rattledagger]

If you didn't have any problems with v4.12 then installing it, there shouldn't be any problems to continue using v4.12 since the only fix in v4.13 is to make sure you can't use zero minutes in the preference "Switch between applications every NN minutes"


BTW, if you've installed BOINC as service on all your computers, an easy way to upgrade BOINC is to install it to one computer and use 2 small batch-files to do the rest. If using NT & installed BOINC as service it will look something like this:

upgrade.cmd
netsvc boinc \\%1 /stop
copy "c:\boinc-dir\boinc.dll" "\\%1\c$\boinc-dir"
copy "c:\boinc-dir\boinc_cli.exe" "\\%1\c$\boinc-dir"
copy "c:\boinc-dir\boinc_gui.exe" "\\%1\c$\boinc-dir"
netsvc boinc \\%1 /start
exit

boinc_upgrade.cmd
call upgrade.cmd computer001
call upgrade.cmd computer002
call upgrade.cmd computer003
... (continue listing computers...)

Of course it's also possible to only use one batch-file, but if example an upgrade changes more files it's easier to use 2. 😉
computer001 can either be machine-name or ip-address.
boinc-dir of course depends on where you've installed BOINC. 😉

 

[zaph]

Nope, no service installs yet,
but if you could point me to a nice faq on how to do it, i might start using it on a few relatives remote computers. 🙂

 

[Rattledagger]

To install as service on NT, stop the gui.
Open a cmd and
cd "\program files\boinc" (if default install-directory)

boinc_cli.exe -install

And it should be installed as service.
On XP, you must also go into service control panel, and make sure the BOINC-service is running as "localsystem".

And start the service, or reboot. 🙂

Only problem is, some users has reported installing as service gives an error-message, but personally have not had any problems on nt4 & win2k so...