FWH 10.1 - DLL32 Function
Posted: Wed Feb 17, 2010 7:52 pm
I'm upgrading from older FWH version using xharbour version .99
the DLL32 function PPO code reveals a call to GetProcAddress() - "OLD Convention"
in the new FWH 10.1 the same DLL32 function PPO code reveals a call to GetProcAdd() -- "NEW Convention"
in the OLD convention, this function returned a binary string used with CallDLL() function.
in newer FWH libraries, this same call results in a value of data type "Pointer" -- I have never seen a datatype "Pointer" before and wonder what exactly it is and how it's used, defined, etc.
anyway, the NEW convention uses GetProcAdd() instead of GetProcAddress() to return the binary string.
I ask because I am getting GPF's while calling a C-Language .DLL file, which always worked fine in old FWH / XHarbour.
What's the difference with new DLL calling convention in CALLDLL() between .99 xharbour FWH libraries and 1.2 xharbour FWH libraries?
in the meantime I will try to build a simple example to get more information.
thank you.
the DLL32 function PPO code reveals a call to GetProcAddress() - "OLD Convention"
in the new FWH 10.1 the same DLL32 function PPO code reveals a call to GetProcAdd() -- "NEW Convention"
in the OLD convention, this function returned a binary string used with CallDLL() function.
in newer FWH libraries, this same call results in a value of data type "Pointer" -- I have never seen a datatype "Pointer" before and wonder what exactly it is and how it's used, defined, etc.
anyway, the NEW convention uses GetProcAdd() instead of GetProcAddress() to return the binary string.
I ask because I am getting GPF's while calling a C-Language .DLL file, which always worked fine in old FWH / XHarbour.
What's the difference with new DLL calling convention in CALLDLL() between .99 xharbour FWH libraries and 1.2 xharbour FWH libraries?
in the meantime I will try to build a simple example to get more information.
thank you.