Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!ames!sdcsvax!ucbvax!ucsfcgl!socrates.ucsf.edu!kneller
From: kneller@socrates.ucsf.edu (Don Kneller%Langridge)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft C 4.0 spawn is a memory hog
Message-ID: <10224@cgl.ucsf.EDU>
Date: Wed, 27-May-87 14:29:14 EDT
Article-I.D.: cgl.10224
Posted: Wed May 27 14:29:14 1987
Date-Received: Sat, 30-May-87 01:56:21 EDT
References: <3605@osu-eddie.UUCP>
Sender: daemon@cgl.ucsf.edu
Reply-To: kneller@socrates.ucsf.edu.UUCP (Don Kneller)
Organization: UCSF Computer Graphics Lab
Lines: 21

In article <3605@osu-eddie.UUCP> mdf@osu-eddie.UUCP (Mark D. Freeman) writes:
>We have a program called memfree.exe that just prints out the
>available memory.  Memfree always agrees with chkdsk. 
>
>We wrote a program that does nothing but spawns memfree and returns.
>Running memfree from dos shows 70K more available than running memfree
>from our spawn test program (that is, of course, running under dos). 
>
>Why does spawn eat up 70K?  Is there a way around this?

By default, small model programs get 64K of data space.  This can be
reduced to a minimum by using the /CP (can't recall the full name -
CPARAMAX?) switch of the linker.  Use /CP:1 and LINK will figure
out how much to actually allocate.

Alternatively, "exemod memfree.exe /min 1 /max 1" should also do it.
-----
	Don Kneller
UUCP:	...ucbvax!ucsfcgl!kneller
ARPA:	kneller@cgl.ucsf.edu
BITNET:	kneller@ucsfcgl.BITNET