Fatal Error Messages (Part 3) 1100 - 1130
L1100
stub .EXE file invalid
Explanation: The stub file specified in the module definition file
is not a valid .EXE file.
Action: Ensure that the stub file is an executable file.
L1101
invalid object module
Explanation: One of the object modules was incorrectly formed during
compilation or assembly.
Action: Recompile or reassemble your source code. If the error persists,
contact your supplier.
L1102
unexpected
end-of-file
Explanation: An invalid format for a library was found.
Action: Restore the library file from your backup disk and restart
LINK386. If this does not work, rebuild your library or contact your supplier.
L1103
name: attempt
to access data outside segment bounds
Explanation: A data record in an object module specified data extending
beyond the end of a segment. This is a translator error.
Action: Note which translator (compiler or assembler) produced the
incorrect object module and the circumstances, and contact your supplier.
L1104
filename: not
valid library
Explanation: The specified file is not a valid library file. This
error causes LINK386 to stop running.
Action: Ensure that the named file is a valid library file and restart
LINK386. If this does not work, rebuild your library or contact your supplier.
L1105
invalid object due
to aborted incremental compile
Explanation: An object file from an aborted compile is trying to
be linked.
Action: Recompile the source that produced the bad compile and then
relink.
L1106
unknown COMDAT
allocation type for name; record ignored
Explanation: The COMDAT (record in .OBJ) allocation type for the
named COMDAT was not valid.
Action: Recompile or reassemble .OBJ and try again. If that does
not work, contact your supplier.
L1107
unknown
COMDAT selection type for name; record ignored
Explanation: The COMDAT (record in .OBJ) selection type for the
named COMDAT is not valid.
Action: Recompile or reassemble .OBJ and try again. If that does
not work, contact your supplier.
L1108
invalid
format of debugging information
Explanation: An error was detected in a segment that contains debug
information.
Action: Recompile or reassemble and try again. If that does not
work, try relinking without using the /DE or /CO options.
L1113
unresolved COMDEF; internal error
Explanation: LINK386 encountered a COMDEF (record in .OBJ) in pass
2 that was not defined in pass 1.
Action: Recompile or reassemble and try again. If that does not
work, contact your supplier.
L1114
unresolved
COMDAT name: internal error
Explanation: LINK386 found specified COMDAT in pass 2 that does
not correspond to COMDATs found in pass 1.
Action: Recompile or reassemble and try again. If that does not
work, contact your supplier.
L1117
unallocated
COMDAT name; internal error
Explanation: The linker encountered COMDAT in pass 2 for which space
was not allocated during pass 1.
Action: Recompile or reassemble and try again. If that does not
work, contact your supplier.
L1121
name:
group larger than 4G-1 bytes
Explanation: The group indicated is too large.
Action: Recompile or reassemble and try again. Remove segments from
the group or create additional executables if necessary.
L1123
name: segment defined both 16- and 32-bit
Explanation: The segment named was defined as both 16-bit and 32-bit.
Action: Create two segments (one for 16-bit, one for 32-bit), or
make sure the segment is defined one way and relink.
L1126
conflicting IOPL-parameter-words value
Explanation: The IOPL parameter words in the .DEF file does not
exactly match those in the corresponding EXPDEF object record.
Action: Make sure .DEF file coincides with that defined in .OBJ.
Relink.
L1128
too many nested
include files in module-definition file
Explanation: The .DEF file exceeded a nesting level.
Action: Combine some nestings into one .DEF file and try again.
L1129
missing or bad include
file name
Explanation: LINK386 could not find a file included by .DEF file.
Action: Make sure the file exists and can be located and that any
path is specified correctly. Try again.
L1130
internal
fix-up applied to undefined area at offset in object number
Explanation: LINK386 attempted to apply an internal fix-up beyond
the defined limits of the object.
Action: This is probably a compiler or assembler error. Revise the
source file and re-create the object file. If that does not work, contact
your supplier.
[Back: Fatal Error Messages (Part 2) 1050 - 1098]
[Next: Fatal Error Messages (Part 4) 1200 - 1218]