AutoHotkey Community

Apart from that, it would still be nice if the new function could be used in newer windows versions.Not only nice, this is the only reliable solution. Any method to workaround via altering the chain i ...

The old clipboard APIs AHK uses were written in the ancient age when programmers could be trusted. Nowadays, if in Vista or higher, better use the modern APIs Add(Remove)ClipboardFormatListener.

The function was designed that way. The simplest way to achieve what you want is using PrintWindow API, but, you will loose the transparency of the window.

Replace the following in the code
DllCal ...

I suggest to read this thread and the linked thread thoroughly as the start.

Allowing Function Pointer in DllCall: ComCall via DllCall

I have checked the Remote variable after calling DllCall, it contains only zeros.I think that's a good sign. BTW, what I meant was more like:
VarSetCapacity(Remote, 40) ; 8 bytes appear to be ...

I have no problem with the gtvremote64.dll.Actually that was my immediate suggestion, using 64bit dll instead as there is only one calling convention with x64. But, I removed that shortly after I noti ...

But why the GetDeviceName and GetCode are working in this case?..__thiscall is almost identical to __stdcall except for the this pointer (in the register). So, as long as a function doesn't have to ac ...

If you want to modify other process's context menu you have to create a contextmenu handler dll file. But, you can simulate some of them inside AHK:
http://www.autohotkey.com/forum/topic22120.html

So, Python supports multi-threading? I didn't know that. Anyway, the page you linked uses IGlobalInterfaceTable for inter-thread marshaling. Although I didn't implement it into AHK code as AHK is sing ...

..to get the FTP_AsyncCallback() to at least be called.Yes, FTPCallbackAddress played the role of lpdwContext in your case. Then, you get NumGet(0, FTPCallbackAddress, "UInt") as dwContext i ...

Your usage of dwContext, which is actually lpdwContext, in InternetConnect was incorrect. The correct form is:
dwContext := 8 ; can be any user-defined value
hInternet := DllCall("w ...

AutoHotkey.dll needs a careful redesign. To see what part is the problem, run the following code and read the error message.
COM_Init()
pshl := COM_CreateObject("Shell.Applicati ...

I did a quick test and found out that AutoHotkey.dll had an issue with out-of-process COM objects, like InternetExplorer, Word, Excel etc. It was the root of your problem. Test code:
COM_Init( ...

OK, I'll test the code today. BTW, as COM.ahk is merely a script, I presume it's more an issue of AutoHotkey.dll side.

I don't have AhtoHotkey.dll in my system, however, I suppose it's of various flavors/builds as it's based on AHK_L, 32/64-bit and/or ANSI/UNICODE. And, COM.ahk also has various versions, for 32-bit AH ...