KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q58815: "Unresolved External" Using Wrong Linker with BASIC 7.00, 7.10

Article: Q58815
Product(s): See article
Version(s): 7.00 7.10 | 7.00 7.10
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | SR# S900130-159 S_LINK | mspl13_basic
Last Modified: 4-SEP-1990

Microsoft BASIC Professional Development System (PDS) versions 7.00
and 7.10 for MS-DOS and MS OS/2 are shipped with Microsoft
Segmented-Executable Linker versions 5.05 and 5.10 respectively.
Because of the newer technology used in these linkers, it is more
important than ever to use only the linker that comes with the product
(or a later version of the Segmented-Executable Linker) to link BASIC
PDS programs.

Linking BASIC PDS modules with a version of LINK.EXE earlier than
5.05, such as the Microsoft 8086-Object Linker, can result in "L2029:
Unresolved external" errors, such as the following:

     B$IsamSetmemDown in file(s):
   C:\BC7\LIB\BCL70ENR.LIB(..\rt\isam.asm)

     B$IsamSetmemBack in file(s):
   C:\BC7\LIB\BCL70ENR.LIB(..\rt\isam.asm)

     B$RestoreEmsState in file(s):
   C:\BC7\LIB\BCL70ENR.LIB(..\rt\isam.asm)

     B$DoIsamTerm in file(s):
   C:\BC7\LIB\BCL70ENR.LIB(..\rt\isam.asm)

     B$FIsamInited in file(s):
   C:\BC7\LIB\BCL70ENR.LIB(..\rt\isam.asm)

These errors should not occur when linking BASIC PDS modules with
Microsoft Segmented-Executable Linker versions 5.05 or later.

A very common mistake is running the Linker from a directory that does
not contain LINK.EXE and thus invoking an older linker version found
first in your DOS PATH. You must be sure to have the correct linker
found in your DOS PATH or in the current directory.

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.