Update (2017-06-27): We release a patched version (1.5.4) that implements a couple other minor updates and changes.
We've finally released the next version of Screensaver Operations.
Screensaver Operations is an application for Microsoft Windows systems that allows you to perform configurable actions after a computer has been left idle for a specified amount of time (e.g., log off, shut down, run a process).
There are a lot of new bug fixes and a couple features in the latest release:
- Bug/Security Fixes
- Fixed issue where when enabling RunProcessEnabled, the default title and message texts were incorrect.
- [Window XP & Windows Server 2003 Only] When using the RunProcessEnabled flag, older versions of Windows (XP, 2003) close the process when the screensaver ends. This is due to multiple factors. Windows XP, etc. closes child processes along with the screensaver. It also puts the screensaver in a separate Virtual Desktop and kills all processes in that desktop when the screensaver ends! We have implemented a workaround and running a process in older versions of Windows should work. This issues took many days to fix so we are glad that we got it to work!
- Changed action button on process run to "Start Now" rather than "Start Process Now" (which was cut off as it only showed "Start Process").
- Opens "Configure" properly from right-click context menu on SCR file.
- Fixed some issues with double-quotes in process path or process argument.
- Fixed issue where sometimes the Keyboard Filter "DisableSpecialKeys" would crash the program when a special key (e.g., the Windows key) was pressed.
- New Features
- Added: BackgroundOpacity registry value - Setting allows you to modify background opacity from the default of 75%. Some organizations might want to completely hide content. Note that this setting is not yet available from the Configuration GUI and can only be set via registry and ADMX. (Note: In Windows 8 and newer, Windows always shows an opaque background color as a security feature)
- Added: A "Snow" Easter Egg. See the README for more information. :-)