L1001

option : option name ambiguous
Explanation: A unique option name does not appear after the option indicator (/).
Example: The command

    LINK386 /N main;

produces this error because LINK386 cannot tell which of the seven options beginning with the letter N is intended.
Action: Retry using the correct minimum option abbreviation.

option : invalid numeric value
Explanation: An incorrect value appeared for one of the LINK386 options. This might be because a character string has been entered for an option that requires a numeric value or because the proper numeric prefix (for example, 0x for hexadecimal) was not used for a numeric value.
Action: Retry with a numeric value.

option : stack size exceeds 65,535 bytes
Explanation: The size you specified for the stack in the /STACK option of the link command is more than 65,535 bytes.
Action: Retry with a stack size of less than or equal to 65,535 bytes.

option : segment limit set too high
Explanation: The specified limit on the /SEGMENTS option is greater than 16 375.
Action: Retry with a limit in the range 1 to 16 375.

no object modules specified
Explanation: You did not specify any object file names to the linker.
Action: Restart LINK386, including at least one object file name.

cannot nest response files
Explanation: A response file has been named within another response file. You have used @filename within the response file. The @ symbol is reserved by LINK386 to signify a response file name.
Action: Edit the response file to remove the nested response file.

response line too long
Explanation: A line in an automatic response file is longer than 256 characters.
Action: Edit the line to make it shorter than 256 characters. Response files can contain more than one line.

terminated by user
Explanation: You pressed Ctrl+C or Ctrl+Break.
Action: Your action has terminated LINK386. Restart if necessary.

missing internal name
Explanation: You have not specified an internal name for an import in the module definition file.
Action: Edit the module definition file, giving an internal name so that LINK386 can identify references to the import.

module description redefined
Explanation: You have used the DESCRIPTION keyword for a module in the module definition file more than once.
Action: Edit the module definition file, deleting the extra descriptions.

module name redefined
Explanation: You have defined a module name more than once with the NAME or LIBRARY keyword in the module definition file.
Action: Edit the module definition file, checking the module name definitions.

input line too long; number characters allowed
Explanation: The input line contains more than number characters.
Action: Retry the command with fewer characters on the input line.

too many exported entries
Explanation: You have tried to export more than 65535 names.
Action: Retry with fewer names, creating an additional executable module if necessary.

resident-name table overflow
Explanation: The total length of all your resident-names, together with an overhead of 3 bytes for each name, is greater than the LINK386 limit. The internal LINK386 limit is 65,534 for LINK386 versions prior to 2.01.012 and is 1,048,576 for LINK386 version 2.01.012 and later versions.
Action: Reduce the number or the length of your resident names.

nonresident-name table overflow
Explanation: The total length of all your nonresident-names, together with an overhead of 3 bytes for each name, is greater than 65,534 for versions prior to 2.01.012 and is 1,048,576 for LINK386 version 2.01.012 and later versions.
Action: Reduce the number or the length of your nonresident-names.

relocation table overflow
Explanation: There are more than 65,535 load-time relocations for a single segment.
Action: Reduce the number of relocations in the source files and recompile or reassemble them. Interframe references generate load-time relocations.

imported-name table overflow
Explanation: The total length of all your imported-names, together with an overhead of 1 byte for each name, is greater than 65,535 bytes.
Action: Reduce the number or the length of your imported-names.

too many TYPDEF records
Explanation: An object module contains more than 255 TYPDEF records. These records describe communal variables. This error can only appear with programs produced by compilers that support communal variables.
Action: Reduce the number of TYPDEF records, breaking the module into smaller parts, if necessary.

too many external symbols in one module
Explanation: An object module specifies more than the limit of 1023 external symbols.
Action: Reduce the number of external symbols, breaking the module into smaller parts, if necessary.

too many group, segment, and class names in one module
Explanation: The program module contains too many group, segment, and class names.
Action: Reduce the number of groups, segments, or classes, and re-create the object files.

too many segments in one module
Explanation: An object module has more than 255 segments.
Action: Reduce the number of segments, splitting the module or combining some segments.

too many segments
Explanation: The program has more than the maximum number of segments. The /SEGMENTS option specifies the maximum allowed number; the maximum is 16375.
Action: Restart LINK386 using the /SEGMENTS option with an appropriate number of segments.