PRB: VerLanguageNameA() Not Exported in Win32s

Last reviewed: March 6, 1996
Article ID: Q147876

The information in this article applies to:

Microsoft Win32s version 1.3c

SYMPTOMS

If you call VerLanguageName() from a 32-bit application running under Win32s, you will get an Undefined link error on VerLanguageNameA in Version.dll.

CAUSE

In Win32s, Version.dll does not export this function. In Windows NT and Windows 95, VerLanguageNameA is exported in both Version.dll and Kernel32.dll. In Windows NT, Version.dll forwards the export of VerLanguageName() to the export in Kernel32.dll. In Windows 95, Version.dll separately calls the function in Kernel32.dll.

RESOLUTION

Under Win32s, you can still use the VerLanguageName() function from your application because the function exists in Kernel32.dll. You will need to specify Kernel32.lib before Version.lib on your link line. Then your application will use the function from Kernel32.dll.

STATUS

This behavior is by design.

Additional reference words: 1.30c win32s gdi
KBCategory: kbprg kbprb
KBSubcategory: w32s kbgdi

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: March 6, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.