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.
BIND Limitations
◄Up► ◄Contents► ◄Index► ◄Back►
─────BIND Limitations───────────────────────────────────────────────────────
Not all programs can be bound. Programs suitable for conversion
should make no system calls other than calls to the functions
listed in the Family API. (The Family API is a subset of the
Application Program Interface functions and is summarized in the
"Microsoft(R) Operating System/2 Programmer's Reference.")
If your program makes calls to dynamic-link functions outside the
Family API, you have three alternatives:
1. Specify a standard (not DLL) library containing the non-API
functions. To do this, use the <linklibs> field of the
command line.
See: ◄BIND Command-Line Syntax►
2. Have your program check which operating system is running and
restrict system calls to functions in the Family API when
running under DOS.
BIND supports this alternative by providing the /N command-
line option. With this option, you specify a list of
functions supported only in protected mode. If your program
attempts to call one of these functions in real mode, the
BadDynLink system function in the Family API is called, and
your program aborts.
See: ◄Specify Protected-Mode Functions (/N)►
3. Create a dual-mode version of your program.
See: ◄How to Build a Dual-Mode Program►
An executable produced with BIND can be run under DOS versions 2.0
and higher. However, if you rename the file produced by BIND, it
can be run only under DOS versions 3.0 and higher.
-♦-