LHC@home

> They thought that did have the separate connections locked so that they could
> not happen at the same time....

Aft gang agley ...

Well, as I posted in the SETI Forum I have my machines on no network access so I can TRY to prevent that from happening.

I did find out that I had one computer that was still running 4.05 so this is a pre-4.09 bug, not that that is important.

I also dropped Pirates off and on one machine dropped off predictor too ... Time will tell if any of this works to solve the problems.

Bad news is on one system I have about 6 cross-connected WU that are LHC@Home, but are tagged as cp.net ... sigh ...

<p>
For BOINC Documentaion: Click Me!

1) Close BOINC
2) Make back-up copies of all your XML files to a safe directory
3) Open all account_*.xml files and edit the project name so that it is appropriate to the project URL
4) Open client_state.xml. Scroll through the file. Change your project name(s) that you corrected in the account files to match the URLs here, too. Note that the XML file contains project tags for each project. When you find an affected project, you'll see that there is app and file data that is inconsistent with that project. Delete these entries (including tags) from the file. Don't be shy (you made back-ups, right?) -- you can do it again in case you mess something up. Besides, your editor has undo.
5) Restart BOINC
6) It *might* be necessary to detach an orphan project. In my first attempt, I somehow wound up with an extra LHC@home on one machine. It showed 0 results, so I just detached it. My valid LHC@home entry remains fine.

Feel free to delete the invalid files from your project dirs.