Chances of that succeeding in the present BOINC design are next to zero. You can run a minimal client, just fetch 1 task at the time, the smaller ones such as MIP1, MCM1 who have a 7 day deadline at that with <fetch_minimal_work>1</fetch_minimal_work> in the cc_config.xml file. Nothing will be fetched until the present task is completed and reported.

ahh fair enough i kinda always assumed thats what the select pc thing was for

Where is app_config written in my recommendation?

lavaflow

You mentioned app_config but didn't actually recommend it. I was trying to suggest a simpler way to proceed.

Mike

+1
I was hoping they would add an XML import/export function to allow a user to move a WU or WUs to another client. Since the client has it's shortcomings when downloading work that creates overloaded clients, it would be nice to be able to move some of that extra work to faster clients instead of watching it abort. There have also been times when one knows that a client machine is about to fail, so it would be nice to be able to move that work to other clients instead of just aborting the work. Once moved, the new machine would report the new location to the server on the next scheduler request and download any files that might be missing.