Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!delta.eecs.nwu.edu!olsen
From: olsen@delta.eecs.nwu.edu (Jeff S. Olsen)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Memory requirements for Borland C++
Message-ID: <16888@accuvax.nwu.edu>
Date: 26 Feb 91 23:31:57 GMT
References: <1991Feb25.103801.2994@waikato.ac.nz> <1771@pdxgate.UUCP>
Sender: news@accuvax.nwu.edu
Organization: EECS Department, Northwestern University
Lines: 16

In article <1771@pdxgate.UUCP> dmatlock@eecs.cs.pdx.edu (Delbert Matlock) writes:
>I'm running Borland C++ on a 386 with 4MB of memory.  I originally set up the
>PIF file to only give BC 512K of expanded memory.  BC took nearly 20 minutes
>to compile and link one of the sample windows programs.  When I ran the EMS up
>to 1.5MB, compile and link time came down to under two minutes.  So, I guess 
>you could run BC on a 1 Meg machine, but pack a lunch.

Did you recompile the same program the second time?  If so, did you
remove any pre-compiled headers that might have been generated during
the first compile?

Jeff Olsen
olsen@eecs.nwu.edu

"Simple explanations are for simple minds. I've got no use for either."
   - Joe Orton, "What the Butler Saw"