0
votes

this is my first time on such a prestidigious site, so please welcome me by assisting me. I am doing independent development and am primarily a music designer. So that is why I may not sound like a real pro coder but nevertheless truly love creating my music through automative processes.

My present issue is this: Windows 8.1 Pro AutoHotkey 1.0.48.5 32bit (running as Admin)

Everytime I attempt to use the command 'RUN' with an .ahk target, I get the expected result except that the .ahk residing folder is opened by MS Explorer. I suspect that something like the fact that AutoHokey is an unsigned app, windows does not want it to run flawlessly. I am now trying a number of Administrative Tool Services disabling, but with no success yet.

RUN C\:XZN\Mecanisms\AnyAHK_script.ahk ;;or RUN AnyAHK_script.ahk, C\:XZN\Mecanisms ;;or RUN C\:XZN\Mecanisms\BactchfileLaunchingAboveScript.bat ;;or RUN AnyAHK_script.ahk, C\:XZN\Mecanisms

Would there be a workaround this at the OS settings level or another way to run/start an .ahk file?

I tried the 'Comspec' approach as well as running an .ahk from within a batchfile, but the .ahk always get intercepted whenever it contains a 'RUN' command requesting an .ahk target.

Thanks.

2
Try updating to the latest version of AHK first, here, and post a sample of your code if possible, especially the Run command.Sid
Yes I'll post some sample code of this issue in a couple of days and will report her about both my WIN764Pro and WIN81Pro new code behavior as both build will run uptodate AHK versions.Carl Poirier

2 Answers

1
votes

You are using outdated version of AutoHotkey which is more than 5 years old. Always use AutoHotkey and its documenatation from http://ahkscript.org/ (current uptodate version, new official website)! AutoHotkey and its documentation from autohotkey.com is outdated and you may have some problems using them!

1
votes

One thing to try if you only have this problem on win 8 is to Enable interaction with administrative programs http://www.autohotkey.com/board/topic/70449-enable-interaction-with-administrative-programs/

That script modifies the executable file's embedded manifest, then creates and installs a self-signed certificate and uses it to sign the file. The executable will not run on any other system, unless you install the certificate used to sign the file.

But lets see some script code that way we have something to test with and can better help you out...