delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/05/25/00:44:49

Date: Wed, 25 May 1994 00:40:00 -0400
From: meetze AT charlie DOT ece DOT scarolina DOT edu (Murle C. Meetze III)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Thanks(RE: paging problems)

Mike Castle said:
 
>When running under windows, windows DPMI server does the memory
>management.  When you malloc memory, it is automatically
>allocated, and if need be, virtual memory is arranged.
>
>When run under regular dos, go32 does the memory management
>(unless you explicitly use a dpmi manager), and doesn't actually
>allocate the memory until you actually use it.  Try using
>calloc() instead of malloc(), and see if the sizes are closer to
>being the same (calloc() just goes through and sets all the
>allocated memory to zeros, so go32 willl then actually allocate
>the memory).
>
>go32's method is more effecient if you often allocate more memory
>than you usually use (such as sparse arrays).  window's method may 
>be more effecient by getting the memory into a contigous file,
>but if access is random, it really won't be much better.
>
>mrc
 
DJ said:
 
>In both cases, just run "go32" and it will tell you how much available
>memory it has for itself.  If you need more than that, you will use a
>paging file.
 
 
Thanks to all who responded your info has helped me greatly, 
and just wanted to say thanks.
 
                                Thanks,
                                MCMIII
                                Murle Cleveland Meetze III
                                meetze AT charlie DOT ece DOT scarolina DOT edu

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019