From: mlarch AT ix DOT netcom DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Fallowup -- slow dos, fast win95 linking
Date: Tue, 31 Dec 1996 08:27:24 -0500
Organization: Netcom
Lines: 26
Message-ID: <32C914BC.6E3A@ix.netcom.com>
NNTP-Posting-Host: frd-md1-18.ix.netcom.com
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

earlyer I'd written ...
> 
> With a rough timmer I got 78.6 seconds in dos
> compared to 11.5 seconds in a dos window under
> win95. What causes this ? In both cases TMPDIR
> points to a 16meg ram disk. Under dos qemm is
> serving up memory. The *.o files passed to make
> total less than 8k


As it turns out, Eli was right on with this appreciated
response:
> The most probably cause is that you didn't set up a disk cache in MSDOS.  
> Please read section 3.9 of the DJGPP FAQ list (v2/faq202b.zip from the 
> same place you get DJGPP) for advice on optimal system configuration for 
> DJGPP.
>
> Another cause might be that you don't let DJGPP use enough memory in 
> MSDOS.  What does go32-v2 print when invoked with no arguments?

The disk-cache line in my autoexec.bat file was REM'ed out. Restoring
that
fixed the problem and the link time is back down to 10.2.

Thanks to everyone who responded,
mlarch AT ix DOT netcom DOT com