Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,673 of 4,675    |
|    R.Wieser to All    |
|    Re: EXE program stack setup questions    |
|    13 Nov 18 22:45:37    |
   
   From: address@nospicedham.not.available   
      
   Jim,   
      
   > The real solution to your problem was to assemble and   
   > link a .COM file.   
      
   No, it was-and-isn't.   
      
   > There is no point to a tiny model .EXE file   
      
   Yes, there is. There are a couple of load-time differences between the two.   
      
   > as you requested in your first post (with SS=CS, and SP=FFFE).   
      
   No, I didn't *request* that. Twice (you're mixing up .COM and .EXE style   
   stacks). It *causes* SP to become zero [1], meaning its 64 KB away from   
   the start of the program - leaving a *big* hole between the end of the   
   program and the bottom of the stack. which I don't want.   
      
   [1] for method #1   
      
   > 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.   
      
   Than I suggest you re-read my initial (thread-starting) message again. My   
   description for method #2 literally starts with "Use a ".stack {size}"   
   definition".   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca