Tripredacus Posted March 29, 2010 Posted March 29, 2010 I've noticed that since yesterday, my screensaver hasn't turned on like it used to. Its set for Mystify and to turn on after 7 minutes of inactivity. I know exactly what was done since it worked and didn't:- installed dosbox- installed Warcraft II in dosbox (it doesn't work anyways)Since then, it does not come on. If I do the preview button on the Screen Saver window, it does come on, so I know its not a problem with that. Obviously there is something stopping it from running. I checked my processes and they appear normal, and my av is running fine and has not found anything. Any ideas how I can see what's keeping it from turning on?Oh uh Windows 7 Professional x86
cluberti Posted March 29, 2010 Posted March 29, 2010 Removal of the two additions bring it back? I'm not sure how DOSBox would cause anything (or installation of anything in DOSBox for that matter), but if you know what changes were made since it worked rolling them back would be a start. Anything that would hook DirectX and the display could cause it though if it keeps grabbing any portion of the display (it will reset the idle timer).
GrofLuigi Posted March 30, 2010 Posted March 30, 2010 Sounds very much like BlockSendInputResets.The value survived from Win2K through XP and Win2k3, so I think there's much hope it exist in 7 too.GL
cluberti Posted March 30, 2010 Posted March 30, 2010 That works around it (and it still exists in Vista and Win7), but it won't help you find the culprit causing the calls to reset the session lock timer. If all you want to do is remove the symptom, sure, but if you want to troubleshoot (there are ways to hook calls and catch them to see who's doing it) this wouldn't be recommended.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now