From: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Virtual Memory Exhausted
Date: Tue, 16 Sep 1997 15:35:22 -0400
Organization: Cornell University
Lines: 27
Sender: asu1 AT cornell DOT edu (Verified)
Message-ID: <341EDF7A.560D@cornell.edu>
References: <341e124d DOT 11267294 AT news DOT virgin DOT net> <341D69F3 DOT 703A AT cornell DOT edu> <341f83c9 DOT 872231 AT news DOT virgin DOT net>
Reply-To: asu1 AT cornell DOT edu
NNTP-Posting-Host: 128
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Matthew Winter wrote:
> 
> I have tried
> 
>    1. Removing the optimisation all together.
>       This causes the MSDOS shell to terminate with a GPF
>    2. Set the TMPDIR for use with CSWDPMI. Done this, tried it under
>       real DOS, and I get a page fault error message from CSWDPMI
>    3. Increased the Min Stack of CC1.EXE using STUBEDIT to (1024K)
>       This bypassed the virtual memory error, but produces the same
>       as one. GPF for the DOS box
>    4. Now tried section 15.6, increasing the DPMI setting to 64Mb for
>       the MSDOS shell.
>       This also bypasses the virtual memory problem, but causes the
>       DOS box to GPF.
> 
> The GPF has the following details provided by Win95
> 
> Fault Location: 0117:EFDD4
> Interrupts in service: None
> 

double hmmmm. did you run scandisk on this drive recently? and, as
another person suggested, how is the space on this drive? finally, are
you positive your system is not infected?

  -- Sinan