2 replies to this topic

[axlar]

May I suggest a manual modification here?

 

Sometime people (including ME!)  misses DLLCall and got ErrorLevel -3 because of if bit-edition different.

for example:

DllCall not calling a function properly

DllCall Failing x64 - Issues

Using AHK to control vJoy

 

if I DLLCall from 32-bit AHK to 64-bit DLL, got -3.

if I DLLCall from 64-bit AHK to 32-bit DLL, got -3.

 

My suggestion is that description for ErrorLevel -3 should be include exlpanation like "32-bit AHK can not call functions in 64-bit DLLs".

 

I know most of people knows it naturally.

But if there is description for bit-edition-different, it will be a bit help for people realizing cause of problem in loadlibrary who failed to DLLCall with ErrorLevel -3.

 

Current description for ErrorLevel -3 in DLLCall Manual: 

-3: The specified DllFile could not be accessed. If no explicit path was specified for DllFile, the file must exist in the system's PATH or A_WorkingDir. This error might also occur if the user lacks permission to access the file.

 

I think fincs's explanation is appropriate. (Sorry I do not speak English,)

 

 

 

32-bit programs can only load 32-bit DLLs, and 64-bit programs likewise can only load 64-bit DLLs. You should check out if there's a 64-bit version of your DLL.

 

http://www.autohotke...g-x64/?p=548926

[Lexikos]

Best Answer

-3: The specified DllFile could not be accessed and loaded. If no explicit path was specified for DllFile, the file must exist in the system's PATH or A_WorkingDir. This error might also occur if the user lacks permission to access the file, or if AutoHotkey is 32-bit and the DLL is 64-bit or vice versa.

Is that sufficient?

[axlar]

Hi Lexikos, Yes it is. Thank you so much!