Specifications
Error! Style not defined. 787
Filename: LMAETAPA.DOC Project: MASM Environment and Tools
Template: MSGRIDA1.DOT Author: Nobody Last Saved By: Mike Eddy
Revision #: 136 Page: 787 of 103 Printed: 10/09/00 02:49 PM
L1127 far segment references not allowed with /TINY
The /TINY option for producing a .COM file was used in a program that has a far
segment reference.
Far segment references are not compatible with the .COM file format. High-level-
language programs cause this error unless the language supports the tiny memory model.
An assembly-language program that references a segment address also causes this error.
For example, the following causes this error:
mov ax, seg mydata
L1128 too many nested include files in module-definition file
Nesting of INCLUDE statements in a module-definition (.DEF) file is limited to 10
levels.
L1129 missing or invalid include file name
The file specification in an INCLUDE statement in the module-
definition (.DEF) file was
missing or was not a valid filename.
LINK Error Messages
L2000 imported starting address
The program starting address as specified in the END statement in an assembly-language
file is an imported routine. This is not supported by the Windows operating system.
L2002 fixup overflow at number in segment segment
This error message is followed by one of these strings:
u target external symbol
u frm seg name1, tgt seg name2, tgt offset number
A fixup overflow is an attempted reference to code or data that is impossible because the
source location (where the reference is made “from”) and the target address (where the
reference is made “to”) are too far apart. Usually the problem is corrected by examining
the source location.
For information about frame and target segments, see the Microsoft MS-DOS
Programmer’s Reference.
L2003 near reference to far target at offset in segment segment
pos: offset target external name
The program issued a near call or jump to a label in a different segment.
This error occurs most often when specifically declaring an external procedure as near
that should be declared as far.
This error can be caused by compiling a small-model C program with CL’s /NT option.