LHC@home

Boinc Clients 4.25 are available >> http://boinc.berkeley.edu/download.php?dev=1

upgrade from 4.24 to 4.25 was no problem. everythink looks fine, but i think it works a little bit "slower".

Benchmark results (athlon 2900+, winxp sp2):
2005-03-04 12:51:54 [---] Number of CPUs: 1
2005-03-04 12:51:54 [---] 1965 double precision MIPS (Whetstone) per CPU
2005-03-04 12:51:54 [---] 3334 integer MIPS (Dhrystone) per CPU

greetz from old europe

---

Thanks for the v4.25 Link ... :) ... Ill give it a try.

Installed the v4.25 on all my PC's without a hitch ... :)

I don't see any difference from v4.24 but there must be something different like bug killers ... hehe

I also installed v4.25 yesterday. There no obvious difference in the operation other than it seems to start up much faster. Past version of 4.2x were rather slow to display data. The installer has also been reduced in size from 10.4M to 9.12M.

As always, a WARNING has to be made. This is the bleeding edge alpha version of Boinc CC.
Unless you are prepared to bleed and rebuild your system when things go wrong, stay with the official release V.4.19.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

Am running the 4.24 CC...Is it safe to install the 4.25 right on top of the 4.24 or will uninstalling and reinstalling now be the standard practice??

Seems like a lot of work will be deleted needlessly if this is the only 'correct' way to do this.

I just installed the v4.25 right over the top of v4.24 with no problems ...

Thank you PoorBoy for the fast reply.

Seems like a lot of work will be deleted needlessly if this is the only 'correct' way to do this.
==========

Actually if you un-install BOINC first no work is lost, the core files are saved from being un-installed. Then when you re-install the new version the work just picks up where you left off from ...

The reason that 4.25 is a bit slower on some operations is the stack trace code that has been put in to track down a crash that someone was reporting.

---

BOINC WIKI

Thank you John McLeod VII for this infomation

---

> Seems like a lot of work will be deleted needlessly if this is the only
> 'correct' way to do this.
> ==========
>
> Actually if you un-install BOINC first no work is lost, the core files are
> saved from being un-installed. Then when you re-install the new version the
> work just picks up where you left off from ...
>
>

Ahhh I should have added that you must uninstall when going from 4.19 to 4.2x as the code base is substantially different..

My bad.
:)

Ahhh I should have added that you must uninstall when going from 4.19 to 4.2x as the code base is substantially different..
==========

I didn't mention it either because you were talking about going from v4.24 to v4.25 which there is no reason to un-install the Client first unless you wanted to ...

All good here with 4.25, except I had to abort a Predictor WU due to it running to 102% completion.....

No problems since, and looking at the WU it seems a few people had client errors.

So, cannot safely say if it was a 4.25 issue, or a WU issue.

I have a few other small problems with 4.25:

1.) Cannot sort by selecting the headings.
2.) If running more than one project, if you perform a manual update, it will start crunching FOR the project you have updated - only intermittent at this stage.
3.) Closing the application takes a fair while.

---

> All good here with 4.25, except I had to abort a Predictor WU due to it
> running to 102% completion.....
>

Predictor is having problems. Do no abort the Predictor WU it will finish by itself, just as Seti continues to crunch even after reaching 100%. It is just one more issue which needs to be cleaned up. It is better for the project to run to completion.

> No problems since, and looking at the WU it seems a few people had client
> errors.
>
> So, cannot safely say if it was a 4.25 issue, or a WU issue.
>
> I have a few other small problems with 4.25:
>
> 1.) Cannot sort by selecting the headings.

V4.2x are early alpha and many minor features are not implemented yet.

> 2.) If running more than one project, if you perform a manual update, it will
> start crunching FOR the project you have updated - only intermittent at this
> stage.
> 3.) Closing the application takes a fair while.
>

There are still many BUGS to be resolved.

Again, WARNING, V4.2x are for development and should not be used by the faint of heart. TOTAL SYSTEM MELTDOWN IS ALWAYS POSSIBLE WITH ALPHA SOFTWARE.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

Again, WARNING, V4.2x are for development and should not be used by the faint of heart
==========

I've yet to have any of the Development Versions do anything to my Systems, it may not install right or be to buggy to run but other than that v4.25 is running just fine on all my systems ... Thats why you save first before installing the Dev Versions and if things get screwed up you can always go back to what you had before the installation ...

