The "Project resources" menu is far from self-explanatory. Consider this scenario:

You add a project through your local boinc manager. Later you go to boincstats to set the percentage of your CPU resources it will receive.
You find that it's not there, so you go to "sign-up for projects" and is careful to select "find account".

All well so far. Then you go to "project resources" and find that the new project is listed.
You adjust its resource share and click update. But this will have the effect of detaching the new project from your local computer!

I'm not sure if this is a problem that could be solved by better default settings in the menu or if boincstats ignores or lacks information from the boinc manager. And the problem would of course go away if you always attach projects through boincstats and never the boinc manager. But that's not the path most newcomers will take. They first install the boinc manager and familiarize themselves with it, boincstats comes as a later, valuable addition.

Changing the resource share from the BAM website shouldn't detach your client from the project. However, if you have your BOINC client attached to an account manager, you cannot manually add projects from within the client without it being detached when the project manager synchronizes.

If I attached them before they were added to BAM! I never had problems with a detach, and as an ATA I've done it quite often. Last project I added to BAM! after crunching 40K credits was RNA and I just "found existing account", BAM! contacted about half a day afterwards and I was still attached after that.

I didn't change anything here for that project in the ~half day between adding it and automatically updating my client with BAM! the next morning, perhaps that's the fault. But I really don't see any need for changes at an existing and already running project in the few hours between just adding it to the BAM!-account and the next contact.

Ah, it's more of a BOINC problem then. It shouldn't allow adding projects when it "knows" it's being "remote controlled" by BAM.

With my 5.10.45 BOINC manager, I get
Doesn't this warning appear any longer with newer versions?

Gruß,
Gundolf

No, definitely not, is has to allow such things.
There are always projects in some stage of testing that isn't yet ready to be open, let alone to be mentioned on some sites like this one or, even worse, in BAM!. How should testers, that use BAM!, crunch for those projects?

IIRC, this happens to projects that are connected to BAM, but are not set in BAM to be working on said host. Thus, when the client connects to BAM and sees that you are attached to X project but under BAM host preferences X project is set to detach/delayed detach, BAM tells the client to drop said project.

This would not be the case with projects not managed by BAM, as I myself am attached to such a project (ORE/Renderfarm.fi) and have experienced no involuntary detaches.

I was attached to RNA World long before it was listed here.
I let BAM! look up my accountafter it came to BAM!, and didn't do anything else.
After the next contact RNA was still on my computer, and now as well here in my BAM! settings.