The installer is designed to shut down the BOINC client - the bit that runs silently in the background - by itself. If it's running when the installer starts, you should get a warning that it is going to need to do that, and give you the opportunity to cancel.

It doesn't matter to the Installer if BOIMC Manager, BOINC Tasks, or any other user interface is running - nothing the installer does matters to Manager-like tools. In fact, the plan was to leave the Manager running, but close the client and start it back afterwards. If anyone sees anything different to that, please describe with as much detail as you can.

The only change between 0.44 and 0.45 in this area is the detection or 32-bit and 64-bit OSes - I might have broken something there.

Well my slow but sure rise in RAC continues:



Just so you know it is this machine:

6851722

AuthenticAMD
AMD A8-3800 APU with Radeon(tm) HD Graphics [Family 18 Model 1 Stepping 0]
(4 processors)

NVIDIA GeForce GTX 970 (4095MB) driver: 368.22 OpenCL: 1.2

I run two tasks on the 970 and have two CPU cores free.

However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Just for a historical perspective during last years WOW event this machine peaked at 15,799 RAC, dipped to 3,899 on the 22nd Jan and has not gone higher than 11,458 since.

Before this upturn the lowest point was 6,459. current RAC is 8969

Lets hope it continues.

---

However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Are you running with the defaults or have to made use of -use sleep?

---

Grant
Darwin NT

I have noticed, that the 64 bit installer shows the warning about boinc running, even if it is not.

However it is also my daily machine and I am typing this on it. I watch streaming videos for several hours a day with no noticeable problems. I play games for around 4 hours per day and then Boinc is off.

Are you running with the defaults or have to made use of -use sleep?

Sorry, yes forgot to mention the "-use sleep" is the only command I currently use.

---

I have noticed, that the 64 bit installer shows the warning about boinc running, even if it is not.

Thanks, I'll go down and check that out now.

Edit: well, I've learned something new - but not what I expected.

At my first test attempt, I didn't get the warning at all, whether BOINC was running or not. Then I remembered that I had set that machine up to 'allow_multiple_clients': with that disabled, detection behaved as planned (warned that BOINC was running if it was, didn't warn if it wasn't). And having looked at the code, I can see why it might not work with multiple clients allowed - even if only one is running. The installer makes no attempt to enumerate and stop multiple clients - if you use that (somewhat obscure) facility, take care with the installer.

My test was with a 64-bit copy of Windows 7: could you describe the system you see this false detection on, please?

And please can you use a third-party tool, like Task Manager or Process Explorer, to check that BOINC is really stopped when you think it is? You would normally expect to see three BOINC components listed when it is fully up and running:

boinc.exe
boincmgr.exe
boinctray.exe

It's only the first one of those that we're testing: boincmgr and boinctray can stay running, as far as the installer is concerned. Let us know what you see in both 'running' and 'stopped' states.

Of the three wu's I'm working on 2 are having trouble(I'm trying 0.45 again with 0.5/0.1 as suggested), the time left does not shrink at all, processing slows to a crawl, when I stop boinc, all 4 of the cpu wu's and 1 of 3 gpu's stop, the other 2 gpu wu's stay in Memory and continue, plus the cpu% keep dropping.

I have the cmdline set for: -use_sleep -instance_per_device 3
I've also had the cmdline set for 2 also, makes no difference.

Here's two screen grabs, note the time left, on 2 they don't change...

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

My test was with a 64-bit copy of Windows 7: could you describe the system you see this false detection on, please?

I redid it with no boinc(related) processes running---fine, no warning.
With just boinc.exe running---warning---correct..

I have another machine running boinc( older version), which i have not considered.
That appears to be fine.
I can log onto it, if necessary, but the link is bad, and i rarely connect to it.

That's OK - I think we can put it down to a random failure to shut down boinc.exe, without spending too much time on it. But now you've alerted everyone who reads this thread to the possibility, I'm sure other people will have tested as well (and they know what to look out for).

If anyone reproduces the problem (consistently), we can follow it up then.

Thanks for looking into it.
I am 90% certain, that boinc was fully shut down, but there are still these 10%...

With the use of -use_sleep the percentage of CPU usage should continue to drop as the work continues to be processed.

The failure of time left to change, might be an issue with the way the program works. Somewhere I seem to remember comments about the non-linear countdown of work units. I don't know if that is what is happening but might explain it.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Are you using an up to date version of BOINCtasks? Just trying to figure out what is happening.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Correct.
There is a menu item to stop the client.
If you just exit "BoincTasks", the client remains running.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Correct.
There is a menu item to stop the client.
If you just exit "BoincTasks", the client remains running.

Both BOINC Manager and BoincTasks have that behaviour, but in both cases, they either stop boinc.exe (and all tasks should stop with it), or they leave everything running.

Vic wrote:

all 4 of the cpu wu's and 1 of 3 gpu's stop, the other 2 gpu wu's stay in Memory and continue

That shouldn't happen with either Manager. It sounds more like the applications themselves failing to notice that BOINC wasn't there any more - something we had problems with a few years ago.

With the use of -use_sleep the percentage of CPU usage should continue to drop as the work continues to be processed.

The failure of time left to change, might be an issue with the way the program works. Somewhere I seem to remember comments about the non-linear countdown of work units. I don't know if that is what is happening but might explain it.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Are you using an up to date version of BOINCtasks? Just trying to figure out what is happening.

I'm using 1.69 which is the latest BoincTasks and BT is set to have all work stop when Boinc exits.
Note: When Boinc was set to go to sleep as scheduled, all work ceased at the appointed time.

At the time of this post I was using Boinc v7.6.22, now I'm using v7.6.33, during the upgrade Boinc shut down, but 2 gpu wu's kept going, even after I put boinc to sleep, so I ended the programs, then restarted Boinc, then the 2 had lost ground and would now go to sleep.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Zoom,

Just a thought.

Do you run ccleaner after your installs?

Sometimes things get left in the registry after updating and that can cause issues.

Just like what we do with clean install of drivers.

Might be worth a shot.

https://www.piriform.com/ccleaner/download


Zalster

Zoom,

Just a thought.

Do you run ccleaner after your installs?

Sometimes things get left in the registry after updating and that can cause issues.

Just like what we do with clean install of drivers.

Might be worth a shot.

https://www.piriform.com/ccleaner/download


Zalster

No.

What Richard Haslegrove said sounds plausible.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

With the use of -use_sleep the percentage of CPU usage should continue to drop as the work continues to be processed.

The failure of time left to change, might be an issue with the way the program works. Somewhere I seem to remember comments about the non-linear countdown of work units. I don't know if that is what is happening but might explain it.

As to why the work units continue to crunch after you have exited? I think someone had commented that with BOINCtasks, there was a command that needed to be checked to stop all work when exiting. Failing that, I think I remember something like that happening a while back.

Are you using an up to date version of BOINCtasks? Just trying to figure out what is happening.

. . I get a pop up window when exiting BOINC client confirming to stop running tasks.

When 0.44 was installed, SoG went away, so did the 16 Sog wu's which were replaced with 18 guppis, the 16 were also guppis.

. . I think you made the same mistake I did, when "rolling back" from 0.45 running SoG I did an uninstall, this is why the downloaded "SoG" WUs went away, if I had done what I should have done and simply re-run the 0.45 install but selecting CUDA50 instead of SoG things would have been fine.

. . Another brilliant "D'oh!" moment.

Still getting 'waiting to run, now with 4000+ day run times...

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Set your cache to 1 day and just let it run.

You have changed apps so much BOINC has no idea what the average times should be.

It will run high priority until it sorts it out.