Article ID: 85509 - Last Review: October 16, 2003 - Revision: 2.0

FIX: ORG Calculated from Label May Fail in 6.0a/6.0b

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q85509

On This Page

Expand all | Collapse all

SYMPTOMS

In Microsoft Macro Assembler (MASM) versions 6.0a and 6.0b, if the expression for an ORG directive is calculated from a label, the ORG directive will not give the correct results. The origin set by the ORG directive will be off by the value of the current location counter ($) prior to the ORG directive.

RESOLUTION

The sample code below demonstrates a macro that can be used to correct the behavior of ORG. This macro should be used only if the expression being supplied to ORG was calculated using a label. If the expression being supplied to ORG was not calculated using any labels, the ORG directive should work correctly.

This macro works correctly only under MASM versions 6.0a and 6.0b.

STATUS

Microsoft has confirmed this to be a problem in MASM versions 6.0a, and 6.0b. This problem was corrected in MASM for MS-DOS version 6.1.

MORE INFORMATION

Sample Code

; Assemble options needed: none

ORGFIX MACRO arg1             ; This macro can be used
   ORG (arg1- ($- @CurSeg))   ; whenever the origin you are
ENDM                          ; trying to set contains a LABEL
                              ; or $ as part of the expression.
.MODEL small
.STACK 4096

.CODE
start LABEL BYTE
   .startup
   .exit 0
finish LABEL BYTE

ORG ((finish- start)+ 10h)    ; This will incorrectly set
tst1 LABEL BYTE               ; the origin.

ORGFIX ((finish- start)+ 10h) ; This will correctly set
tst2 LABEL BYTE               ; the origin.

   DB 'hello'
END
				

APPLIES TO
  • Microsoft Macro Assembler 6.0a
  • Microsoft Macro Assembler 6.0b
Keywords: 
kbfix KB85509
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.