Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Retired Forums Forum: UD Windows Agent Support [Read Only] Thread: Screensaver disabled |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 6
|
Author |
|
loek
Cruncher The Netherlands Joined: Nov 17, 2004 Post Count: 5 Status: Offline Project Badges: |
When UD switched projects today. it disabled somehow my Windows XP screenlock. The timer had long expired, but the screensaver did not kick in. I had to select the screensaver again in "Display Properties" and press "apply" in order to get it working again.
----------------------------------------This is annoying when relying on a timer driven, password protected screenlock.
Loek - The Netherlands
|
||
|
BuckShot
Advanced Cruncher Joined: May 5, 2005 Post Count: 58 Status: Offline |
Hopefully one of the IBM techs will confirm this but I doubt that the downloading of a FAAH work unit changed the setting for the screen saver. It is possible I suppose but it did not happen on any of my machines and I have not heard of it elsewhere. Is it possible that something else changed?
---------------------------------------- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello loek,
This sounds like the sort of interaction that Viktors warned of: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=4591 Were you locked onto the screensaver that came with the Human Proteome Folding Project? Were you set to run in screensaver mode only? What utility are you using to lock screensavers? This is very interesting. We may run into this with each new project, but you are the very first to report it. Can you think of any details that I did not ask for? mycrofth |
||
|
loek
Cruncher The Netherlands Joined: Nov 17, 2004 Post Count: 5 Status: Offline Project Badges: |
I have a standard install of UD on this machine. UD was not set to run in screensaver mode only.
----------------------------------------As far as I know, I am using the standard WXP (pro) supplied method of running screensavers with password lock. During the switch from HPFP to FAAH the system was not in screensaver mode, I had UD opened and saw that HPFP was at 100% and could not connect to the server. By minimizing and opening UD again, the connection came up and a few minutes later FAAH was running. I left the machine alone, and over an hour later I noticed that the screenlock was not activated after 15 minutes.
Loek - The Netherlands
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks loek,
I will pass the word on this. We are interested in all problems that occur when we start a new project. mycrofth |
||
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: |
When UD switched projects today. it disabled somehow my Windows XP screenlock. The timer had long expired, but the screensaver did not kick in. I had to select the screensaver again in "Display Properties" and press "apply" in order to get it working again. This is annoying when relying on a timer driven, password protected screenlock. The only time the agent touches the screensaver settings is when you install/uninstall it. It's never touched after that. Simply downloading a workunit doesn't cause a change in the screensaver settings. My guess is something else caused the problem. Have you installed anything else? Windows updates? Graphics card driver updates? These are the two things that come to mind when some XP setting gets reset. Just a guess though.
Rick Alther
Former World Community Grid Developer |
||
|
|