I think it would be alot more reasonable if instead of setting how often BOINC connects to the internet (connect every X days), you could set it to connect whenever it finishes a work unit or is attached to a project or has no workunits in a specific project, and have a setting to limit how often it may connect in hours (dont connect more then once per X hours).

Maybe even make a differenciation by project. So it could be set to "dont connect more then once per X hours" with the choice of it being per project or per machine

You can already set fractional days. .1 day is 2.4 hours.

0 days will wait until there is no work on the computer before starting a DL.

I know, I explained that already. I said its better to measure in hours instead of days, where 24 hours is a day, instead of 0.1 of a day is 2.4 hours... makes it more reasonaable, and you would also notice I said change it from "connect this often" to "connect as soon as possible but no more then this often". Quite the difference there.

If you add the flag '-return_results_immediately' to the client on start up, it updates itself after every wu. This applies to the gui aswell as the cli ;-)

Dunc

thanks...

I still think it should be an option at the preferences, but this is better then nothing.

How do I format it? there is already a flag there -min

I presume it means to minimize. When I add the second flag, do I just add it afterwards? Do I need to put a space between them?

> thanks...
>
> I still think it should be an option at the preferences, but this is better
> then nothing.
>
> How do I format it? there is already a flag there -min
>
> I presume it means to minimize. When I add the second flag, do I just add it
> afterwards? Do I need to put a space between them?

There should be a space between the file name and the "-min" which should NOT have a space between the "-" and the "min" and this switch will cause BOINC to start up minimized to the Notification area of the taskbar.

if you put the two flags in, the second one is separated by one space from the first one.
<p>
For BOINC Documentation: Click Me!

like this?
E:\BOINC\boinc_gui.exe -min -return_results_immediately


Because it doesnt do it still...

> like this?
> E:BOINCboinc_gui.exe -min -return_results_immediately
>
>
> Because it doesnt do it still...

Hmmm, ok, maybe the GUI client ignores the switch. I know it works on my Macintosh ... but that is a command line client ... have you considered getting one?

:)


<p>
For BOINC Documentation: Click Me!

well, yes and no... I used to work with command line clients, I like it better when there is no GUI to waste system resources. BUT,

It is unacceptable that it has this DOS window constantly open... I just do too many things with my computer and it gets in the way, and I always end up accidently closing it.

I wonder if it ignores it since its the second switch, maybe the GUI can only deal with one?

> like this?
> E:BOINCboinc_gui.exe -min -return_results_immediately
>
>
> Because it doesnt do it still...
>
>

I use that switch, plus '-allow_remote_gui_rpc' with the Boinc_gui with no problem?

To avoid the Boinc_cli running in a dos window, install it as a service 'boinc_cli -install'

Dunc

adding that switch in addition to the other too caused boinc to instantly terminate upon activation. Removing it made it go back to normal, since it doesnt submit instantly, I just removed the other one aswell, and not it just has the switch -min with which it came.