Hi:
I\'m a little concerned. The launch is scheduled for the 26th and some of us are still having issues running the Beta in Linux with few suggestions (sorry Carl know you are busy) like \"is your PC overclocked\".

Realizing this is /was a Beta test I didn\'t expect too much.

The other CPDN forum was great for assistance but with this one I think that things seem to be missed. These forums will be flooded with issues after the launch.

Sorry for the Rant, but were some of the problems solved? work arounds? I\'ve tried looking around but can\'t find anything.

DaveN

Hi there,

i'm not running Linux boxes but yes, there has been some problems in BOINC Beta.
Finally and rather accidentaly ('cause this forum has now funcional search engine and sucks) found Carl's answer.
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=280#1575

Yes, there will be new build for public launch so [hopefully] most of the bugs found in alpha and beta will be fixed.

Also, Colin is promissing something about web pages/forum so that "hopefully you'll all be reasonably happy"
http://www.climateprediction.net/board/viewtopic.php?p=19197#19197

It has been suggested that FAQ in needed to prevent forum 'flooded with issues after the launch'. For many other suggestions and opinions on 'Future of the forum' see there
http://www.climateprediction.net/board/viewtopic.php?t=2194&postdays=0&postorder=asc&start=0

Some we have some promises and will see tomorrow (or later tonight)
And yes, i agree with majority to keep classic forum 'cause it MUCH better and BOINC so far.
http://www.climateprediction.net/board/viewtopic.php?t=2197

P.S. Sorry for mess of links - too lazy to code all HTML when no phpBB available.
<img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=56&amp;trans=off">

Honza:

Thanks for the information, I sure that the FAQ will help a lot for many of us. I was trying the Linux Beta as I'd like to get away from M$. We'll see with the launch tomorrow, hopefully there will be some information on what people who installed the Beta are to do to get the new client up and running, how to resolve some of the crash issues, etc.

DaveN

EDIT: note that BOINC link is alive and directly available from classic homepage.
Will try migration to 4.05 BOINC client...


&gt; Honza:
&gt;
&gt; Thanks for the information, I sure that the FAQ will help a lot for many of
&gt; us. I was trying the Linux Beta as I'd like to get away from M$. We'll see
&gt; with the launch tomorrow, hopefully there will be some information on what
&gt; people who installed the Beta are to do to get the new client up and running,
&gt; how to resolve some of the crash issues, etc.
&gt;

As for Beta -&gt; Public migration, hopefully the same scenario as Alpha -&gt; Beta will work. Making a full BOINC backup prior to following instruction is recommended; actually, i'm doing regular daily BOINC backup as when beta testing classic client. Note that filenames/folder naming is a bit different in Beta but structure remains.

[pasted from old Alpha web page before it is flushed, text by Carl].
If you are currently running a client with the old client/website that is fine, it should finish and upload. If you running the Windows or Linux client and would like to 'migrate' your current alpha test run to use this improved client and website, please do the following:

Note the currently running experiment/workunit name in your "old alpha" BOINC, (i.e. "4000_0043120000")
You are going to want to copy the files matching this workunit name that are in your old_boinc/climateapps2.oucs.ox.ac.uk_cpdn/ folder, i.e. it would be the 4000_0043120000.xml file and the 4000_0043120000 folder as an example
Download the 'special' BOINC 3.90 client, attach to this site: http://climateapps2.oucs.ox.ac.uk/boinc with your old authenticator code (you can get your code emailed to you from the Your Account link
You should get a new download of the CPDN client (3.15) and a new new experiment (or two...or 100 ;-). If not please check your user preferences and make sure that you have enough disk space, and that your BOINC setting allows for using a disk drive that has a high enough percentage, etc.
Note the name of the experiment that starts up (i.e. "4110_004324334")
Stop your boinc client
Copy over your "old boinc" experiment .xml file and the folder with the same name.
Rename the new experiment .xml and folder to something else (or you can delete it as it will not be needed)
Rename your "old boinc" experiment .xml file and folder that you copied over to the new experiment name from boinc (i.e. rename 4000_0043120000.xml to 4110_004324334.xml and 4000_0043120000 folder to 4110_004324334 in my example)
Restart your new boinc client, it should pick up where you left off in the new model. One odd quirk is that now we are using the BOINC CPU time accounting (as we should) which will show time reset to 0 (and consequently the finish time will be a little odd as well
<img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=56&amp;trans=off">

I'm not sure the old trick of copying an old run into a new folder will work with the launch version; it's probably best to "Detach Project", get the new BOINC 4.05 client (launch version) which will then get the new CPDN. There have been many changes over the past two weeks to fix things up in Linux, basically everything but the kitchen sink is compiled statically in the BOINC client &amp; CPDN apps!

&gt; I'm not sure the old trick of copying an old run into a new folder will work
&gt; with the launch version; it's probably best to "Detach Project", get the new
&gt; BOINC 4.05 client (launch version) which will then get the new CPDN. There
&gt; have been many changes over the past two weeks to fix things up in Linux,
&gt; basically everything but the kitchen sink is compiled statically in the BOINC
&gt; client &amp; CPDN apps!
&gt;
Yes, you are propably right - i haven't succeded in 4.02 model -&gt; 4.05 migration.

btw, is there possibility of Inactiveta account to prevent new model download until ours 4.02 running are finished?

<img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=56&amp;trans=off">

well the way BOINC does upgrades is it will do it after a workunit is finished. I have set all workunits from the alpha/beta as "frozen", so when your run is finished you'll get a new workunit and you should get the 4.03 hadsm3 then. You may want to upgrade to BOINC 4.05 anyway though?