Per your request, I’m creating a new thread for this topic.

What I have done and experienced. Tue night (Pacific) I created BAM account and configured it properly, setting home/work/school preferences and BURP and pirates as default projects to attach.

Tuesday night, I joined my main comp at home (BAM ID 156) to BAM, no errors once I found the correct url. It was previously doing work, and I did not abort anything. I had all the projects I work for attached on this computer, but most were set to "no new work" (just for monitoring porpoise). In BAM I selected the projects that were already running on 156, expecting it to detach all the rest. It did not, instead it said "attaching". Fine. so I updated my comp manually from the BOINC manager. Response was successful, but no changes, either in the manager or on the web. I then just detached all the projects that weren’t doing work and went to bed. Curious, I read else ware that I should be able to do it this way.

Next morning only QMC and seasonal were running. I had no time to make changes either then or at work.

Wed night I checked and everything had resumed to normal, all 4 projects were running.
Wed night I also joined my other comp at home (BAM ID 157) to BAM, and then went back the original comp to set the host preference, since the page was already open. I made the changes within the one minuet the manager took to recheck the connection, and everything went as it should. 157 did not have any extra projects attached to it, but did have 4 projects running.

I checked both computers Thursday morning. Everything was running normally.

While at work Thursday afternoon, I took a new computer that we joined to the network (BAM ID 183) and attached BAM from scratch, no existing work at all. The default projects attached just fine. I wanted to add laden to the mix, but every time I selected it and clicked "set", the page would refresh and my original selections would be there. I then manually joined laden in the BOINC manager, which worked. I then updated boinc manually and BAM detached the laden and now on the web it said "detaching". Another update in BOINC removed the text from the web. I then rejoined laden manually, left a note in the other thread, and went home (was the end of the shift). From home I was able to join laden in the host config page just fine.

--edit--

Friday morning I found 156 running with odd settings. First, only 2 projects had work again, this time it was xtream and seasonal. Also, only one project was running at a time, and with TH it should be 2. I am also having problems with BOINC seems to be configured to pause when I am using the comp even though I have selected it to run while comp is in use.

When I got to work, I attached another comp (BAM ID 235) and everything worked just fine. My problems of yesterday were gone.

--end edit--

156 - P4 3.2, 1.5GB ram, boinc 5.4.9
157 - P4 2.8, 1GB ram, boinc 5.4.3
183 - P3 celery 533, 320MB ram, boinc 5.4.9
235 - P3 733, 256MB ram, boinc 5.4.9

I have 6 more comps in a lab room (P3 450s) currently running only hash, but not joined to BAM yet. I can use these to do more testing. Any sugestions on what you would like me to test?


Thx,TM