From: not@any.adr   
      
   On Mon, 27 Sep 2004 02:34:03 -0500, Glenn Someone   
    wrote:   
      
   >OK I am waiting for good suggestions still, at least that I can   
   >understand in the scope of what I'm trying to do.  It seems it comes   
   >back to this.  Please elaborate, because I'm not understanding how   
   >this is going to fit my requirements I've already stated in this   
   >thread, especially in a multitasking system as people have kept going   
   >on about.   
      
   Ok, lets give this one last try...   
      
   The only "requirement" I've seen posted involved a loop that would soak up   
   every last bit of remaining memory... an absolute no no in a multitasking   
   environment.   I've three times suggested that you change the memory   
   allocation strategy in that program to a) allocate memory only when needed and   
   b) release memory as soon as you are done with it.  Several others have given   
   you practically the same answers in different ways...   
      
   So, please tell me...   
      
   	1) Exactly what is it this program does?   
   	2> Why does it need to sop up so much memory?   
   	3) How much memory does it actually need?   
   	4) Why can't it be re-written to play nice in a windows environment?   
      
   I just can't get beyond the distinct impression this is one of those cases of   
   "If it's thee I want it".... so your program sops up 512megs of ram, just   
   because it can, then only allocates 36 bytes to dynamic variables.   
      
      
   -----   
   Laura   
      
   (http://www.start.ca/users/ldblake)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)