Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

                                             ◄Up► ◄Contents► ◄Index► ◄Back►
─────BIND Internal Operation────────────────────────────────────────────────
 
     BIND performs three major steps:
 
       1. For imported functions, BIND reads the dynamic-link entry
          points from the OS/2 executable file. For each function, BIND
          writes an EXTDEF object record to a temporary object file.
          Each EXTDEF record is associated with an external reference
          that the linker must resolve.
 
       2. BIND uses LINK to link the executable file, the temporary
          object file, the API.LIB file, and any other libraries
          specified on the BIND command line.
 
          The API.LIB library file supplies a stub loader module. This
          module loads the OS/2 executable file in a DOS environment
          and simulates the OS/2 startup conditions. API.LIB also
          supplies code that emulates the OS/2 Family API (Family
          Application Program Interface) in a DOS environment.
 
       3. BIND merges the protected-mode and real-mode executable files
          into a single file that runs in either mode.
 
     See: ◄Internal Layout of a Bound Program►
                                    -♦-