Path: utzoo!attcan!uunet!aplcen!haven!umd5!brianf
From: brianf@umd5.umd.edu (Brian Farmer)
Newsgroups: comp.windows.ms
Subject: Re: how not to develop in SDK
Message-ID: <7471@umd5.umd.edu>
Date: 25 Oct 90 17:50:32 GMT
References: <5270@crash.cts.com>
Reply-To: brianf@umd5.umd.edu (Brian Farmer)
Organization: University of Maryland, College Park
Lines: 23

In article <5270@crash.cts.com> alen@crash.cts.com (Alen Shapiro) writes:
>Did you know (and not a lot of people know this :-)) that...
>
>You can't be in the MSWindows 3.0 environment and compile an
>MSC 6.0 program so that you can remain in the environment
>while you compile-debug your windows application (SDK).
>The compiler runs out of heap space!!
>
>nmake when run from a DOS-PROMPT within windows 3.0, hangs
>my PS2/80 (4Mb RAM DOS3.3).


Make programs have a habit of eating memory.  Try the following makefile:

hello:
	chkdsk

After this finishes run chkdsk from the dos prompt.  This difference will
show you about how much memory is being eaten by Make.  For me nmake ate 
about 118K.  An expensive option might be polymake which is able to remove
all but 4 or 5K from memory when it runs another program, I use this
program for my making.  Or you might be able to use the /N option to build
a bat file which you run after nmake is finished.