This post has been edited by Glenn9999: 16 November 2008 - 09:50 PM
Timed Shutdown Screen Saver Beta 1 Release
Posted 27 January 2008 - 12:51 PM
Posted 27 January 2008 - 02:58 PM
the problem comes in when Vista activates the screensaver, 15 minutes goes by and powers off the screen. The monitor detects no input on DVI and switches to VGA where it proceeds to attempt to burn the XP desktop into my 24" LCD monitor (please no one tell me LCD burn-in doesn't occur -I have a 19" LCD in my office with a sunflower desktop wallpaper permanently burnt into it that begs to differ) besides the terror of seeing a ghost XP desktop for the rest of this monitors life, i have to access the menu on the monitor to switch it back to DVI when i return to my desk.
If this program could be modified to start the blank screen screensaver after the interval specified, that would prevent the monitor from switching and let me use a screensaver on this machine again (im using 'blank screen' with a modified power profile at the moment)
Posted 29 January 2008 - 09:33 AM
After I posted this, I had the thought to set an option in it as to what to do (Standby, Hibernate, Log off, maybe even start the blank screen saver like you suggest - in addition to shutting down the computer). It should be easy enough to do once I get the chance to sit down and finish it up.
I'll just go ahead and post it to this thread when I get it to the point I'm happy with it.
Posted 29 January 2008 - 12:34 PM
My kids are constantly walking away from the computer and leaving it on all day long. This would be a great thing for me. If there is a link to download it from I would like to give it a try.
Posted 16 February 2008 - 08:33 AM
copy it into the Windows\System32 directory (if XP) or Windows\System (if 98/ME) to install.
This post has been edited by Glenn9999: 04 April 2008 - 12:25 AM
Posted 16 March 2008 - 06:19 PM
When I use the screensaver at the logon screen i.e. when there isn't anyone logged onto the computer, I get the error shown below.
These are the settings I use in the registry.
What do you think would cause this problem?
Posted 16 March 2008 - 07:47 PM
It would seem when no one is logged in (i.e. as a default screen saver), there is no assigned right for a running program to shut down the system. To shut down a system via software, you have to have the assigned rights as a user to be able to do it. The program assigns those rights before it shuts down. But since there is no user right to assign (i.e. no user to assign those rights to), you see the message you are seeing. See the Microsoft Page on this error for more details.
Does it work without problem if you were to set the action to black screen (just to clarify that I'm on the right track)?
(I'll look into fixing this for the next revision)
Posted 17 March 2008 - 05:10 PM
Thanks for looking into this for me. I really appreciate it.
This post has been edited by aceuk: 17 March 2008 - 05:16 PM
Posted 17 March 2008 - 06:29 PM
What I was asking was whether it worked for not if you set the "action" in the configuration to "Black Screen" instead of "Shutdown"...
Hopefully I can look into this and a couple of other things very soon.
Posted 19 March 2008 - 12:51 AM
I'm not sure I understand. The idea is more for to do something with the system so the power requirements will be eliminated/reduced if it is left for a certain period of time unattended. I know many people/places where the computer tends to be left on - the screen saver is an ideal enough solution to do whatever it is. I started out with shutdown, and moved to all the other options.
As far as sending the monitor to standby, is that functionality already not in the Power Options? However, this program will send the whole system to standby in the time period if you were to set it. If there is a concern of the screen saver even running, I guess you could always set it to one minute - you would mainly see the countdown screen that aceuk posted.
(and yes I know the Black Screen option does not turn the monitor off, but as you saw in this thread, it was a requested feature)
Not a problem, thank you for checking into it. That confirmed the problem for me.
Posted 19 March 2008 - 07:02 AM
What I meant was the option of using standby rather than a screensaver as the first step (Set screensaver to run: Standby), then after the set time the system would perform the action selected by the user.
Posted 20 March 2008 - 01:15 AM
Thanks for looking into this for me. I really appreciate it.
It seems to me, unless I'm missing something (and I've been known to do that from time to time), that the screen saver would not be possible under WinLogon. The necessary permissions are not in the main super-user account (the NT kernel's version of Root in Linux - SYSTEM), which runs when the system is booted up. It seems I can't find a way to add those permissions, either (programmatically or through registry). The program could probably (again my guess) impersonate a logged on user to do it through the shutdown app, but it would need to prompt for a user account and (if necessary) password for that to happen - not sure that's too wise from a security standpoint.
I can understand the limitations, though, since it is the super-user account and would effectively bypass all authorizations and security if were possible to add privileges (the malware author's dream). But the odd thing about it is this: NT doesn't stop you from setting SCRNSAVE.EXE in this case to whatever you would like that would run. Perhaps the most ludicrous and silly/stupid thing you could do is set it to EXPLORER.EXE and get a fully working login session (with limits of course, most notable being the only thing you could do is "switch user". You can't log off, shutdown, restart the system, etc, etc. - it's effectively an account with no privileges beyond exactly what's required to run MSGINA).
Interesting stuff, anyhow...
Posted 22 March 2008 - 08:29 PM
No. the limitations I mentioned apply to all programs run under SYSTEM and not just the screen saver. I can especially confirm it by looking at the source and seeing that this program requires the same access permissions as mine does to perform a shutdown.
This post has been edited by Glenn9999: 22 March 2008 - 08:29 PM
Posted 22 March 2008 - 08:32 PM
I see what you mean, and I could do this. In fact, I already made a screensaver which has this function (turn off the monitor). Integrating it into the main app hopefully won't be too hard.
Posted 04 April 2008 - 12:33 AM
0.2: Fixed defaults for screen saver name for Windows ME - maybe other 9X systems?
0.2: Wrote check so screen saver will not run & warn of problems if someone tries to run it as a logon screen saver. Windows, as far as I'm aware from my testing, does not allow the application permissions necessary to do any of the configured actions beyond "log off" and "black screen". This makes it effectively useless in function under Win Logon.
0.2: Added option to turn off the monitor as a screen saver action.
This post has been edited by Glenn9999: 30 September 2008 - 06:18 PM
- ← Patched uxtheme but Vista .msstyles not showing up!
- Customizing Windows
- how can i change this letter as u see in the picture by using which dl →