XPost: comp.os.msdos.programmer   
   From: nomailings@nospicedham.trgzxcqvbe.cpm   
      
   On Mon, 28 Oct 2019 08:29:49 +0800   
   Johann 'Myrkraverk' Oskarsson    
   wrote:   
      
   > On 27/10/2019 4:23 pm, Rod Pemberton wrote:   
      
   > > Other than the typo, I'm assuming these have no effect, and that the   
   > > problem is the zero padding at the start of the .com since the   
   > > binary code is the same otherwise.   
   >   
   > Thank you.  I can get rid of the zero padding by simply dropping the   
   > "org 100h" from the source.   
      
   No.  You need that for the correct offsets within the binary   
   instruction encodings.   
      
   > That tweak, along with adding "public main" and "op start=main" to   
   > wlink to get rid of the warning don't seem to change anything.  The   
   > program still runs and switches the graphic mode, then just sits   
   > there waiting until I turn off DOSBox-X.   
      
   If I do "public main" "op start=main", and keep the "org 100h", and the   
   other tweaks I posted, then the assembled .com code disassembles   
   exactly the same as NASM code.  There is no 100 bytes of padding, and   
   it exits with ESC when run.  Neither seem to do anything with graphics   
   here.   
      
   > I was wondering if the problem is with my stack settings (none) but   
   > at the moment I don't know how to explicitly set a stack.   
      
   The issue seems to be that you need the link tweaks you posted above   
   plus "org 100h".   
      
   Good luck,   
      
      
   Rod Pemberton   
   --   
   Why are humans trying to un-bias A.I.?  That's a human bias.  Humans   
   don't want pure A.I.  What humans want is slave-A.I.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)