Text 9682, 29 rader
Skriven 2005-07-18 07:37:00 av JEFF GUERDAT (1:123/140)
     Kommentar till en text av JASON LAMB
Ärende: XP Chkdsk
=================
On 07-16-05, JASON LAMB said to ALL:

JL>I discovered something interesting. I open the command prompt window and
JL>ran Chkdsk. I use the command "chkdsk c:". It was in 3 stages. After it
JL>finished. Here is what it said: Correcting errors in the volume bitmap.
JL>Windows found problem with file system. Use chkdsk with the /f (fix)
JL>option to correct these.

JL>I then used chkdsk c: /f and answered yes to schedule on next restart. I
JL>then restarted my system and chkdsk ran. When Windows started, I opened
JL>the command prompt window and ran chkdsk c: again. No errors reported.

JL>After using the computer for a little while I decided to run chkdsk c:
JL>again. This time the error is back. The same message as the first time.

JL>Why? Is there a known problem with chkdsk? The system seems to be running
JL>just fine. Does anyone else have this problem? What should I do? Should I
JL>ignore it?

Nothing is wrong.  It's a dynamic file system (stuff is always in use).
That's why the reboot was required - the file system needed to be quiet.  The
check during the session showed that not everything was ok, probably becuse
the OS had cached information rather than having it writen to disk yet.  I
never bother with a chkdsk when live - it's bogus...


---
*Durango b211 * DurangoMail for Windows NT/9x
 * Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140)