Fatal Error Messages (Part 2) 1050 - 1098
L1050
too many groups in one module
Explanation: LINK386 found more than 32 group definitions (GRPDEF)
in a single module.
Action: Reduce the number of group definitions by splitting the
module, by eliminating one or more group definitions, or combining group
definitions.
L1051
too many
groups
Explanation: The program defines more than 32 groups in addition
to DGROUP.
Action: Reduce the number of group definitions by splitting the
module, by eliminating one or more group definitions, or combining group
definitions.
L1052
too many
libraries
Explanation: You tried to link with more than 32 libraries.
Action: Combine libraries, or use modules that require fewer libraries.
L1053
out of memory for
symbol table
Explanation: The program has more symbolic information, such as
public, external, segment, group, class, and file names, than the amount
that could fit in available real memory.
Action: Combine modules or segments and recreate the object files.
Eliminate as many public symbols as possible or use shorter names.
L1054
requested segment limit too high
Explanation: There is not enough memory to allocate the necessary
tables for the amount of segments requested.
Action: Reduce the number of segments by combining or creating additional
executable modules.
L1057
data
record too large
Explanation: A LEDATA record (in an object module) contained more
than 1024 bytes of data. This is a translator (compiler or assembler) error.
Action: Note which translator (compiler or assembler) produced the
incorrect object module and the circumstances, and contact your supplier.
L1060
program exceeds number
bytes
Explanation: There is not enough memory to process all segments.
Action: Reduce the number of segments by combining or creating additional
executable modules.
L1063
out
of memory for debugging information
Explanation: LINK386 was given too many object files with debug
information, and ran out of space to store them.
Action: Reduce the number of object files that have debug information.
L1064
out of memory - name
heap exhausted
Explanation: The linker ran out of heap space; name = near
or far.
Action: Reduce the number of background processes or install more
memory.
L1070
name:
segment size exceeds 64K
Explanation: A single segment contains more than 64K of code or
data. This could be because you attempted to combine identically named segments.
Action: Try compiling (or assembling) and linking using a larger
memory model or breaking up the named segment.
L1071
segment _TEXT larger than 65,520 bytes
Explanation: This error is likely to occur only in small-model C
programs, but it can occur when any program with a segment named _TEXT is
linked using the /DOSSEG option of the LINK386 command. Small-model C programs
must reserve code addresses 0 and 1; the reserve is increased to 16 for
alignment purposes.
Action: Make the program source code smaller, or change to a larger
memory model.
L1072
common
area longer than 65,536 bytes
Explanation: The program has more than 64K of communal variables.
This error occurs only with programs produced by compilers that support
communal variables.
Action: Rewrite your program using fewer or smaller communal variables.
L1073
file-segment limit
exceeded
Explanation: There are more than 255 physical or file segments.
Action: Reduce the number of physical or file segments. You could
use the Combine Contiguous Data (/PACKD) option for combining data segments
or the Combine Contiguous Code (/PACKC) option for combining code segments.
L1074
name: group
larger than 64K
Explanation: A group contains segments that total more than 65,536
bytes.
Action: Reduce the number or size of segments or remove segments
from the group.
L1075
entry
table larger than 65,535 bytes
Explanation: You have exceeded a linker table size limit because
of an excessive number of entry names.
Action: Reduce the number of names in the modules that you are linking
or create additional executable modules.
L1076
name:
segment size exceeds numberM
Explanation: The named segment is larger than the specified size.
Action: Break the segment into smaller segments and try again.
L1077
common area longer than 4G-1 bytes
Explanation: The space for the C languages common area is too big.
Action: If the load module is an .EXE,
consider putting some routines in .DLL; otherwise, link without debugging
information or create additional executable modules.
L1080
cannot open list file
Explanation: The disk or a directory is full, or an invalid file
name was specified.
Action: Check that the file name specified is correct. Delete or
move files to make space and restart LINK386.
L1081
out of space for run file
Explanation: The disk on which the .EXE file is being written is
full.
Action: Delete or move files to make space and restart LINK386.
L1082
name: stub
file not found
Explanation: The stub file specified in the module definition file
could not be found.
Action: Check that the correct path to the stub file has been specified.
L1083
cannot open run file
- reason
Explanation: The run file could not be opened for the stated reason.
Action: Correct the problem and restart LINK386.
L1088
out of space for list file
Explanation: The disk on which the listing file is being written
is full.
Action: Delete or move files to make space and restart LINK386.
L1089
filename: cannot
open response file
Explanation: LINK386 cannot find the specified response file. This
usually indicates a typing error.
Action: Include the drive specifier or path, or both, for the response
file.
L1091
unexpected end-of-file
on library
Explanation: The disk containing the library has probably been removed
or is corrupted.
Action: Replace the disk containing the library and restart LINK386.
L1092
cannot open module
definition file
Explanation: The specified module definition file cannot be opened,
or an invalid file name was specified.
Action: Check that the specified file name is correct. Include the
drive specifier or path, or both, for the module definition file.
L1093
name: object not found
Explanation: LINK386 could not open the object module you specified.
Action: Specify full path name or directory in which object module
resides.
L1096
unexpected
end-of-file
Explanation: LINK386 encountered an end-of-file character while
reading an input file AND expected more information.
Action: Check input files for errors and relink.
L1097
I/O error - string
Explanation: The linker encountered the I/O error shown while reading
from a file.
Action: Make sure the file is not corrupted or on a bad disk sector
and relink.
L1098
cannot
open include file filename - reason
Explanation: LINK386 could not open the include file for the stated
reason.
Action: Correct the problem and restart LINK386.
[Back: Fatal Error Messages (Part 1) 1001 - 1049]
[Next: Fatal Error Messages (Part 3) 1100 - 1130]