I would appreciate advice or help:

Just upgraded to v7.16.5.
Now BOINC Manager is giving me a Notice that seems to be a new "behavior" for this new release (at least to me).

The Notice says:

"Amicable Numbers: Notice from BOINC
Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
4/11/2020 9:03:37 AM"

The Event Log shows several red colored messages (one per project), in respect to the above cited Notice:

"4/11/2020 9:03:37 AM | Amicable Numbers | Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site."

How can I suppress these "annoying" messages?
YES, I have searched through docs and forums, but couldn't find an answer.

Thanks and stay virus free ...

S-F-V

What did you upgrade from? I think this behaviour has existed for several versions now.

You can't turn off the Event Log lines, or prevent the Notices being generated. But if you find them annoying, you can turn off the reminders:

In BOINC Manager, either Simple or Advanced view, go to the 'Options' menu and choose 'other options'. In the first tab, there's a drop-down list for 'Notice reminder interval'. Set that to 'never', and it'll shut up.

I upgraded from v7.14.2

Setting to "never" turns everything off - or am I wrong with this assumption?.

I just find it very irritating to see the tab saying Notices(1) - that forces me to check the Notice -- just to see this certain special reminder about no CPU.
Strangely, I only get one notice (in this case from amicable), but for the other projects there is no notice.
One could say: either a notice for all or for none.
But looking into Event Log I see the RED colored warning for all the other projects where I also have set no cpu.
The amicable project is the first project that appears in the event log.

Maybe I am understanding something wrong?

Thanks for your response.

EDIT:
Just tried setting notices to "never".
Re-booted PC and again received an new Notice(1) message (checked time stamp).
So, what is the "never" option good for, if does not work?

I upgraded from v7.14.2

Setting to "never" turns everything off - or am I wrong with this assumption?.

I just find it very irritating to see the tab saying Notices(1) - that forces me to check the Notice -- just to see this certain special reminder about no CPU.
Strangely, I only get one notice (in this case from amicable), but for the other projects there is no notice.
One could say: either a notice for all or for none.
But looking into Event Log I see the RED colored warning for all the other projects where I also have set no cpu.
The amicable project is the first project that appears in the event log.

Maybe I am understanding something wrong?

Thanks for your response.

EDIT:
Just tried setting notices to "never".
Re-booted PC and again received an new Notice(1) message (checked time stamp).
So, what is the "never" option good for, if does not work?

The settings are not (as far as I can tell) retrospective, therefore you will still see the notice that you received before you changed the flag but never get another.

...
Re-booted PC and again received an new Notice(1) message (checked time stamp).
....

The settings are not (as far as I can tell) retrospective, therefore you will still see the notice that you received before you changed the flag but never get another.

As I said, I checked the timestamp. The time stamp changes and is always a new/changed one.
Just retried it.
Also if it were the old notice the number "one" in parenthesis behind the Tab-name would not show up again..

The second question was "why just a notice for the one project"?
And the first question was "does never mean NO notices at all"?

I hate to say it, but there are notices that are important or interesting, so I really don't want to turn it completely off.

Have a nice day ...

The Notices also show messages from the Messages log. Because not everyone knows that there is a messages log (the Event Log), where sometimes messages show that are urgent enough that the user needs to know about them, these are copied into the Notifications tab. Perhaps you set long ago that the project should only use CPU and in the mean time it has developed GPU apps, you may want to know about that when you renew your attachment to it. On some projects they did away with the GPU apps, so you may want to know about that when your preferences are set to use GPU only.

So the message about not fetching work for CPU is a service to the user. If that's annoying you, well, run BOINC with just the client and not the manager, or use BOINCTasks as an alternative manager.

---

Well spoken ...
Of course you are right - using this type of argumentation, one could think of many things that could be put on the notice tab as a service to the user.
Let me tell you, I knew/know about this situation.

Still does not explain why just the one project is forwarded to the notice tab board.

And why repeatedly, I mean a one time notice would be fine.

And saying "run BOINC with just the client and not the manager, or use ..." is very helpful - I would never have thought of that.

Sorry to even have asked for help.
Just ignore my post.

Since the question has come up, I've looked at the notices on this machine (I rarely do - I look at the Event Log much more often). I find three at the top:

SETI@home: Notice from BOINC
Your settings do not allow fetching tasks for Intel GPU. To fix this, you can change Project Preferences on the project's web site.
05/04/2020 18:48:38

--------------------------------------------------------------------------------
Einstein@Home: Notice from BOINC
Your settings do not allow fetching tasks for NVIDIA GPU. To fix this, you can change Project Preferences on the project's web site.
05/04/2020 18:48:38

--------------------------------------------------------------------------------
Asteroids@home: Notice from BOINC
Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05/04/2020 18:48:38

So, it's not just one project - it's every project where I've set an active "Don't fetch for ..." preference.

Note that the timestamps are identical: they correspond (to within 2 seconds) with the last time I started BOINC on this computer.

And why repeatedly, I mean a one time notice would be fine.

It's done every time you restart the client. At project detection you're getting that message. If it's for one project only while you have multiple projects that you have the message for, that's probably a bug.

It probably is a bug as I see it for one project only as well, and I have four projects yelling at me in the startup messages. So I will put that one forward as a bug to Github Issues - and with thanks for letting us know.

And saying "run BOINC with just the client and not the manager, or use ..." is very helpful - I would never have thought of that.

You sounded aggravated and like you were having a go at Richard, who is a volunteer helper just like about everyone here on the forums, present company included. Perhaps you didn't know how BOINC/BOINC Manager worked.

