From: joemonk64@gmail.com   
      
   > Note that I am running up against the 640k limit    
   > with PDOS/86. The OS and command processor    
   > are taking up 300k or something, and when I    
   > try to run pdmake (which opens another command    
   > processor before running another program), I run    
   > out of memory.    
   >    
   > I refuse to change the fundamental design to try to    
   > alleviate the memory problems, and instead wish to    
   > run the exact (*) same toolchain in either PM16 or    
   > PM32 with the D bit set to indicate 16-bit.    
   >    
      
   Back in the day, when I was doing application work before I got into systems,   
   I wrote code that did accounting for pensions.   
      
   We had one piece of mainline code, and then we had subroutines that did   
   certain parts of the work. We dynamically built the code each time we started   
   a run. In addition, we had code that did file IO, but one of the features of   
   the system was that account    
   numbers could be either 12 or 20 bytes with no change in the code.   
      
   The mainline had hooks (our term), but what they really were was a common API   
   - a well defined interface for passing information among code. Since we were   
   on memory limited systems (most of the time 256K or less), we would swap in   
   and out portions of    
   code that didnt need to be in memory.   
      
   I'd be willing to bet your code is probably suffering from the same issues...   
   You have everything in memory, versus a "resident" portion of the OS that   
   provides services, and swaps in and out portions of code that dont need to be   
   there all the time -    
   passing a buffer among subroutines for input and output as those subroutines   
   are swapped in and out.   
      
   Joe   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)