Yes, of course you're right I dont have BOINC installed as a service. I assumed it was a service, because of the way the 'To completion' time still increases after BOINC is suspended or I am 'active'. I installed 6.4.5 over 6.4.2 and just followed the default settings all the way through the install. I didn't really pay any attention to where or how BOINC was being installed.
So, the only way I have to stop the 'to completion' time increasing while I may want to do other things with the PC is to manually 'Exit' BOINC and tick the 'Stop running science applications...' box when doing so. Or perhaps there could be some other explanation for my problem. Might this perhaps be a bug with 6.4.5.?[/Edit]
It seems to be a bug, yes. Setting it to "suspended" from BOINC Manager "Activity" menu always works. Detecting user activity works fine installed as a service since they added boinctray.exe. If the time to completion changes at all while it should be suspended, it must be some other problem. Do the workunits still say "Running" when they do that?
[another-edit] The reason I've not gone back to an older version of BOINC, is that 6.4.5 is the recommended version for GPUgrid[/another-edit]
Yes, you
need 6.4.x to work with GPU apps.
Ok I just spent 20 mins composing a reply to this thread and it got lost in space!!. Second, and much shorter, attempt...
Just to put everything together into one post.
I'm running BOINC 6.4.5 on WIN XP Pro (SP3) 32-bit and a Q9450 quad.
BOINC is not installed as a servive. i just assumed that it was because of the way it behaved when I tried to suspend.
When I 'suspend' from the 'activity' menu in the BOINC manager, the symptoms are:
CPU time - stops
Progress bar/percentage - stops
Time to completions - increases @ 1 second/second (normal time)
WUs show as 'suspended'
Task manager show - 00 CPU is being used by WUs
When activity resumes, after clicking 'run always' the CPU time and Progress bar/percentage carry on from where it was suspended, but because the time to completion has increased then the effective run-time of the WUs increases by the amount of time the WUs were 'suspended'.
they went back for 6.4.2 as reccomended since 6.4.5 is a big foulup..
Apart from this problem I've been quite happy with 6.4.5. The cc_config.xml has gone of to the developers. hopefully I can help sort out this problem. with some luck, it may do some good for future versions.
Thanks for the suggestions guys. I'm still trying other options to see if I can stop it doing this.
Mark