---

For the record, and since you've escalated it as a bug:

The particular machine that exhibited three notices is

05-Apr-2020 18:48:36 [---] Starting BOINC client version 7.16.3 for windows_x86_64

It has 12 projects attached, though few of them are currently active. I'll check for other warnings in the startup log, to see if any others were active but failed to generate a notice.

The full set is:

05-Apr-2020 18:48:38 [Albert@Home] Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [Albert@Home] Your settings do not allow fetching tasks for Intel GPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [Asteroids@home] Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [Einstein@Home] Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [Einstein@Home] Your settings do not allow fetching tasks for NVIDIA GPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [GPUGRID] Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [Milkyway@Home] Your settings do not allow fetching tasks for NVIDIA GPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [NumberFields@home] Your settings do not allow fetching tasks for NVIDIA GPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [SETI@home] Your settings do not allow fetching tasks for CPU. To fix this, you can change Project Preferences on the project's web site.
05-Apr-2020 18:48:38 [SETI@home] Your settings do not allow fetching tasks for Intel GPU. To fix this, you can change Project Preferences on the project's web site.

So that's seven projects, ten warnings, but only three notices.

It may be significant, or maybe not. I got just one notice for each device type (CPU, NVidia, Intel_GPU) in that order, although multiple projects were 'prefer not' for each device.

Another datum:

25-Oct-2019 19:11:00 [---] Version change (7.13.0 -> 7.16.3)

Prior to that change, there were no warnings about non-fetchable device/project combinations in the event log.

I have the feeling it's to do with the alphabetical order of the project URLs and that something breaks there.
Now, where did you find the actual notification messages? Because my BOINC Data directory seems to have misplaced them.

---

The notices themselves, I copied from the BOINC Manager display on the Notices tab. (These internally generated notices don't seem to be stored in the data directory, only the news items sent by projects)

I've also linked the guilty commit on your #3590.

With a number of "boinc rigs" I got tired of having to scroll through 1000's of annoying message just to find that the ones I wanted to see had already been purged off the 2000 limit that boinc tasks has.

FWIW, I added a message filtering capability to cc_config

<exclude_proj_msg>       <!-- put this in the flags section, not the options section -->
<proj_name></proj_name>  <!-- project name with correct syntax are isted in event messages -->
<msg_type>low</msg_type>
<msg_content></msg_content>  <!-- if enmpty, all are excluded -->
</exclude_proj_msg>

the message that were particularly annoying

<msg_content>settings do not allow fetching tasks</msg_content>
<msg_content>No work available</msg_content>
<msg_content>No work sent</msg_content>
<msg_content>No work is available</msg_content>
<msg_content>Resent lost</msg_content>
<msg_content>resend lost</msg_content>
<msg_content>already reported</msg_content>

Unfortunately, it only works with my app
https://github.com/JStateson/MSboinc

In BOINC Manager, either Simple or Advanced view, go to the 'Options' menu and choose 'other options'. In the first tab, there's a drop-down list for 'Notice reminder interval'. Set that to 'never', and it'll shut up.

By the way, this only stops the notification balloons from popping up, it doesn't stop the notifications in BOINC Manager's Notification tab.

---

I did say that in the line above the one you quoted!

You said it turns off the reminders, which doesn't specify if it's in BOINC Manager or in Windows. Each time you restart BOINC (Manager), the Notification tab will show 1 new notification, which is a reminder of sorts as well. But it doesn't stop these, only the ones from the Windows system tray.

...You sounded aggravated and like you were having a go at Richard, who is a volunteer helper just like about everyone here on the forums, present company included. Perhaps you didn't know how BOINC/BOINC Manager worked.

@Jord:

Sorry if I hurt your or anybody elses feelings.
If you read it right, I am not going or did not go at anyone -- at least not intentionally.
Of course I appreciate every help - even if it does not.
I think I know halfway how the manager works (I know, I know, everybody says that).
AND I konw that IT IS now working differently than it did with V7.14.2
AND that bugs me - it is costing me a lot of time for all my rigs --> (this is not a rant - it is just "unimportant" facts)!

@everyone else:

I just changed all profiles/preferences on all relevant (the ones mentioned in my event log) projects to use
CPU and GPU ---- then stopped BOINC, rebooted PC ...
AND guess what, the messages still appear.

I can't find any docs on this "new" behaviour either.

So, thank you all for chiming in on my very unimportant problem ... I APPRECIATE YOUR HELP VERY MUCH !!

AND please remember, my mother tongue/language is not English, perhaps YOU can speak or articulate yourself better
in a foreign language than I can.

Have you all a nice day and stay away from the virus ...

Thanks for coming back and trying to explain.

Just a suggestion: you say you have "changed all profiles/preferences on all relevant projects". That's the first step. What you have to do next is to ensure that your own copy of BOINC contacts all of those projects, so that the new preferences are transferred from the project servers to your machine. You can use the 'Update' button on the Projects tab in BOINC Manager to do that.

If you could complete all those updates, and then restart BOINC, I think you should find that all the messages and notices go away - it would be helpful if you could test that out.

In the meantime, have a look at Virtualbox 6.1.4 Not Utilized by BOINC 7.14.2x64 on Windows 10 Pro. That guy (running the older v7.14.2 without the annoying notices) had precisely the opposite problem - he wanted to use a resource - his new VM - and couldn't work out why it wasn't happening. I don't think the new messages would have helped in that case - VMs are not treated in the same way as GPUs - but it's an indication that there's a balance to be struck somewhere.