45
« on: April 01, 2011, 07:29 PM »
It is on a Vista Home Premium laptop, so no monitor light to see.
The 500ms in the code is interesting...the cycle time I saw could have been 1/2 sec for either on or off instead of 1-1/2 total as I said. I didn't measure it--just estimating. On and off time 'seemed' about equal, but that is not measured.
If you don't hear about it from anyone else, it may not be Tclock, or it may be some odd interaction with something on my machine and not others.
I will do as you request-- try in a week (assuming I remember to turn it back on in a week!). However, I don't think it started right when I set the option (I don't think...but frankly, I don't remember when I set that). Big help I am.
So, we shall experiment.
I don't read code much and certainly not C++; where is that WTS_SESSION_LOCK message (bit?) set, and what clears it? Could it still be true when unlock happens? But never mind--I was not consciously doing anything to cause the unlock (certainly not entering the password--it was not asked-for). That a clue? Wait! It actually was not locking, because it came back to logged-in screen, not to login password screen as would be normal if it really had locked. It was only screen off on, not lock-unlock.