Then he'd offer you some refreshing recycled sewer waterIf Bill Gates would weigh in, he probably could give a suggestion how to immediately turn the screen BLUE.
Then he'd offer you some refreshing recycled sewer waterIf Bill Gates would weigh in, he probably could give a suggestion how to immediately turn the screen BLUE.
LOl definitely.If Bill Gates would weigh in, he probably could give a suggestion how to immediately turn the screen BLUE.
I have an SP2 (no dock) with two external daisy-chained monitors. My screen saver is Blank and as you stated, the display is still on, just blank. As a result, my first external monitor doesn't go into sleep/energy-saver mode; this effect is then cascaded to the second monitor.Tried the screen saver hack, and although its responsive & easy to execute, it doesn't really turn the screen 'off'. It blanks the display, but it is still on, almost like a color bleed test.
Any way to actually turn the screen completely OFF?
You mean use the Metro(sexual)UI windows? nah, I think not. Im doing my best to completely exclude Metro from my day to day comings and goings. Just dont like it, not my cup o tea, cats meow, etc etc...Or they were creating a platform for modern computing moving beyond legacy computing. Move to Modern Apps and if properly coded it should work.
Well you will be wrestling with Connected Standby as Legacy Win32 Code is written for desktop class machines and ACPI power management.You mean use the Metro(sexual)UI windows? nah, I think not. Im doing my best to completely exclude Metro from my day to day comings and goings. Just dont like it, not my cup o tea, cats meow, etc etc...
That .exe appears to have been made for a dell laptop a while ago.
<says in dramatic, all-hope-is-lost deep voice> THEN.... SO BE IT....Well you will be wrestling with Connected Standby as Legacy Win32 Code is written for desktop class machines and ACPI power management.
That may be true or maybe not. I don't know why, 'it is what it is', but probably it's like there were 200 power management changes but only time for 100 of them, maybe next time. Maybe it was a hardware issue, power management chip limitation, whatever. The verbiage is a clue that it's not likely to change soon or in the SP3 despite all the Monday quarterbacks derisions.I think the reality is that you have to give up the notion of using CS as a function of legacy Windows. There are many areas where the two are not compatible and power management is one of them. If you cannot/do not want to move to the new ecosystem, you can disable CS and use SP3 as a regular Windows device. You will then be able to turn off power to the monitor without having the machine go to sleep. But you can't do this and keep CS at the same time. You'll just have to choose which is more important to you.