compiled script stops working windows 10
Posted: 08 May 2021, 04:34
I've used AHK since about 2005 and found it 100% reliable at work across many thousands of workstations and obviously my own. Now I get a compiled script unresponsive on some clients. I think this is a probably Windows 10 problem, I have clients that run for months that still work. The problem ones mostly seem to be interactive workstations.
How should I look at trying to debug and resolve this?
It doesn't happen if the script is running with interpreter whether it be one script or multiple that I tend to use when adding a new function to my core scripts.
My scripts are fairly simple low cpu usage doing things like inserting text into hotkeys or scanning documents when pressing F9 and replacing text with company standard
e.g. "Acme Corp. Worldwide (2021)" from "AcMe corp USA" or "AcmE crop PRC" etc
What I'm currently doing as a fix is using a powershell script run by the scheduler to test a function in the ahk script and if it fails it kills and re spawns the ahk script and that works ok, but is klunky.
How do I resolve this?
How should I look at trying to debug and resolve this?
It doesn't happen if the script is running with interpreter whether it be one script or multiple that I tend to use when adding a new function to my core scripts.
My scripts are fairly simple low cpu usage doing things like inserting text into hotkeys or scanning documents when pressing F9 and replacing text with company standard
e.g. "Acme Corp. Worldwide (2021)" from "AcMe corp USA" or "AcmE crop PRC" etc
What I'm currently doing as a fix is using a powershell script run by the scheduler to test a function in the ahk script and if it fails it kills and re spawns the ahk script and that works ok, but is klunky.
How do I resolve this?