LINK386 is used to combine object files and standard library files into a single file: an executable file, a dynamic-link library, or a device driver. The output file from LINK386 is not constrained to specific memory addresses. Thus, the operating system can load and execute this file at any convenient address.
LINK386 Input
LINK386 uses the following files as input:
LINK386 accepts object files compiled or assembled for 8088, 80286, 80386, 80486, or PENTIUM* microprocessors. Object files must be in the Object Module Format (OMF), which is based on the Intel* 8086 OMF, and Tool Interface Standards Portable Formats Specification.
Library files are used to resolve external references in your object files.
LINK386 Output
LINK386 can produce dynamic-link libraries (.DLL) and device drivers (.SYS), in addition to executable files (.EXE). For additional information, see Output Files.
LINK386 displays all of its output messages on the standard output device.
LINK386 Features
LINK386 creates the executable file and map file in the current directory unless you enter an explicit path.
LINK386 looks in several locations for object, library, and module-definition files. See Where LINK386 Looks for Files.
File names are not case sensitive; for example, abc.exe and ABC.EXE refer to the same file.
If you enter a file name without an extension, LINK386 adds a Default Filename Extension that depends on the type of file expected.
If you leave a field blank (but define the field with a comma), LINK386 uses a default for the field. If you end the LINK386 command with a semicolon (;), LINK386 uses Filename Defaults for all remaining fields.
If you do not give all file names or do not end the command line with a semicolon, LINK386 prompts you for the omitted files.