Now BOINC 6.2.16 is withdrawn, too - we're back to 5.10.45 again.

That didn't last long.

Me too, (once I get it running on Vista after having to manually start the Core Client)

The "waiting for memory" is exactly that. Several FAAH's in parallel are memory hungry (at worst it can hit maxima
as per this FAQ). Increasing the Memory use % as per this FAQ (not necessarily the maximum) usually fixes that issue.... most sits anyway in VM.

BTW, can you please size down your illustration. My 1028/760 screen setting makes it not able to read other
posts without scrolling.

thanks

And again, it was released without complete testing. Only try this release if you want to be an unwitting alpha tester.

Good luck!

Well, you passed the first hurdle.... the benchmark fails for some. Anyone who has this is requested to report to the Core Client forum of Berkeley http://boinc.berkeley.edu/dev/forum_forum.php?id=2 and provide details and what you did step by step. Further, there are people succeeding to loose all their work during the migration from 5.10 to 6.2.... again there is a thread where you can deposit the full / gory details as what you did to manage that.

It's too depressing it went out and was instantaneously declared "recommended", but the reported bugs are getting less the higher the point release number climbs.

I am still running an older version of BOINC (5.8.16), which never gives me any problems. Is there a need to upgrade to a higher version? I only use BOINC to be able to run WCG and not so much for GUI-features. Will a higher version make better use of my computer?