Issue with latest Ahk2Exe Edge with latest AHK binary file

[JnLlnd]

Hi,

I'm having issues trying to move to new version of the Akh2Exe compiler EDGE branch (I love directives) and to the latest AHK binary files.

With my old EDGE Ahk2Exe v1.1.11.01 and AHK BIN v1.1.22.07, I have no issue.

With the current EDGE Ahk2Exe v1.1.23.00 and AHK BIN v1.1.23 32-bit
Script compiles but the compiled exe gives the error "Script file could not be found" with the "My Document path\MyScriptName.ahk"




FYI, I tried to revert to my previous Ahk2Exe EDGE compiler v1.1.11.01 with the new BIN but I had another type of error:

With my old EDGE Ahk2Exe v1.1.11.01 and new AHK BIN v1.1.23 32-bit:
Compiler stops with copy of BIN renamed to the script to compile and freeze on "Changing version information" and after 10-20 seconds stops on an "Out of memory" error.




But, anyway, my goal is to make the latest EDGE compiler work with the latest AHK BIN. Any help would be appreciated.

Thanks,

Jean

[JnLlnd]

Additional info:
- I tested with an "Hello World" script, no directive, and I had the same issue (screenshot #1)
- but I found that the issue only occurs if I run the compiled file in another directory than the script directory.

[joedf]

I've compiled it. I tried a test "hello world" script. Seems to work.
Ahk2Exe-edge_v1.1.23.00.zip

[JnLlnd]

Yes it work now that I use your compiled script. Does the compiler need to run compiled?

I have another issue now with the binary file that I edited to change the class name to something other than AutoHotkeyGUI. I'll re-work on this. But is there a newer technique to change the class name of the compiled script?

Thanks for your help JoeDF.

[joedf]

So you're using this technique? https://autohotkey.com/board/topic/3388 ... entry52356
I personally don't know of another way. What is the reason for this, why change it?

[JnLlnd]

Yes I do.It worked well. But I must be missing something this time.

>What is the reason for this, why change it?

Just a preference. I change the class to make it easier to other AHK programmers to control my app's windows without having to worry about other scripts running having the same AutoHotkeyGUI class name or with window names that I find less reliable than classes to control windows.

Did you miss my first question: Does the compiler need to run compiled?

[joedf]

Did you miss my first question: Does the compiler need to run compiled?

Oh sorry. I don't think so. It must be some issues when using older ahk versions? I simply compiled it with Ahk2Exe from AHK v1.1.23.00

[lexikos]

No, the compiler does not need to run compiled. The Ahk2Exe.exe included in each release is compiled using the uncompiled version of that same script.

Script compiles but the compiled exe gives the error "Script file could not be found" with the "My Document path\MyScriptName.ahk"

This error message and the condition which it is for are specific to AutoHotkey.exe. The bin files do not contain the message or the code which shows it. If you are using v1.1.23 binary files, you must be using a copy of AutoHotkey*.exe, not the provided bin files.

[JnLlnd]

Hi Lexikos,

Doing additional tests, I found that this message appear only after I altered the class name in the binary file. With the original bin file, no issue. So, the technique described in https://autohotkey.com/board/topic/3388 ... entry52356 is not working anymore. I can live with it. Changing the class is not required for my app to work. But I would hope that, in a future version, this would become possible again.

And, BTW, I just want to say the I don't change the class name to hide that I'm developing with AHK. This is the contrary. I'm proud of developing with AHK and I make source file available on my site.

Thanks Lexikos, Fincs, JoeDF and all other developers on this project for making these wonderful tools available :-)

[JnLlnd]

Oh! Got it, Lexikos. I was not editing the proper binary file. I was editing the portable versions of the .exe files (renaming it .bin). My very bad... Using the .bin included in the AhkExe zip file (master branch), I can edit the class and everything works well with both the compiled and uncompiled "edge" version of AhkExe.

Sorry for having you lost your time on this. Issue closed :-)

[joedf]

ahhh ok, all makes sense now.

[gwarble]

I use this instead of a hex editor, thanks SKAN

Code: Select all

; AutoHotkeySC.bin String Patcher for AHK_L 32b Unicode             / by SKAN 16-Nov-2010.

PathToAHKSC := "exeorbin.exe"
     StrOld := "AutoHotkeyGUI"
     StrNew := "NewClass"

FileGetSize, Sz, %PathToAHKSC%
FileRead, Bin, *c %PathToAHKSC%

nLen   := StrLen( StrOld ) * 2
VarSetCapacity( StrRep, nLen, 0 )
StringLeft, StrRep, StrNew, %nLen%

If ( ( Off := InBuf( &Bin,Sz, &StrOld,nLen ) ) < 0 ) {
 MsgBox, 16, AutoHotkeySC.bin Patcher, String not found !? :: %StrOld%
 ExitApp
}

hFile := DllCall( "_lopen", AStr,PathToAHKSC, Int,0x2 )
DllCall( "_llseek", UInt,hFile, UInt,Off, Int,0 )
DllCall( "_lwrite", UInt,hFile, UInt,&StrRep, UInt,nLen )
DllCall( "_lclose", UInt,hFile )

Return ;                                                 // end of auto-execute section //


InBuf( hayP,hayS, neeP,neeS, sOff=0 ) {    ; slightly altered version of InBuf() by wOxxOm
 Static InBuf      ; Original version available @ www.autohotkey.com/forum/topic25925.html
 If ( ! VarSetCapacity( InBuf ))  {
     FiH =
     ( LTrim Join
       530CEC83E58955|5D8B9C57565251|C28E0F00FB8314|8B104D8B000000|41D929C1291845|8B000000
       B18E0F|0C758BC701087D|2A744BACFCC031|4B36744B2D744B|AD933F754B1474|008B850FAEF293|E
       BF4751F390000|7F75AEF2AD4E75|68EBF775FF4739|8A62EB7475AEF2|27386C75AEF226|AD669356E
       BF875|39665E75AEF293|434E47EBF7751F|C1DA89FC7589AD|E283F45D8902EB|87DF87F8558903|AE
       F2CA87FB87D1|F775FF47393775|03C783CA89FB89|85F44D8BFC758B|DE75A7F30474C9|0474C985F8
       4D8B|4FDF89D375A6F3|5F9D08452BF889|14C2C95B595A5E|F0EBD0F7C03100
     )
 VarSetCapacity( InBuf,224,0 )
 Loop, Parse, FiH, |
   NumPut( "0x" A_LoopField, InBuf,(7*(A_Index-1)), "Int64" )
 }
Return DllCall( &InBuf, UInt,hayP, UInt,neeP, UInt,hayS, UInt,neeS, UInt,sOff )
}

; "AutoHotkeyGUI" in Unicode hex: 4100750074006F0048006F0074006B0065007900470055004900

Esc::ExitApp

[JnLlnd]

I use this instead of a hex editor, thanks SKAN

Good stuff. Thanks for sharing and thanks to SKAN!