Text 6957, 68 rader
Skriven 2005-04-16 09:17:02 av Jeff Guerdat (1:106/2000.0)
     Kommentar till en text av Jason Lamb
Ärende: XP Defrag amd Error Chec
================================
On 04-15-05, Jason Lamb said to All:

JL>I discovered that ScanDisk is no longer used. Instead XP uses an updated
JL>version of Chkdsk. I used it via command prompt. It says there is an error
JL>with the file system and use chkdsk /fix to fix it. I then right-click the
JL>drive and selected tools > error checking. It does not report any
JL>problems. I did not select the 2 options (don't remember the option
JL>names). Whick program should I rely on.

They are one and the same.  What differs is how you access them.  Use CHKDSK
/F - it will prompt you that it can't lock the disk and would you like it to
run on the next reboot.  Answer yes and reboot - it will run after the Cylon
screen and before the full graphical screen shows.  If you run NTFS, it will
reboot again after running.

Another alternative is to install the command console and run chkdsk from
there.  To install, use a DOS prompt to cd into the location of the XP install
files (might be on the hard drive in c:\i386 or use the CD) and use the
following command line:

winnt32 /cmdcons

It takes ony a few seconds to run and will 1) add a new hidden directory,
c:\cmdcons, and 2) add an entry to boot.ini to give you a selection to the
boot menu.

To use this, reboot and choose the command console entry.  this will end up in
a DOS-like environment (you'll get prompted to choose the XP installation,
even if there's only one installed and will be prompted for the
administrator's password - reset it to something you know before rebooting if
necessary).  You can type "help" to see what commands are available.  To check
the disk, use "chkdsk /p" (note the different option! - no idea why they
thought that was necessary).  This allows the disk to be checked without the
extra prompts and reboot.

JL>Also, I read on some message boards that peoples hard drive are failing
JL>after using defrag or error checking. Has anyone heard of this? Is this a
JL>coincident or is there a problem with XP defrag or error checking program?

Definitely coincidence.  The file system may be so messed up that chkdsk can't
fix it properly, leading to the "failed" drive diagnosis.  I've use chkdsk on
a too regular basis when the OS was screwy, causeing spontaneous reboots, and
have never had a drive problem.

JL>I have had this system for almost 3 months. I have not used defrag yet amd
JL>used error-checking and chkdsk twice. How often is it neceesary to run
JL>these programs on an XP SP2 system with a NTFS. I know that it was a good
JL>idea to run the program on a 98SE system quite often.

I see a need to run chkdsk only after an unclean shutdown/crash.  Since you
need to reboot to get it to work in any event, it's enough of a pain to run it
only then.

I defrag on a semi-weekly basis but I don't use the built-in defrag since it
can't be scheduled (AFAIK).  I've been using Perfect Disk which Charles S.
recommended.

JL>Btw, There are new critical updates available on Windows Update. I believe
JL>there are 6 of them.

It's important to keep up-to-date...


___
*Durango b211 * DurangoMail for Windows NT/9x

--- Maximus/2 3.01
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)