Date: Wed, 5 Jan 2000 11:11:28 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Ben Hussey cc: djgpp AT delorie DOT com Subject: Re: need help with DJGPP 2.01 In-Reply-To: <000a01bf570e$d7de6c20$a91409d2@user> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Please don't post in HTML. On Wed, 5 Jan 2000, Ben Hussey wrote: > The problem I have is that the compiler only works intermittently for = > EXACTLY THE SAME command. > Sometimes there is no problem with compilation but most of the time it > says "no such file or directory". This might mean some hardware-related problem. GCC is a memory hog, and it moves large buffers around quite a lot. I actually use compilation of a large source (run several times) as a good way of finding bad memory chips and incorrect CPU cache settings ;-) Did you per chance overclock your motherboard? For that matter, what hardware do you have in your system? > The cause I can think of is the DPMI swap space but I don't have any > idea about what it does. I can hardly believe that the swap space has anything to do with this. This would be the last factor I'd think about. > config.sys > --------------- > > DEVICE=C:\ECS\ECSCDIDE.SYS /D:ECSCD003 What is this device driver? Does it have something to do with the hard disk? > OUTPUT from go32-v2.exe > ---------------------------------- > go32/v2 version 2.0 built Nov 15 1998 14:36:43 > Usage: go32 coff-image [args] > > DPMI memory available: 24587 Kb > DPMI swap space available: 4997 Kb You have about 30MB of DPMI memory. I don't see how can this ever be not enough for a compilation. > Output from compilation: (gcc -c -v for.cc) > ------------------------------------------------------------ > gcc.exe: for.cc: No such file or directory (ENO ENT) > gcc.exe: No input files What does "dir for.*" print in that directory?