> > I would rather not insist that users edit raw XML. I have entered this
> as a
> > feature request.
> >
>
> This feature is already in the BOINC core client (4.24, maybe earlier). I can
> not figure out how to access it thru BoincManager GUI, but it is accessable
> thru the 3rd party addon GUI 'BoincView'. I've tested it, and it works. The
> project/host you activate it on will run dry...
> Test it with BOINC v4.24 and BOINCView v1.0rc6
> It is 3rd from the right, in the row of buttons on the toolbar at the top.
>

Downloaded the 4.24 core client last night, with the intention of installing it on top of the 4.19 client on one of my machines, so as to not lose any of the workunits cached. Done this in the past and it has worked smoothly with each version change.
This type of installation is no longer possible, as the new 4.24 installer detects a previous Boinc installation and requires you to uninstall it. A phaseout/stop-sending-work/complete-current-cache option would come in real handy in this situation. It would allow a user to run his/her cache dry before upgrading the Boinc client.

Some users might be comfortable with workarounds such as editing xml files or running 3rd party add-ons, but... would everyone else? The feature discussed in this thread should be in the core client itself and the user be given direct access to it. It makes sense to not download work that you know will never get processed/returned.

> This type of installation is no longer possible, as the new 4.24 installer
> detects a previous Boinc installation and requires you to uninstall it.

Uninstalling 4.19 will not delete work in progress -- you can uninstall 4.19, install 4.24 and everything starts right back up.

It's a good idea to make a back-up of your existing work, just in case (even though you'd only lose one work unit per project).

---