FIX: DOSXNT DX1020 Error Using .WHILE and Processor Flag

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

The information in this article applies to:

  • Microsoft Macro Assembler for MS-DOS, versions 6.1 and 6.1a
  • Microsoft Macro Assembler for MS-DOS version 6.0, running under OS/2 version 1.21

SYMPTOMS

Microsoft Macro Assembler (MASM) version 6.1, and 6.1a may generate a DOSXNT DX1020 general protection fault when using the .WHILE directive to test the state of a processor flag (SIGN?, ZERO?, CARRY?, PARITY?, or OVERFLOW?). The error occurs if the processor flag is tested by itself or is negated and tested. For example:

   .WHILE SIGN?
   .WHILE !SIGN?

MASM version 6.0 running under OS/2 version 1.21 may generate a trap 13 in the above situation.

RESOLUTION

To work around this problem, OR the desired processor flag with zero. For example:

   .WHILE SIGN? || 0

This work around will also work with ZERO?, CARRY?, PARITY?, and OVERFLOW?.

STATUS

Microsoft has confirmed this to be a problem in MASM versions 6.0, 6.1, and 6.1a. This problem was corrected in MASM version 6.11.

MORE INFORMATION

The following sample code can be used to demonstrate the problem.

Sample Code

; Assemble options needed: none

.MODEL small .STACK 4096

.DATA

.CODE

    .startup
    .WHILE SIGN?       ; generates DOSXNT general protection fault
        nop
    .ENDW
    .WHILE SIGN? || 0  ; avoids the protection fault
        nop
    .ENDW
    .exit 0
END


Additional reference words: 6.00 6.10 6.10a unhandled exception buglist6.00
buglist6.10 buglist6.10a fixlist6.11
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.