Hello Gymmarn,
The BAM incompatibility is the result of switching from UD to BOINC in 2005. For a while we ran them in parallel, which required hacking the BOINC server code. We fully intend to unhack the code someday, but for the moment it is not on the schedule.

I do not want to sound arrogant or coldly bureaucratic, but I hope that you might consider someday attaching a single machine to WCG without using BAM, to see if it is fun or not. I'm into distributed computing because it seems fun to me.

Lawrence

Here is a link to BOINCTASKS which I also use to manage all my BOINC computers -

http://www.efmer.eu/boinc/boinc_tasks/index.html
.
.

BAM has limited enablement here. BOINCTasks wont fill the Resource/Share aka Project Weight need to change [it cant], but WCG's being default 100 as with any other project. The way than to manage is by assuming the % value of what 100 then is. E.g. let's consider you want to give WCG 20% and project X 50% and project Y 30%. Then at BAM set:

WCG =100
X = 250
Y = 150

There's been talk for years about the full BAM allowance at WCG, particularly the attaching/detaching to WCG which is not possible until the first *at-the machine* attach is performed. Besides the UD issues, another problem is IIRC the secure connection requirement that WCG(IBM) has. Cant remember what the BAM system compliance to that part is/was, but seem to recollect something needed adapting over at Willy's too.

--//--

P.S. At BAM make sure to tick the "attach new host by default" box for WCG at http://boincstats.com/bam/projects.php else BAM could cause WCG to be detached on client sync once you've done a manual attach at the client (if we can seduce you to do that :O).