|
Questions and Answers : Windows : BOINC Preferences not working correctly
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 7 Aug 04 Posts: 13 Credit: 125,384 RAC: 0 |
For whatever reason I have been unable to get my Preferences for home, work, school to take effect. I can get my general preferences to apply to my computers but when I make changes and then select which location my computers are at it does not affect they way my BOINC client runs. I can see they are not taking effect because i set my school preferences to use 2 processors and my work preferences to use only 1. Either way I set this it does not apply when Updating. I am able to get it to do what I want by making changes in my BOINC general preferences then updating the client but this is not how it should work. |
![]() ![]() Send message Joined: 5 Aug 04 Posts: 426 Credit: 2,426,069 RAC: 0 |
There are some known bugs in the venue specific prefs. 1) Suspend type preferences do not work if any venue specific prefs are defined. 2) Venue is forgotten/ignored by the client. This one should be at least partially fixed in the next verstion of BOINC. 3) Venue is forgotten by the server. Reducing the number of CPUs will not take effect until the current workunits are completed (this may behave differently with 4.xx). Increasing the number of CPUs may take a few minutes after the update and/or a client restart. CCv4.xx has new logic for the cpu scheduler so I am not sure of the expected behavior. <br>John Keck BOINCing since 2002/12/08 |
![]() Send message Joined: 9 Aug 04 Posts: 1 Credit: 684,964 RAC: 0 |
The Venue stuff seems very flakey - I tried setting this up so rarely used PC's use all their processors etc - but it keeps forgetting it. > Reducing the number of CPUs will not take effect until the current workunits > are completed (this may behave differently with 4.xx). Increasing the number > of CPUs may take a few minutes after the update and/or a client restart. > CCv4.xx has new logic for the cpu scheduler so I am not sure of the expected > behavior. It appears to stop if you restart the client but not if you don't |
©2025 cpdn.org