---

> Again, WARNING, V4.2x are for development and should not be used by the faint
> of heart
> ==========
>
> I've yet to have any of the Development Versions do anything to my Systems, it
> may not install right or be to buggy to run but other than that v4.25 is
> running just fine on all my systems ... Thats why you save first before
> installing the Dev Versions and if things get screwed up you can always go
> back to what you had before the installation ...
>

Basically agree, but I have had a situation where the system locked up on reboot, after a first install, several versions ago. I had to uninstall from safe mode. I now never let Boinc autorun on bootup. I still manually remove the shortcut from the Startup folder, since the installer insists on placing one there, no matter what option I choose.

This is why I always place a warning to discourage computer neophyte from using the latest version.

---

Questions? Answers are in the BOINC Wiki.

Boinc V6.10.56 Recommended
WinXP C2D 2.1G 3GB

> I've yet to have any of the Development Versions do anything to my Systems, it
> may not install right or be to buggy to run but other than that v4.25 is
> running just fine on all my systems ...

I ran 4.20 for about 24 hours when it first came out and it really messed over my system. This had to be back in January.. It ran, quit, ran again, restarted my pc, ran, restarted my pc a 2nd time.. and on the 2nd restart whatever was in 4.20 it caused my BIOS (yes my BIOS) to have to be reflashed! Fortunately my BioSTAR mobo has bootblock BIOS and I was able to flash it and things were okay .. but if those events happened to someone who had no clue (or to any laptop manufactured that I can think of), it would have been a very pricey bill to pay to get that machine working again!

Unusual behavior comes with the territory with such software. :)

and my Ambien's kicking in so I'm going to bed now! :)

---

> > All good here with 4.25, except I had to abort a Predictor WU due to it
> > running to 102% completion.....
> >
>
> Predictor is having problems. Do no abort the Predictor WU it will finish by
> itself, just as Seti continues to crunch even after reaching 100%. It is just
> one more issue which needs to be cleaned up. It is better for the project to
> run to completion.
>
Hi All,
I had the same issue where a WU for predictor was showing 102.7 on the progress bar, but in Boinc log it actually showed it was at 96.3%. This was while I was still using 4.24. So I don't believe it is a problem with 4.25. I have seen it happen with only one Wu so far, but it could have been more. The Wu finished as normal with 103.5% and Boinc Log at 100%

Have A Great DAy And A Better tomorrow!

Regards,

Rocky

---

<img src="http://boincwapstats.sourceforge.net/summary.php?name=ML%20Cudd&amp;team=US%20Navy&amp;seti=123863&amp;einstein=4173&amp;lhc=1091&amp;climate=2545&amp;predictor=7916&amp;style=6&amp;ctx=yellow">
WinXP SP2 Boinc - 4.44
Have A Great Day!

http://www.ssl.berkeley.edu/pipermail/boinc_projects/2005-March/000831.html

I'm pleased to announce the 4.25 release of the BOINC client for Windows.



The highlights for this release are:

1. A MSI based installer, for large scale deployments.
2. A new task based GUI which utilizes the wxWidget cross platform
framework, so we could use the same GUI code for the rest of the platforms.
3. Installation options for running in the shared and service execution
modes.
4. A more comprehensive set of GUI RPC's for management of the daemon.
5. Abilities to suspend/resume projects.
6. Abilities to suspend/resume results, even ones which haven't started
executing yet.
7. Abilities to abort results.
8. Abilities to abort transfers.
9. Abilities to add URLs to the GUI Interface on a project specific
basis.
10. Supports multiple messages returned from the scheduler.



We would like to thank the Alpha testers and the various community members
who reported bugs and helped us smooth out the rough edges.



We are still cooking the Linux, Solaris, and Mac versions which should be
showing up in the next week or so.



----- Rom

BOINC Development Team

Space Sciences Laboratory

University of California, Berkeley

> >
> > Predictor is having problems. Do no abort the Predictor WU it will finish
> by
> > itself, just as Seti continues to crunch even after reaching 100%. It is
> just
> > one more issue which needs to be cleaned up. It is better for the project
> to
> > run to completion.

I have found V4.25 quite stable across all projects.

Best to just let the WU run to completion.

There was issues with the earlier v4.2x versions but these seem to be sorted.