4401
T-Clock / Re: T-Clock 2010 (download)
« Last post by Stoic Joker on April 02, 2011, 09:41 AM »It is on a Vista Home Premium laptop, so no monitor light to see.-movrshakr (April 01, 2011, 07:29 PM)
Crap ... Unfortunately that lends credence to my florescent light bulb theory (could be the power board at the base of the screen assy).
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.-movrshakr (April 01, 2011, 07:29 PM)
The half second pause allows the user time to let go of the buttons, so the triggered action isn't inadvertently canceled.
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.-movrshakr (April 01, 2011, 07:29 PM)
Just because nobody else noticed, doesn't (conclusively) mean that it ain't broken (See AMMA's post/discussion
)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.-movrshakr (April 01, 2011, 07:29 PM)
Thank you. The list of things I can't remember could fill a library ... *Shrug* ...It's part of being human.

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.-movrshakr (April 01, 2011, 07:29 PM)
The Clock registers itself with the system to receive Login Session Changes, and then responds to them by firing the monitor off code. And yes you are correct about the clue, the fact that no login was required is important.
Two things (tests) that could help the diagnosis, if/when the behavior reoccurs:
1. View the monitor while shining a flashlight (or other light source) on the screen at an angle to see if the desktop is still there but very faint. Usually have to get really close (8-10") and toggle something like the Start Menu to see it. This is typical behavior if the screen's back-light goes out.
2. Try connecting an external monitor (Might require mode switching the video output), to see if it gives you back the desktop.

Recent Posts


...Trust being a factor - In them - I have none.
?!? ...That hardly seems wise...