DOS ain't dead

Watcom ASM + C puzzle, variable has conflicting addresses (Developers)

posted by boeckmann, Aachen, Germany, 01.01.2026, 21:58

> > > this is indeed puzzling. Can you upload the .OBJ file? Then I can
> verify
> > > via OMFDUMP if the corresponding fixup in the OBJ is correct.
> >
> > Here is a .zip archive containing vv.asm and vv.obj:
> >
> > http://0x0.st/P-wO.zip
>
> I inspected the .OBJ file. The fixups are wrong, as they are segment
> offsets:
>
>     FIXUP  segment-relative, type 1 (16-bit offset)
> record offset 0094
> frame method F5 (TARGET index)
> target method T4 (SEGDEF) index 0002 '_DATA'
>
> There are two ways to fix this: The MASM way is to ASSUME:
>
>     assume ds:DGROUP,es:DGROUP
>
> Put this in front or right after the start of the _TEXT segment. This
> should instruct WASM to spit out DGROUP related memory addresses. Be
> careful not to break other code locations.
>
> You may also explicitly indicate that you are referencing DGROUP:
>
>     mov bh,DGROUP:activpg

And as Japheth pointed out a DGOUP definition is missing:

    DGROUP group _DATA

Complete thread:

• Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 31.12.2025, 23:25 (Developers)
  • Watcom ASM + C puzzle, variable has conflicting addresses - jadoxa, 01.01.2026, 02:06
    • Watcom ASM + C puzzle, variable has conflicting addresses - Rugxulo, 01.01.2026, 03:44
  • Watcom ASM + C puzzle, variable has conflicting addresses - Japheth, 01.01.2026, 09:01
    • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 01.01.2026, 16:35
      • Watcom ASM + C puzzle, variable has conflicting addresses - Japheth, 01.01.2026, 18:57
        • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 01.01.2026, 21:07
  • Watcom ASM + C puzzle, variable has conflicting addresses - boeckmann, 01.01.2026, 21:09
    • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 01.01.2026, 21:32
      • Watcom ASM + C puzzle, variable has conflicting addresses - Japheth, 01.01.2026, 21:51
      • Watcom ASM + C puzzle, variable has conflicting addresses - boeckmann, 01.01.2026, 21:56
        • Watcom ASM + C puzzle, variable has conflicting addresses - boeckmann, 01.01.2026, 21:58
          • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 01.01.2026, 22:54
            • Watcom ASM + C puzzle, variable has conflicting addresses - boeckmann, 01.01.2026, 23:26
              • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 02.01.2026, 17:42
                • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 03.01.2026, 18:09
                  • Watcom ASM + C puzzle, variable has conflicting addresses - ecm, 03.01.2026, 21:23
                  • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 16.01.2026, 04:44
              • Watcom ASM + C puzzle, variable has conflicting addresses - Japheth, 04.01.2026, 05:21
                • Watcom ASM + C puzzle, variable has conflicting addresses - rr, 04.01.2026, 11:40
                  • Watcom ASM + C puzzle, variable has conflicting addresses - bencollver, 04.01.2026, 15:31
                    • Watcom ASM + C puzzle, variable has conflicting addresses - Japheth, 04.01.2026, 16:21
  • Watcom ASM + C puzzle, variable has conflicting addresses - samwdpckr, 02.01.2026, 08:50
    • Watcom ASM + C puzzle, variable has conflicting addresses - bretjohn, 08.01.2026, 21:53