SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?


To: Steven Bowen who wrote (903)11/30/1998 10:06:00 AM
From: PMS Witch  Respond to of 110648
 
"Does that mean these .chk files can or can't be deleted?"

I usually look at what .CHK files contain. If something I recognize as important, I check the integrity of the files where the data belongs and base my actions on what I discover. Most of the time the .CHK files contain unrecognizable data or garbage and I delete them.

Where they come from is a more important question for me. Usually killing some locked program while it's buffers haven't been flushed will leave lost clusters. I run CHKDSK regularly (daily) and find these before it's too late. Often, temporary files leave this junk, and it's no loss to delete.

While developing software, a bug or two will give my system fits and scramble my files and disk. This proves another fertile source of lost clusters. (Stuff I write runs close to the hardware.) Careless pointer manipulations are especially efficient at wreaking havoc.

In short, delete in haste, regret in leisure. Happy experimenting, PW.