Jump to content

AuScripter

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by AuScripter

  1. Hi, did you find a solution on that? I'm just sticking to Windows 10 1909 because 2004 and the following versions force modern standby and my AutoIT automation software is no longer able to wake up the computer. Regards, Achim
  2. In the meantime, I have read that it is probably a phenomenon of Windows tablets. So I searched in the wrong place. Not AutoIT is the problem, but the hardware.
  3. An alternative idea: Maybe I could also set the screen brightness to 0. Is that possible with Autoit? With Windows on-board means this does not work with the surface under Windows 10. Minimum brightness setting here is 25%.
  4. No. For mains operation all options are set to "Never"
  5. Tried it. The same result: 2019-01-11 15:51:57 : Start script 2019-01-11 15:52:02 : Monitor off 2019-01-11 15:52:02 : Main loop 2019-01-11 15:52:07 : Main loop 2019-01-11 15:52:12 : Main loop 2019-01-11 15:55:33 : Main loop 2019-01-11 15:55:38 : Main loop 2019-01-11 15:55:43 : Main loop 2019-01-11 15:55:48 : Main loop 2019-01-11 15:55:53 : Main loop 2019-01-11 15:55:58 : Main loop 2019-01-11 15:56:03 : Main loop 2019-01-11 15:56:08 : Quit script The loop stops after three passes (red) and will not resume until the computer is re-activated with the mouse (green).
  6. Strange! The script seems to continue without Sleep. I would not have gotten that idea at all. But what can I use as an alternative? The original script does a lot more in the main loop and Sleep is used in different places.
  7. Which Sleep command do you mean? The one within the main loop? No, I didn't try this. Would not that result in too much load on the System?
  8. The idea is to turn the monitor off when the script is idle (main loop). The plan is to activate the monitor only during the activities. Unfortunately, the script stops and misses the time of the next activity.
  9. Hi, I'm trying to create a script that runs in the background while turning off the monitor. Unfortunately, the script execution stops when the monitor is off. I wish, however, that the script will continue. This is an example of my implementation: #include <File.au3> Global Const $lciWM_SYSCommand = 274 Global Const $lciSC_MonitorPower = 61808 Global Const $lciPower_Off = 2 Global Const $lciPower_On = -1 Global $LogFileName = @ScriptDir & "\MonitorOffTest.log" HotKeySet("^q", "QuitScript") WriteLog("Start script") Sleep(5000) _Monitor(0) WriteLog("Monitor off") $Run = True While $Run WriteLog("Main loop") Sleep(5000) WEnd Func WriteLog($logtext) Local $hFile = FileOpen($LogFileName, 1) _FileWriteLog($hFile, $logtext) FileClose($hFile) EndFunc Func _Monitor($run = 1) Local $Progman_hwnd = WinGetHandle('[CLASS:Progman]') If $run = 0 Then ; BlockInput(1) DllCall('user32.dll', 'int', 'SendMessage', _ 'hwnd', $Progman_hwnd, _ 'int', $lciWM_SYSCommand, _ 'int', $lciSC_MonitorPower, _ 'int', $lciPower_Off) Return 1 ElseIf $run = 1 Then ; BlockInput(0) DllCall('user32.dll', 'int', 'SendMessage', _ 'hwnd', $Progman_hwnd, _ 'int', $lciWM_SYSCommand, _ 'int', $lciSC_MonitorPower, _ 'int', $lciPower_On) Return 1 EndIf Return 0 EndFunc Func QuitScript() WriteLog("Quit script") $Run = False EndFunc It creates log entries as follows: 2019-01-11 14:00:58 : Start script 2019-01-11 14:01:03 : Monitor off 2019-01-11 14:01:03 : Main loop 2019-01-11 14:06:24 : Main loop 2019-01-11 14:06:29 : Main loop 2019-01-11 14:06:32 : Quit script As you can see, nothing is logged when the monitor is off. After moving the mouse, it is running again. Who has a hint for me how to make sure that the monitor is off, but the script and all other processes on the computer are still running? Btw: The computer I'm testing with is a Surface 3
×
×
  • Create New...