From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Maximising conventional memory for shelled program
Date: 23 May 2001 13:15:22 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 21
Message-ID: <9egd5a$g1e$1@nets3.rz.RWTH-Aachen.DE>
References: <56a3c75f DOT 0105230150 DOT 75217dd4 AT posting DOT google DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 990623722 16430 137.226.32.75 (23 May 2001 13:15:22 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 23 May 2001 13:15:22 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

John Argyle <john DOT argyle AT harwellinst DOT com> wrote:
> I'm trying to maximise the amount of conventional (below 640k) memory
> for a program that I 'shell' from a DJGPP program using the system
> library function. Operating system is MSDOS 6.22. It seems that the
> DJGPP program takes about 92k of conventional memory, estimated by
> taking the difference between a 'mem' command typed at the DOS prompt
> and one shelled from my program. I'm using the CWSDPMI extender. Any
> ideas welcome.

There's nothing much you can do to reduce that footprint any further
Those 92K are mostly CWSDPMI. Shell out and try "mem /c /p" to see it.
It's not the actual DJGPP program, but the DPMI provider that's eating
most of the memory.  In principle one could swap (large parts of)
CWSDPMI itself to high memory, too, but that's not implemented, AFAIK.

The only other thing you could do would be to change parameters of
CWSDPMI to reduce the size of memory tables. But most of those 92 K
are irreducible.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.