Xref:	news2.mv.net comp.os.msdos.djgpp:7730
From:	david DOT faure AT bbsrc DOT ac DOT uk (David Faure)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: lots of disk access when linking?
Date:	21 Aug 1996 07:03:58 GMT
Organization:	BBSRC
Lines:	23
Message-ID:	<4veccu$57p@is.bbsrc.ac.uk>
References:	<01bb8ef5.847655a0$06020690 AT cam DOT utas DOT edu DOT au>
NNTP-Posting-Host:	pc0570.sri.bbsrc.ac.uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <01bb8ef5.847655a0$06020690 AT cam DOT utas DOT edu DOT au>, "Ryan Boyes" 
<rboyes AT postoffice DOT newnham DOT utas DOT edu DOT au> says:
>
>Whenever I compile and link any source(usually from rhide) there is a 
lot
>of accessing the HD. The classic "Hello World" source takes up to two
>minutes to compile and link. Isn't this a bit long?
>
>Also, the available memory, in the top right hand corner of the IDE does
>not change during the compile/link process (should it?). This suggests
>that the process is relying exclusively on the TMPDIR that is set in my
>autoexec.bat. Is there an option for gcc that I should set to get gcc to
>utilize my 16Mb of ram?
>

Hello Ryan,

I think you should call a program like SMARTDRV to "cache" some 
disk-accesses. If you don't use it at the moment, you should just add it 
to your autoexec  (see FAQ for optimal configuration of Smartdrv....)

Hope this helps
David.

- Raw text -