is there any way to export dll functions only when a certain condition exists? here's the scenario:
1. program calls an exported dll function, passing a "code".
2. dll checks the value of the code, and if it is ok, other exported functions will become available, and if the code is incorrect those functions would remain unavailable.
Any ideas would be appreciated.
There is a similar Delphi implementation by James Mistry. It is based on the C program. However, in NT and XP the function simply doesn't work. Does anybody know if this is also the case with the C function?
I have a MFC application. It loads a DLL and invokes a method in it. In this method few arguments are passed of type long, LPSTR, COM interface pointer. I can access these arguments in the method in which I have passed them. I store them in some DLL variables. But when I try to access them in some other DLL method, these variables are set to the default value i.e. to NULL. How do you save the state of the variables, is anything special is needed for COM interface pointer?
I use to call function from my activex dll from VB application, i use createobject to create the dll object, the tASK MANAGER shows that application increase in memory size, thats obivious but when i use set object=nothing then why that memory isn't returned to window system, it is showing same memory and some times 2-3 bytes less.
Plz help me friends.
I have one regular dll which exports few functions. I have loaded the dll in my VC application and trying to call the functions. GetProcAddress returns me some valid address. But when I give call to that function, it fails.
Can anybody please tell me what is the problem or where I am going wrong ?
Posted by Rakeshsoni
on 04/28/2005 03:30am
There may be a problem with the calling convention. Make sure you are calling the function the same way you declared it.
When i run c++ dll, i got error message below. Is there anyone can help me?
The value of ESP was not saved across a function call .This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention.
Posted by Rakeshsoni
on 04/28/2005 04:25am
The message shown by Windows is quite clear and correct. This is happening because the way the function was defined is not the same as the way you are calling for example WINAPI is missing or the return type is incorrect or something of that sort.
I am trying to download this game for Windows 2000. Its saying that i dont have thedinput8.dll file or the dsound.dll file and its keep on doing that when i download them. Is there something i can buy to fix this promblem?�?