...to send a second unit until the upload of the last unit is in progress or completed, this would enable my slowest machine to collect a bonus.
No settings in computing preferences will make this happen at the moment.

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Setting your cache really low (maybe .01) should stop the BOINC client from asking for more work until you are almost done with the last WU.

---

Thanks - Steve

It is set at 0 and still sends work.

Thanks for the reponse.

...to send a second unit until the upload of the last unit is in progress or completed, this would enable my slowest machine to collect a bonus.
No settings in computing preferences will make this happen at the moment.

How would that allow ever completing workunits for which the first computer failed in a way that kept it from ever uploading the outputs? I suppose that the server could wait until this computer is no longer still eligible for a bonus, though, or keep the first computer eligible for a bonus for the normal length of time (not the same as the deadline time) even if some other machine returns outputs for that workunit first.

I found that for my fastest machine, I had to keep it running close to 24 hours a day AND set a low cache length to make it eligible for a bonus, rather than just a normal credit without a bonus.

Also, have you even tried getting the cache size really low but not quite zero?
I MIGHT have seen something saying that .01 is the lowest value that actually works; I don't remember clearly.