| View previous topic :: View next topic |
| Author |
Message |
dirkla
Joined: 17 Mar 2010 Posts: 3
|
Posted: Wed Mar 17, 2010 11:47 am Post subject: Keycommand To Turn Of Monitors Fails |
|
|
Hi,
I'm using this keycommand to turn off my monitors:
^1::
Sleep, 200
SendMessage,0x112,0xF170,2,,Program Manager
return
It works, but only for a few seconds. After a few seconds the monitors are switched on again.
Any ideas why this is? |
|
| Back to top |
|
 |
HotKeyIt
Joined: 18 Jun 2008 Posts: 4652 Location: AHK Forum
|
|
| Back to top |
|
 |
maxgohan
Joined: 09 Oct 2009 Posts: 81
|
Posted: Wed Mar 17, 2010 2:12 pm Post subject: |
|
|
try using a longer sleep,
i have it set at 500
| Quote: |
F12::
Sleep 500
SendMessage 0x112, 0xF170, 2,,Program Manager
return
|
|
|
| Back to top |
|
 |
Chicken Pie 4 Tea
Joined: 18 Aug 2009 Posts: 375 Location: holland
|
Posted: Wed Mar 17, 2010 3:04 pm Post subject: Re: Keycommand To Turn Of Monitors Fails |
|
|
| dirkla wrote: | Hi,
I'm using this keycommand to turn off my monitors:
^1::
Sleep, 200
SendMessage,0x112,0xF170,2,,Program Manager
return
It works, but only for a few seconds. After a few seconds the monitors are switched on again.
Any ideas why this is? |
your lucky because your script and the one below do nothing on my computer not even a flicker! _________________ "Choose your parents wisely" |
|
| Back to top |
|
 |
dirkla
Joined: 17 Mar 2010 Posts: 3
|
Posted: Thu Mar 18, 2010 8:28 am Post subject: |
|
|
Higher values for sleep don't make a difference.
Any idea how to find out which application triggers the pc to turn on the monitors again? |
|
| Back to top |
|
 |
HotKeyIt
Joined: 18 Jun 2008 Posts: 4652 Location: AHK Forum
|
|
| Back to top |
|
 |
dirkla
Joined: 17 Mar 2010 Posts: 3
|
Posted: Thu Mar 18, 2010 9:01 am Post subject: |
|
|
| No, I'm using W7 64 bit. |
|
| Back to top |
|
 |
Guest
|
Posted: Thu Mar 18, 2010 9:14 am Post subject: |
|
|
| HotKeyIt wrote: | | If you are not pressing a key or moving mouse then there is an application that possibly does this. | That is very likely the answer. Why not try starting windows with the absolute minimum programs and see if the monitor will stay off. Then you can start adding programs until you find the culprit |
|
| Back to top |
|
 |
|