DOS ain't dead

How to set an .EXE stack segment same as the code segment? (Developers)

posted by ecm  , Düsseldorf, Germany, 09.03.2018, 13:11

During some work on RxCMD, I noticed that the original reference file has exeInitSS = 0 and exeInitSP = 0 too. That means the stack lives at the end of the (64 KiB) first segment of the file. exeMinAlloc doesn't cover this usage, even though it should.

It appears that these settings are the defaults when no stack segment is specified. Using WarpLink, it is the case that both fields as 0 are the default (which also displays a warning).

Now, I wanted to explicitly set the stack as a segment, but I can't seem to get WarpLink to put the stack into the same segment as the code segment. I tried naming a group (as "dgroup") and including both the RXCMD segment and the STACK$$ segment into that, and also tried setting the "class=" of the stack segment to RXCMD (same as the code segments), but alas. In the NASM source text, I need to specify the "stack" attribute to the "segment" instruction, which tells the linker that this is the stack segment.

Anyone got any ideas?

---
l

Complete thread:

• How to set an .EXE stack segment same as the code segment? - ecm, 09.03.2018, 13:11 (Developers)
  • How to set an .EXE stack segment same as the code segment? - ecm, 09.03.2018, 14:13
  • How to set an .EXE stack segment same as the code segment? - alexfru, 10.03.2018, 06:35