Hello,

I'm a little disenchanted right now.
I just installed the new version, and it does not recognise all the work I'd started, or completed.

The last few versions quite happily picked up where the others left off.

I'm running Vista 64, and hope others have not had similar experiences.

The client wants me to attach to projects, and I've tried with one, which has produced no results.

Suggestions on how to resume would be appreciated.

Where was BOINC installed and did the new version install to the same place?

If it was installed under the "program files" tree, copy the existing folder to a new place, "c:\boinc" for example. Then install the new version pointing to that folder.

---

BOINC WIKI

BOINCing since 2002/12/8

update: installation fixed.

I had all projects working on existing data.

On a sadder note, other projects I'd signed up to, are now failing.

---

Hi Ralph

Well done for sorting out the installation.

If you can tell us which projects' tasks are failing and tell us the exit or error code numbers of the crashed tasks, or quote the boinc manager messages if they give any details about the task crashes, somebody may be able to advise you about why this is happening and how to avoid it.

Due to Boinc 5.10.21 (Linux) stopping and no longer responding I had to install something to fix the problem.
Boinc 5.10.21 would not run, it would start then stop after a few seconds, even without the manager running.

Unfortunately I installed 5.10.45, BIG mistake.
It totally wiped all data from the Boinc folder and then started as if it was a new install.
I stopped and reloaded all old data from a copy but on starting it wiped it all again (including a 160 year CPDN model with less than 20% to go).

Reinstalling Boinc 5.10.21 made no difference, it still would not run so I rolled back to 5.8.16 and it ran ok, so upped to 5.10.8 and while it would run via the client, the manager would not run at all, not even start.

Then went back to the 5.10.45 install and let the thing go it's own way, I then had to go round almost every project I had on that computer (9 of 11) and merge all the new computers I did not have (but would probably like).

Although all is now working again, I am not happy with BOINC and there disregard to how their data installs.
As Ralph said all the recent versions had no problems picking up where the last one left off.

Mine could be related to the fact that as an older Linux distribution (Fedora Core 3) I had to download the version without the manager installed and had to copy one over from a previous version to see what was going on.

I believe this had a lot to do with it, and more testing should of been done.

I wasted over 3 hours sorting things out, so NOT amused.
It has made me give up on CPDN, as I need stable software to run that and Boinc is not stable, it reset the data for CPDN twice while it was running before it killed it altogether.
And I still don't know why the 5.10.21 version stopped.

I am not updating my other computers.

Due to Boinc 5.10.21 (Linux) stopping and no longer responding I had to install something to fix the problem.
Boinc 5.10.21 would not run, it would start then stop after a few seconds, even without the manager running.

Unfortunately I installed 5.10.45, BIG mistake.
It totally wiped all data from the Boinc folder and then started as if it was a new install.
I stopped and reloaded all old data from a copy but on starting it wiped it all again (including a 160 year CPDN model with less than 20% to go).

Reinstalling Boinc 5.10.21 made no difference, it still would not run so I rolled back to 5.8.16 and it ran ok, so upped to 5.10.8 and while it would run via the client, the manager would not run at all, not even start.

Then went back to the 5.10.45 install and let the thing go it's own way, I then had to go round almost every project I had on that computer (9 of 11) and merge all the new computers I did not have (but would probably like).

Although all is now working again, I am not happy with BOINC and there disregard to how their data installs.
As Ralph said all the recent versions had no problems picking up where the last one left off.

Mine could be related to the fact that as an older Linux distribution (Fedora Core 3) I had to download the version without the manager installed and had to copy one over from a previous version to see what was going on.

I believe this had a lot to do with it, and more testing should of been done.

I wasted over 3 hours sorting things out, so NOT amused.
It has made me give up on CPDN, as I need stable software to run that and Boinc is not stable, it reset the data for CPDN twice while it was running before it killed it altogether.
And I still don't know why the 5.10.21 version stopped.

I am not updating my other computers.

The problem with BOINC crashing was something the LHC did. Any computer that was uploading to LHC during its recent outage was going to crash on start until such a time as LHC came back up. No, we have not figured out exactly why that occurred.

I have installed almost every single version since 3.1 directly on top of the existing installed version. There was only one time where there had to be an uninstall first - and that was known and advertised in advance. My bet is indeed that your lost work was due to the funny install that you had to do. There is currently a discussion in the boinc developers email list about what linux packaging *should* be. At the moment, there are three different camps - one that says that there should be 2 installs - one for headless and one for both client and UI. One that says there should be one for UI and one for client. And the third that says there should be one install that does not include the libraries needed to run the UI as dependencies.

---

BOINC WIKI