I don't see anything like that in my device preferences for BOINC. Where is that for BOINC?

Thanks! I'll try that and see how the behavior changes. I knew that ID had limits on both run time and clock time and presumed the "Report Deadline" date in BOINC was the same sort of thing. Could you expand on the quorum point? It almost sounds like even if I have BOINC only pull one wu at a time, I could delay the quorum if I went several days without BOINC running.

Thanks mycrofth! I suspect that there are a lot of factors that could delays in getting a quorum. I know with the UD agent, you could crunch only when it was running as a screensaver. Not sure about doing that with BOINC as I've always run whenever my machine was powered up. But it would seem that it could be days, even a week before you get a result back from a user.

From my perspective, I want to have enough WU on hand to crunch for two days as that seems to be the longest that that's been in terms of a server outage, inability to connect to the server or my DSL connection being down (I guess I could connect over dial up on those rare occasions). I like how this is more of a "set and forget" thing in that you simply set the value in your device profile and BOINC keeps enough work on hand to cover that amount of time.

It does seem that BOINC determines if you have enough WU based on the values in the "To completion" column. That's a reasonable estimate but appears to usually be an upper bound if it's off, so a day's worth of work may actually be more than you'll get with a value of 1 in the device profile. Of course, you also need to account for whether or not you normally have BOINC running all day too. Also, the "To completion" values for all "ready to run" WUs seem to alway be the same value. That is, it seems that the first one pick up the value of the running WU or the WU listed above it (not sure which) and then additional WUs downloaded in advance seem to pick up that value from the last WU listed. It seems if you go from a long running WU to several short ones, you could have less work than you want.

Still, I'm quite happy with this. I should pretty much be able to avoid any crunching downtime (as long as it's not my 'puter). I can easily eyeball things on occasion in case I run into a good string of long running WUs or very short running WU's and temporarily adjust the value in my device profile so as to avoid any impact to WCG or other crunchers.

This is false. The UD agent checkpoints and saves completed work just as the BOINC agent does, since it's the application that determines when to checkpoint. Except for specific API hooks for each agent, the application code is identical.

It's possible that the checkpoint/work files could have been corrupted during a sudden power loss, but this could occur with any application that has open files, including BOINC.