From: mobygamer@nospicedham.gmail.com   
      
   On Monday, October 29, 2018 at 7:47:34 AM UTC-5, R.Wieser wrote:   
   > I've solved the problem (both the memory gobbling as well as the initial    
   > stack location) by patching, after generating the executable, the relevant    
   > fields in the EXE file header.   
      
   The real solution to your problem was to assemble and link a .COM file.  There   
   is no point to a tiny model .EXE file, as the tiny model doesn't allow for   
   multiple segments which is the problem .EXE files were designed to solve.  In   
   a .COM file, DOS loads    
   and sets up the environment directly as you requested in your first post (with   
   SS=CS, and SP=FFFE).   
      
   If you are following the code, data, data-uninitialized model then you should   
   also define a stack segment, but I didn't see that in the previous messages.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)