Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!njin!njitgw.njit.edu!hertz.njit.edu!tdg1465
From: tdg1465@hertz.njit.edu (tod gordon cccc)
Newsgroups: comp.os.msdos.programmer
Subject: Help! Microsoft C program size problem!
Message-ID: <1991May30.184120.11980@njitgw.njit.edu>
Date: 30 May 91 18:41:20 GMT
Sender: news@njit.edu
Organization: New Jersey Institute of Technology, Newark, N.J.
Lines: 16
Nntp-Posting-Host: hertz.njit.edu

We are working on a program that requires about 300-310K to start,
before heap allocations begin. I notice that Microsoft C 6.0, which
we now use (with their linker), allocates 64k above what is quoted
in the .EXE file header. Reasonably, it should use this for something
like heap space, but at least 47K of it never gets used - the heap
allocations begin above this. If I compile with Borland C++, this
kind of waste doesn't happen, but we can't use Borland's compiler
for development now.

This 64K addition is mentioned in the linker documentation as being
added by the startup module as a minimum (see /CP option). We need
all the heap space we can get, and can't afford this kind of waste.
Is there a way around this?

----------
Tod Gordon (tdg1465@hertz.njit.edu)