Microsoft KB Archive/141147

{|
 * width="100%"|

Calling Configuration Manager from Windows 95 Apps and DLLs

 * }

Q141147

-

The information in this article applies to:


 * Microsoft Win32 Device Driver Kit (DDK) for Windows NT, version 4.0

-

SUMMARY
From a 16-bit Windows-based application or DLL, you can make calls to the Windows 95 Configuration Manager. However, a 32-bit application or DLL cannot make Configuration Manager calls directly; to do so, it must thunk to 16-bit code.

To make Configuration Manager calls from 16-bit Windows-based code, you must include the Configmg.h header file from the DDK. You must also follow these steps:


 * 1) Use #define Not_VxD before including Configmg.h.
 * 2) Ensure that IS_32 is not defined anywhere.
 * 3) Include Vmm.h before including Configmg.h.

You need to call Configuration Manager functions from 16-bit Windows-based code by using the correct naming scheme. The function names should begin with CM_ not CONFIGMG_.

You may find when making 16-bit Windows-based Configuration Manager function calls that the names of some flags as documented in the Windows 95 DDK will not work. In this case, use the flag names as they are listed in the Configmg.h file.

Additional query words: Windows 95 4.00

Keywords : kbnokeyword kbDDK

Issue type :

Technology : kbAudDeveloper kbWinDDKSearch kbWin32sSearch kbWin32DDKSearch kbWin32DDKNT400 kbWin32DDKNTSearch