I've noticed recently that my Windows xp pro screensaver (Running Boinc 4.45) never comes on anymore, is not password protected and no Boinc activity runs.

I've tried using the regular windows control panel to modify the screensaver settings, which still shows Boinc, but it defaults to 60 minutes when I choose 5, and I choose password protect.

If I restart, or go back to the control panel, then it's reset back to 60 min, not password protected and the screensaver still never does run AT ALL.

I've also found that my Desktop group policy in the registry has gone missing and don't know if it's related to Boinc.

I know there are issues with password protection in previous releases, but nothing that ever un-did anything I tried to set. I don't care too much if I don't see graphics in order to keep my computer secure and password protected but it's another thing to not have my settings stick, AND to not have Boinc run when it's supposed to.

This is all very frustrating. I've since restored my registry desktop policy to set my screensaver timeout to 5 min as well as be secure. This prevents the current logged in user from changing these settings but I shouldn't have to do this.

Any help or insight would be appreciated. Thanks.

- Rob Sherman

---

Just a follow up. Since I modified the registry's policy for desktop to keep the screensaver timeout to 5 min and secured - it still won't launch the screensaver and nothing happens after 5 minutes. This problem is definately attributed to Boinc.

I've tried uninstalling and reinstalling and still nothing comes up at all and I am unable to modify any settings for the Boinc screensaver other then "go to blank screen" checkbox and the time to go blank. That seems to be the only setting that sticks.

I'm really ready to delete this thing permanently due to the problems I'm having. What a shame really, I've been a longtime user of the Seti@Home classic but what is the point if it won't run, won't display graphics (even if I remove password protect) and won't let me change the screensaver settings. This is worse then an in-law that won't leave after the holidays...

---

It may not be needed to fixed anymore when Boinc 5.2 comes along. Which is at latest around mid-October.

You can test the same things on Boinc 5.1.4
Boinc now uses the Major.1.x versions for testing, while Major.2.x versions are release versions.

If you want to test the same behaviour and be heard about, test version 5.1.4, since 4.45 will never be fixed again.

---

I've updated to the 5.1.4 and have exactly the same problems. In fact, I don't know if it's even Boinc related anymore. I've tried to switch to other screensavers, leaving the password protect off and it never comes on and always reverts back to 60 minutes of timeout. It also never comes on after 60 minutes either. Something is directly interferring with the screensaver and I don't have a clue what it is.

---

I've updated to the 5.1.4 and have exactly the same problems. In fact, I don't know if it's even Boinc related anymore. I've tried to switch to other screensavers, leaving the password protect off and it never comes on and always reverts back to 60 minutes of timeout. It also never comes on after 60 minutes either. Something is directly interferring with the screensaver and I don't have a clue what it is.

Rob, is this a workplace computer that may be joined to a Windows domain, or a home PC?

(j)
James

It's a home machine that was once on my own domain but have since reverted back to a plain old workgroup.

---

It's a home machine that was once on my own domain but have since reverted back to a plain old workgroup.

Hrm... One wonders if some old group policies didn't get tattooed onto your machine.

I'd try this: Create a new test user from scratch on the machine. See if the screensaver problem persists. If that fixes things, I have a possible solution that may work for you.

Also, can you scan your Documents and Settings folder for anything with the .MAN extension? Make sure you're scanning hidden and system files, and just search for *.man.

Other possible culprits I can think of are login scripts or computer management applications that periodically "update" or refresh their settings in your registry.

Just shout back and let me know if any of that made any difference. Thanks!

(j)
James