The more I think about this the less I am sure that BAM can do anything to fix it. Both Rosetta & RALPH have a feature to set the target run time of a wu. When you alter the resource share of either of these projects through BAM, the previously set target run time disappears.

I have raised it on the RALPH boards.

I have been in contact with the Rosetta team about this. There are two solutions, but they need to be implemented at theit end.

1: Make sure that project specific settings aren't cleared when new settings are send by BAM

2: Include the settings in BAM and accespt these when BAM sends the settings.

There is a similar problem with SETI. If you change the resource share here any custom graphics settings disappear.

Cheers Willy

(And have a good holiday mate )