Date: Mon, 14 Aug 2000 00:18:48 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: neldredge AT hmc DOT edu Message-Id: <9743-Mon14Aug2000001848+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b CC: djgpp AT delorie DOT com In-reply-to: <83sns9ughl.fsf@mercury.bitbucket> (message from Nate Eldredge on 13 Aug 2000 12:07:50 -0700) Subject: Re: Borland 4.5 C/C++ compiler problem References: <8n65c7$708 AT nntp DOT seflin DOT org> <83sns9ughl DOT fsf AT mercury DOT bitbucket> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Nate Eldredge > Newsgroups: comp.os.msdos.programmer,comp.os.msdos.djgpp > Date: 13 Aug 2000 12:07:50 -0700 > > Does DJGPP set the hidden or system bits on anything? No, of course not. > This is the usual reason for immovability wrt defragmenters, IME. > Hmm... swapfile? Too many unmovable clusters usually mean lost or cross-linked clusters and other similar calamities. One should run CHKDSK or SCANDISK (or similar tools) before running the defragger. DJGPP programs can leave lost clusters behind them if a program uses up more RAM than is physically available, starts paging, and then crashes. The parts of disk used by CWSDPMI for a swap file become lost clusters. I usually run CHKDSK right after the crash.