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: GROUND ZERO™ who wrote (42854)9/4/2004 1:56:05 PM
From: Junkyardawg  Respond to of 110655
 
To run CHKDSK to check for disk errors
On the Windows taskbar, click Start > Run.
In the Open box, type the following:

cmd

Click OK.
At the command prompt, type the drive letter of the drive you want to check (followed by a colon), and then press Enter.
For example, to check drive D, type the following:

d:

Change to the root directory of the drive by typing the following and pressing Enter:

cd
Type the following, and then press Enter:

chkdsk /<switch>

where <switch> is one of the following:
If you want to automatically repair file system errors, use the /f switch (for example, chkdsk /f).
If you want to both repair file system errors and scan for and recover bad sectors, use the /r switch (for example, chkdsk /r).

If you do not specify a switch when running CHKDSK, any errors that are found will not be fixed.
If you are prompted to schedule CHKDSK to run the next time the computer restarts (because CHKDSK may be unable to gain exclusive access to the drive under Windows), type the following, and then press Enter:

y

At the command prompt, type the following, and then press Enter:

exit

If you had to schedule the CHKDSK operation, then restart Windows NT/2000/XP.
While Windows is loading, CHKDSK should automatically run and check the drive that you specified earlier.



To: GROUND ZERO™ who wrote (42854)9/4/2004 1:56:57 PM
From: Junkyardawg  Read Replies (1) | Respond to of 110655
 
Did you get my email? Did you try a systems restore? I would try that before I did anything else.

dawgy