From: muta...@gmail.com   
      
   On Tuesday, July 13, 2021 at 3:56:37 PM UTC+10, wolfgang kern wrote:   
      
   > and any valid selector can start at any address within 4GB.   
   > (but any means aligned to bounds here) the selector number   
   > got nothing to do with the address it is pointing to !   
      
   There is no point going above 1 GB when I am   
   doing 16-bit programming.   
      
   > selector 0 is invalid   
   > first usable selector number is 8 which is also the offset   
   > in the GDTable (numbers 9..15 are same but restricted PL)   
   > next usable is 0x10 and so on   
      
   Oh, ok. That's fine. I can live with that. I just need to   
   make the rules for huge pointers that when you   
   cross the 64k boundary, the segment gets incremented   
   by 0x10 or whatever.   
      
   > 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?   
      
   > So even if you fill the GDT with max possible entries:   
   > last will be 0xFFF8, that means (65536-8)/16 = 4095 pairs   
      
   Ok.   
      
   > hope you realize that your GDT use a full 64K block by itself.   
      
   That's fine. That's peanuts for what I'm doing.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)