Search the Community
Showing results for tags 'Not responding'.
-
I tried to tackle this about a year ago and gave up.. I write many autoit apps and they all seems to have a similar issue on windows 7. While running, they are always in the 'not responding' status with windows, and now our disk encryption software is popping in and killing my apps due to not responding.. From what I have read, I have to 'Pump the windows message queue' with messages, but I haven't the slightest idea how to do this in autoit. If anyone has a solution or a though, I would be eternally grateful! Here is my demo code: #include <ButtonConstants.au3> #include <EditConstants.au3> #include <GUIConstantsEx.au3> #include <WindowsConstants.au3> #include <MsgBoxConstants.au3> $Form1 = GUICreate("Crash Test Dummy", 314, 123, 192, 114) GUICtrlCreateGroup("Crash test", 8, 8, 289, 89) $Button1 = GUICtrlCreateButton("Do Something", 24, 24, 75, 25) $Input1 = GUICtrlCreateInput("", 24, 64, 257, 21) GUISetState(@SW_SHOW) Msgbox($MB_SYSTEMMODAL,"hey there","Open Task manager, the parent app is 'Running' but the moment you close this box, it will start counting and go to 'Not Responding', even if you click Do Something.") GUISetState(@SW_ENABLE, $Form1) While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit Case $Button1 guictrlsetdata($input1, "0") for $i = 1 to 201 guictrlsetdata($input1, $i) $i+=1 sleep(100) next sleep(500) guictrlsetdata($input1, "0") EndSwitch WEnd Any thoughts / idea are welcome!!
-
I created a few applications in autoit to help with deploying new laptops to our company. Just recently, on several of our laptops, while Autoit is running an install using RunWait, windows will dim the autoit application i made and report that it is not responding, even though the application is still installing. Relevant part of the script: Global $LocAdobe = "\\MyShare\Installer\!Win7Profiler!\Supporting_Files\Adobe Acrobat 10 Pro Win7 only\setup.exe" ; somewhere far down the script... GUICtrlSetData($Label1, "Installing Adobe X Pro") GUICtrlSetFont($Label1, 35, 800, 0, "Arial Narrow") GUICtrlSetColor($Label1, 0x000000) GUICtrlSetBkColor($Label1, 0xFFFF00) RunWait($LocAdobe) GUICtrlSetData($Label1, "Complete") GUICtrlSetFont($Label1, 12, 800, 0, "Arial Narrow") GUICtrlSetColor($Label1, 0x000000) GUICtrlSetBkColor($Label1, 0x00FF00) Also note this happens at random with different installers. what is Windows seeing that it thinks the script is no longer responding?