Link to home
Start Free TrialLog in
Avatar of Slarti
Slarti

asked on

VC++: Weird problem with DLLs

I am trying to figure out how to use other peoples' DLLs in Visual C++, but for some reason I can't seem to load the DLL into memory. I tried the following:

Created a new MFC application (.exe) and added the following code fragment anywhere (for example in CTestView::OnDraw):

HINSTANCE hlib = AfxLoadLibrary("commdlg.dll");
DWORD error = GetLastError();

When I step through this code I see that hlib obtains the value 0 (load failure) and error is equal to 31, which is the error code for General Failure Error. What in the world does a general failure error have to do with loading a DLL? The same result occurs regardless of the DLL I am using (I used commdlg.dll because I know it's a DLL that works). I know that error 31 is originating from AfxLoadLibrary because when I use GetLastError before the call to AfxLoadLibrary I get an error code 0 (success).

What is going on here? I doubt the General Failure error is really what's going on because everything in my OS is working properly (including things that other programs load from the commdlg.dll library). How can I solve this problem?
(Please don't tell me that I can use MFC functions that call commdlg.dll. I've already tried it, and it works. That library name is only an example. The same result happens no matter what DLL I try to load, this is just so that you can try the above code fragment on your computer if you want).

Thanks in advance!

-- Slarti
ASKER CERTIFIED SOLUTION
Avatar of galkin
galkin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Slarti
Slarti

ASKER

That is probably the problem, then. But I would still like to be able to load 16-bit DLLs into memory. (The problem is that I am trying to interface with a device driver written for Windows 3.1). How can I load a 16-bit DLL?
You cannot load a Win16 DLL into a Win32 program's address space. Win32s provided a way for you to do this, but I don't know if it's even supported anymore. Furthermore, Trying to interface to a Win16 device driver in a Win32 environment is extremely dangerous if not impossible. How can you interface to it if the OS won't even load it? Even if you wrote a Win16 program and loaded the driver file directly, Windows would prevent you from accessing the device without going through bona-fide drivers.