Nonfatal Error Messages 2000 - 2063
L2000
imported starting address
Explanation: A MODEND, or starting address record, referred to
an imported name. Imported program-starting addresses are not supported.
Action: The starting address record must refer to a non imported
name. Edit the source file and recompile or reassemble.
L2002
fix-up overflow at location in segment name
Explanation: A fix up overflow occurred near location, in
the named segment. See Conditions
That Can Cause LINK386 Error 2002.
Action: Revise the source file and re-create the object file. If
that does not work, contact your supplier.
L2003
inter segment self-relative fix-up at location
in segment name
Explanation: LINK386 detected an inter segment self-relative fix-up.
A self-relative fix-up cannot be in another segment. This is probably caused
by a near reference to procedure located in another segment.
Action: Revise the source file and re-create the object file. If
that does not work, contact your supplier.
L2005
fix-up type unsupported at location in segment
name
Explanation: LINK386 detected an unsupported fix up type. This
is probably a compiler or assembler error.
Action: Revise the source file and re-create the object file. If
that does not work, contact your supplier.
L2010
too many fix-ups in LIDATA record
Explanation: There are more fix ups applying to a LIDATA record
than will fit into the LINK386's 1024 byte buffer. The buffer is divided
between the data in the LIDATA record itself and the run-time relocation
items. These are 8 bytes each, so the maximum varies from 0 to 128. This
is probably a compiler error.
Action: Revise the source file and re-create the object file. If
that does not work, contact your supplier.
L2011
name: NEAR/HUGE conflict
Explanation: There are conflicting NEAR and HUGE attributes for
a communal variable. This error can occur only with programs produced by
compilers that support communal variables.
Action: Specify only one of these attributes.
L2012
name: array-element size mismatch
Explanation: A far communal array has been declared with two or
more different array-element sizes (for example, an array declared once
as an array of characters and once as an array of real numbers). This error
occurs only when using compilers that support far communal arrays.
Action: Match the definitions and re-create the object module or
modules.
L2013
LIDATA record
too large
Explanation: A LIDATA record in an object module contains more than
512 bytes of data. It is likely that one of your assembler modules contains
a complex structure definition or a series of deeply-nested DUP operators.
(LIDATA is a DOS term.)
Example: The following structure definition causes this error:
alpha DB 10DUP(11 DUP(12 DUP(13 DUP(...))))
Action: Simplify the structure definition and reassemble the module.
L2022
name (alias
internalname) : export undefined
Explanation: A name has been directed to be exported but is not
defined anywhere.
Action: Edit the source file and define the export.
L2023
name (alias internalname) : export
imported
Explanation: An imported name has been directed to be exported.
Items that are not in the source file itself cannot be exported. You cannot
export this imported name.
Action: Edit the source file to not export the imported name.
L2024
name: special symbol already defined
Explanation: Your program defined a symbol name that LINK386 already
used for one of its low-level symbols. For example, the linker generates
special names for overlay support.
Action: Edit the source file and choose another name for the symbol.
L2025
name: symbol
defined more than once
Explanation: A symbol has been defined more than once in the object
file.
Action: Edit the source file, removing the extra symbol definition.
L2026
entry ordinal number,
name name : multiple definitions for same ordinal
Explanation: More than one entry point
name has been assigned to the same ordinal in the module definition file.
Action: Edit the module definition file to correct the usage of
the ordinal.
L2027
number:
ordinal too large for export
Explanation: You tried to export more than 3072 names or indicated
too large of an ordinal.
Action: Edit the source file or define smaller ordinals in the module
definition file.
L2029
string:
unresolved external
Explanation: A symbol declared to be external in one or more modules
was not found among the given objects and libraries.
Action: Supply files that will resolve these external calls.
L2030
starting address not code (use class 'CODE')
Explanation: You specified a starting address to LINK386 that is
not within a segment of type 'CODE.'
Action: Reclassify the segment to CODE, or correct the starting
point.
L2044
string:
symbol multiple defines, use /NOE
Explanation: The symbol shown was defined more than once, perhaps
for different things.
Action: Recompile with the /NOEXDICTIONARY option.
L2047
IOPL attribute conflict - segment: name in
group:name
Explanation: The segment indicated within the group shown has different
IOPL attributes from the rest of the segments in the group.
Action: Remove the segment from the group or make sure all segments
have the same IOPL attributes. Relink.
L2050
use16/use32
attribute conflict - segment:name in group:name
Explanation: The segment indicated within the group shown has a
different USE16/USE32 attribute from the rest of the segments in the group.
Action: Remove the segment from the group or make sure all segments
have the same USE16/USE32 attribute.
L2052
name:
unresolved external - possible calling convention mismatch
Explanation: LINK386 encountered an undefined external, which could
be a fast-call/C-call mismatch.
Action: Make sure the external is defined and called the same way
(for example, all C-calls).
L2053
call
gates are NOT allowed in 32-bit object if its size exceeds 64K - memory
object number number
Explanation: The memory object indicated is larger than 64K and
uses call gates.
Action: Remove the call gates or break the object into smaller portions.
Relink.
L2054
data for
invalid page in segment name
Explanation: LINK386 encountered data past the defined end of initialized
data in the segment indicated.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your supplier.
L2055
fix-up for invalid page at location in segment
name
Explanation: LINK386 encountered a fixup past the defined end of
initialized data in the segment indicated.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your
L2056
object type conflict - segment: name in group:
name
Explanation: The segment indicated within the group shown has a
different TYPE attribute from the rest of the segments in the group.
Action: Remove the segment from the group or make sure all segments
have the same TYPE attribute.
L2057
duplicate
of name with different size found; record ignored
Explanation: LINK386 encountered two COMDAT records with the selection
type "SAME SIZE." The records have the same name but have different sizes.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your
L2058
different duplicate of name found; record
ignored
Explanation: LINK386 encountered two COMDAT records with the selection
type "EXACT." The records have the same name but have different sizes.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your
L2059
size of the data block associated with name exceeds
4G
Explanation: LINK386 encountered a continuation COMDAT record whose
additional size made the communal data too large.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your
L2061
no space for the data block associated with record
name inside the segment name
Explanation: While being allocated space for a COMDAT record inside
the segment indicated, the segment grew larger than 64K.
Action: Make the segment smaller or move communal data into a different
segment.
L2062
continuation
of COMDAT name has conflicting attributes; record ignored
Explanation: While concatenating the COMDAT record indicated, LINK386
found attributes that differ from those defined in the initial COMDAT record.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your
L2063
name allocated in undefined segment
Explanation: LINK386 encountered a COMDAT record in an undefined
explicit allocation segment.
Action: The .OBJ is probably corrupted. Recompile or reassemble
and try again. If that does not work, contact your supplier.
[Back: Fatal Error Messages (Part 4) 1200 - 1218]
[Next: Warning Error Messages 4000 - 4087]