From: muta...@gmail.com   
      
   On Monday, July 12, 2021 at 12:13:48 AM UTC+10, wolfgang kern wrote:   
   > On 11.07.2021 09:38, muta...@gmail.com wrote:   
   > ...   
   > > I'm using normal RM16, not unreal.   
   > > I want a solution that works on the 8086.   
      
   > you posted an alloc option >64KB. even possible with   
      
   Note that MSDOS already provides this, and things like   
   executables require that, since executables can be   
   greater than 64k.   
      
   > two merged 16 bit registers you'll break your nails   
   > on the required overhead for consecutive blocks fit.   
      
   Can you elaborate on this? PDOS/86 huge memory   
   model is still only theoretical. I am determined to   
   make this code:   
      
   https://sourceforge.net/p/pdos/gitcode/ci/master/tree/pdpclib/__memmgr.c   
      
   which was a general-purpose memory-manager for   
   use on the original MVS/380 (where the OS wouldn't   
   manage memory above 16 MiB for you - the app had   
   to do that itself), work as the memory manager for   
   PDOS/86, no matter how many gerbils need to die.   
      
   > OK I see, you want an 8086 with 32 bit addressing :)   
      
   I want an 8086 with 20-bit addressing, an 80286 with   
   24-bit addressing, and a theoretical x86 processor with   
   32-bit addressing. Come to think of it, it might be possible   
   to use an actual 80386 to do effective 16-bit segment   
   shifts. Or surely I can at least match the 80286 and do   
   (effective) 8-bit shifts. That would be a load of fun.   
   I guess it depends how many selectors I can define on   
   the 80386. I'll run everything in supervisor mode, so I   
   can use both GDT and LDT if that helps.   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)