I changed resources from 1 to 0 for Einstein on one of my hosts, After synchronizing with !BAM my resources on the PC went from %1 to %100 instead of %0.

When I went back here to see what happened I noticed that resource was no longer 0 it was "Project Default" and that phrase changed to "-1" when I position the mouse into the value.

I need %0 for resource. My understanding from the BOINC help forum is that 0 means that a work unit is to be download if and only if a CPU or a GPU is available and unused. This is a way (the only way actually) to prevent a queue of work units from forming.

Change it on Einstein, not your host.

I set it to 0 on the project and will try that but I suspect I will have to disconnect from the project as my client shows %100 even though it is 0 there.

Could this be a bug? If I set "-1" meaning use "Project Default" but my boinc client uses !BAM for manager, how can it do both?

Selecting "sync with manager" should find a "-1" at !BAM and go to Einstein and return the "0" ?? that is not happening. I get %100 always
====edit====
I did the following
Einstein: venue = "home" and resource = "0"
!BAM Einstein resource ="-1"
At PC: did an update to contact Einstein and get venue = home but did not pick 0 for resources, still %100
At PC: I do a "sync with account manager" and I still see %100 resource for BOINC. So I will wait till Tuesday when SETI goes off-line and hopefully only a single work-unit, one for each GPU, will be downloaded as the venue shows %0 for resources (at project website no on pc). If this works, great!!! If not, then I will abort probably 300 or more work units as this system has 9 GPUs and Einstein is my fallback project when there is nothing else to do.

OK, I disconnected and the re-connected to !BAM and now haver resources = 0 showing up on the BOINC client (my PC).

I did get a 2nd CPID (project) and have 2 entries for my PC, not sure that is bad or not.

In any event I show resource 0 for Einstein and 100 for SETI and GPUGRID so will see what happens when project SETI goes off-line.

Might work!!

There was a bug which ignored the '0' value which set the value to '-1' This is fixed.