KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q58929: BIND Error "Import By Ordinal Not Defined: DOSCALLS.5"

Article: Q58929
Product(s): See article
Version(s): 1.00   | 1.00
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | s_bind | mspl13_basic
Last Modified: 27-DEC-1990

Question:

When I use BIND version 1.00 to bind my OS/2 program, the following
error message is returned:

   Import by ordinal not defined: DOSCALLS.5

I bind my program with the following:

   BIND hello.exe -o hellob.exe

Why do I get that error when I call FAPI functions by name and not
their ordinal numbers?

Response:

The above error occurs because DOSCALLS.LIB must be listed on the BIND
command line. Bind automatically searches for API.LIB and OS2.LIB
(using the LIB environment variable), but not DOSCALLS.LIB.

When using bind, DOSCALLS.LIB must be explicitly listed on the command
line and the LIB environment variable must point to API.LIB and
OS2.LIB. For example:

   BIND hello.exe c:\c510\lib\doscalls.lib -o hellob.exe

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.

Copyright Microsoft Corporation 1986-2002.