Ok, so what exactly is the most intelligent way to allocate memory if you
don't know exactly what you requirements will be?  Apparently malloc isn't
giving me any single allocations larger than 32K (Watcom v.10.0), so I guess
that I have to use DosAllocateMem, assign this memory with DosSubSetMem, 
and then allocate it with DosSubAllocMem.  However, how do you decide on 
how much memory to initially allocate?  Should you just pick a goodly large 
number (say, 100Meg) leaving the memory uncommitted till you need it, then 
grow the suballoced heap?  Should you take the 512Meg that your application 
is limited to?  Or should you pick a smaller amount to allocate, based on 
calculations that I don't know about?  
   Do you handle memory differently depending on the application?  For 
instance, one of my applications will have sets of linked lists (the length 
of which I don't know) where memory will be allocated in lots of tiny chunks.
Another application will have large bitmapped images, eating up 200k+ chunks
each.  Is it better to use suballocated memory in one case and plain old
nonshared memory in another?

  Thanks to all who are wading through my various posts.  I'm in the process
of joining the Developers' Assistance Program, and then I will get the 
Developer's Connection CD subscription.   However I'm guessing it is going 
to be a month or more before I get all of that ironed out.  *sigh*

Still trying to learn OS/2,
Michael Duffy

... ARRRRRGGGHHH!!!! ... Tension breaker, had to be done.
--- GEcho 1.10+