FIX: ALIGN Immediately After INCLUDE Generates L1101

Last reviewed: September 16, 1997
Article ID: Q80119
6.00 | 6.00 MS-DOS | OS/2 kbtool kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft Macro Assembler for MS-DOS, version 6.0
  • Microsoft Macro Assembler for OS/2, version 6.0

SYMPTOMS

The Microsoft Macro Assembler (MASM) version 6.0 generates an invalid object module when given code that contains an INCLUDE directive followed immediately by an ALIGN directive. The contents of the included file are not important; it can even be an empty file. The linker may not issue a warning. If the linker does detect the error, it generates the following:

   error L1101: invalid object module

RESOLUTION

To work around this problem, place the INCLUDE directive at the beginning of the file so that the ALIGN directive does not immediately follow the INCLUDE directive.

STATUS

Microsoft has confirmed this to be a problem in MASM version 6.0. This problem was corrected in MASM version 6.0a.

MORE INFORMATION

If you assemble the following sample code with /Zi, the linker will detect the invalid object module and issue the error message. Without /Zi, no warning is given and the program terminates normally, but the object module is still invalid.

Sample Code

; Assemble options needed: none ; The file FILE.INC needs to be created, but may be left empty.

_text   SEGMENT para public 'code'
        ASSUME  CS:_text

start: mov cx, 0100h INCLUDE FILE.INC
        ALIGN 4
loopx: mov ax, 4C00h
        int 21h

_text   ENDS

END     start


Additional reference words: 6.00 buglist6.00 fixlist6.00a
KBCategory: kbtool kbfixlist kbbuglist
KBSubCategory: MLIss
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.