scandisk used to run automatically on WINME

  • Thread starter Thread starter Ignacio C.A.
  • Start date Start date
I

Ignacio C.A.

Hello everyone!
I remember that whenever Windows ME was unappropiately shutdown, Scandisk
would run automatically on the next boot.

This doesn't happen on WINXP. does this mean that there is no need for it?
Should I do it manually if i ever shutdown unappropiately?
How can I enable it to run automatically when there is a need for it?

Thank you!
 
Ignacio said:
Hello everyone!
I remember that whenever Windows ME was unappropiately shutdown,
Scandisk would run automatically on the next boot.

This doesn't happen on WINXP. does this mean that there is no need
for it?
Click to expand...

There is no need for it to run every time.
Should I do it manually if i ever shutdown unappropiately?
Click to expand...

Nope, it won't hurt if you do this but there is no need to be as paranoid as
Windows ME was.

You should maybe consider running the disk scanning tool (called chkdsk,
short for 'check disk' in XP) every now and again as part of general
maintenance and care of your computer, and obviously any time you suspect a
hard disk problem, but beyond that i wouldn't worry.
How can I enable it to run automatically when there is a need for it?
Click to expand...

It is already able to run automatically when it feels that it needs to. You
don't need to do anything else.

--
--
Rob Moir, Microsoft MVP for servers & security
Website - http://www.robertmoir.co.uk
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html

Kazaa - Software update services for your Viruses and Spyware.
 
First. XP does not have scandisk, it has chkdsk.exe, also called Error
Checking.

Go here:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Read the instructions at the top of the page.
Scroll down to:
82. Disable or Enable Check Disk Upon Boot
-----------

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"SFCScan"=dword:0000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
"AutoChkTimeOut"=dword:0000000a
----

Scandisk has been retired. Use Error Checking (chkdsk.exe) in XP.
1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Do one of the following:

o To run Chkdsk by using the /f parameter, select the Automatically fix file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]

You have to reboot for Error-checking to run.

For a peek at the log.
Start | Run | Type: eventvwr | OK
Look in Application | Listed as Information
under Winlogon, Event 1001
 
XP uses chkdsk instead of scandisk - also if your XP install is using
NTFS file system instead of FAT/FAT32, then NTFS is a more robust,
self-repairing than FAT/FAT32, therefore it fixes itself for minor
problems, where Win9x/ME needed scandisk to fix. Rarely have I seen
chkdsk run after an improper shutdown, but when it did, well it wasn't
pretty afterwards and we came to assume the drive was on its last legs
anyway - especially after recovering the event logs and seeing man
SMART errors being recorded.
 
Back
Top