DOC: LibraryProcedure DLL Prototype Incorrect

 Last reviewed: April 7, 1997
Article ID: Q136681
3.51 WINDOWS NT kbprg kbdocerr kbdocfix

The information in this article applies to:

  • Microsoft Win32 Device Driver Kit (DDK), version 3.51

SUMMARY

Setup provides LoadLibrary, FreeLibrary, and LibraryProcedure commands to provide a mechanism to add custom procedures to setup scripts.

The LibraryProcedure command provides a way to call an exported function in the specified DLL. This procedure is described in the Windows NT DDK documentation. Drill down to it by following this outline: 

Programmers Guide   (2.3.5.1)
    Setup (part 1)
       Chapter 2 - Driver Installation
          GUI INF Script Language
             Using DLLs and External Programs
                DLLs in Install and Shell Sections
The documentation states the DLL function called by LibraryProcedure must have the following prototype:

BOOL FunctionName(cArgs, lpszArgs[], *lpszTextOut) 

            DWORD cArgs;
            LPSTR lpszArgs[];
            LPSTR *lpszTextOut);
The correct prototype for this function is:

BOOL PASCAL FunctionName(cArgs, lpszArgs[], *lpszTextOut) 

            DWORD cArgs;
            LPSTR lpszArgs[];
            LPSTR *lpszTextOut);
This documentation error has been corrected in the Windows NT DDK version 4.0 documentation.

KBCategory: kbprg kbdocerr kbdocfix
KBSubcategory: NDIS WAN
Additional reference words: 3.51 4.00 SETUP LibraryProcedure Miniports
Keywords : kbprg NDIS WAN kbdocerr kbdocfix
Version : 3.51
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.