![]() I am running Windows XP SP3, and I am not on a corporate network where any policies can have an effect. It seems like at some point Windows decides to "refresh" it's list of screensavers, obviously doesn't find mine as it's not in wondows\system32, and the promptly sets the screensaver to None. When I go to the Desktop properties - Screensaver it has misteriously been set to "None". Suddenly instead of the screensaver comming up only the Windows logon screen appears, as it would when one closes the screensaver with "On resume password protect" is ticked. ![]() I literally sat and watched my pc for 10 minutes, screensaver set on 1 minute: it comes up, I close it and wait. When I simply set the current screensaver file in the registry (HKEY_CURRENT_USER\Control Panel\Desktop CRNSAVE.EXE) to the path of my scr file in some arbitrary folder, it seems to work, and the screensaver comes up the first few times, but then the setting seems to disappear by itself. Where do I install the scr file? I cannot assume that the user has access to Windows\System32. I install the screensaver in code (C#.NET) by setting registry entries in HKEY_CURRENT_USER\Control Panel\Desktop: SCRNSAVE.EXE, ScreenSaveActive and ScreenSaverIsSecure. Just wanted to clarify the above so that no-one thinks "whoo, screensaver developer. This way I can completely "lock" the PC and limit a user to what my application allows him to do. I therefore install my app as a screensaver and insist on "On resume, password protect" being ticked. ![]() It is a security "PC locking" app and although I can trap keys to my heart's content, Windows does not allow one to block Ctrl Alt Delete. ![]() I have an app that runs as a screensaver purely to use it's facility to "block" Ctrl Alt Delete. I would just like to know if you ever got any more info regarding this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |