Date: Tue, 3 Feb 1998 11:47:03 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "David W. Coppit" <dwc3q AT mamba DOT cs DOT Virginia DOT EDU>
cc: djgpp AT delorie DOT com
Subject: Re: slow startup on less (lss332b.zip)
In-Reply-To: <Pine.SOL.3.96.980202120304.13773A-100000@mamba.cs.Virginia.EDU>
Message-ID: <Pine.SUN.3.91.980203114643.21682N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 2 Feb 1998, David W. Coppit wrote:

> I was having the same delays when I did a simple command like "less
> textfile". It was 13 seconds before the cursor went to the next line in
> response to my pressing enter to execute the command, then 1 seconds to
> see the information. This made me think that it was a Window 95 problem
> instead of a djgppp problem.
> 
> I went to the properties for the bash window, and changed the dpmi memory
> setting from auto to 3072, and now it works fine. Evidently, Windows was
> taking some time to allocate the memory.

Incredible!  So what you say is that the "auto" setting was leaving
less than 3MB of DPMI memory to the programs run inside DOS box?  Can
you confirm it by restoring the "auto" setting, running go32-v2.exe in
the DOS box and posting what it prints?

Until now, it was known that you must change the "auto" setting to get
to the maximum of 64MB, but AFAIK nobody have ever reported such a
small amount of memory being available by default.

How much physical RAM do you have installed on that machine?