From: muta...@gmail.com   
      
   On Wednesday, July 14, 2021 at 1:36:08 AM UTC+10, wolfgang kern wrote:   
      
   > >> but you may need at least two selectors per 64K block, one   
   > >> for code and one for data (some folks have third for stack)   
   >   
   > > Is there a reason I can't just have on selector for each   
   > > 64k block?   
      
   > you can have that, but either 64K code only or 64K data only.   
   > but application code usually need both within one 64 K block.   
      
   I see. That's not very nice. But given that the selectors   
   don't start from a neat 0 anyway, I guess pairs are OK.   
      
   The assembler generated from C code in the huge memory   
   model will not care. It just needs to know how much to   
   increment the "segment" (selector) whenever it crosses   
   a 64k boundary.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)