Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!samsung!cs.utexas.edu!rutgers!uwvax!astroatc!vidiot!brown
From: brown@vidiot.UUCP (Vidiot)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Stumpers
Message-ID: <385@vidiot.UUCP>
Date: 5 Jan 90 19:09:43 GMT
References: <21990002@hpvcfs1.HP.COM>
Reply-To: brown@vidiot.UUCP (Vidiot)
Organization: Vidiot's Hangout
Lines: 30

In article <21990002@hpvcfs1.HP.COM> rexw@hpvcfs1.HP.COM (Rex Wickenkamp) writes:
<
<1)  I have access to a Compaq 386/20e.  This Compaq seems to have a problem
<    when exiting out of applications, as it will show an empty screen for
<    approximately 15 seconds, before returning to the DOS prompt.  Does
<    anyone have any ideas what I can use to check this puppy out?

I have such a beast and have never had this problem.

<2)  I have always wondered why CHKDSK, when used with the /F parameter,
<    creates FILE0000.CHK files in the root directory.  Can anyone give me
<    a good explanation of this?

When there are files allocated on the disk and there isn't a directory
entry to go along with it, CHKDSK makes such an entry.  To only real place to
put it is in root.  Before you ask how files can end up not having a directory
entry, but still have space allocated in the FAT, I will try and answer that.
The answer is:  I don't know.  I have seen programs screw up, like compilers,
that somehow leave FAT entries there but, the directory entries are gone.

What to do.  Well, look in the file created and see if it is worth anything
or if it is left-over junk.  If junk, delete it.  Otherwise rename it and
put it where you want.

Oh, why are these files created?  Well, it is to give you, the user, a chance
to see if the data recovered is worthless or not.
-- 
      harvard\     att!nicmad\              cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/  decvax!nicmad/   INTERNET:<@cs.wisc.edu,@astroatc:brown@vidiot>