Stubborn Boot Scandisk

[janshim]

Hello folks,

Lately my XP Pro SP1 machine at home developed a habit of running Scandisk at every warm and cold Boot even though Win XP PRO had been properly shutdown before. I recall some users have encounter such behaviour on their XP too and even after I reinstalled the OS, it is still doing it.

Any ideas how this irritating behaviour can be overcome?

 

[sturm]

Does scandisk find any failures or problems. I know there is a switch to turn off scandisk at boot but cant remember where it is. Ill look to see if I can find it.

 

[Toejam31]

<A HREF="http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/chkntfs.asp" target="_new">Chkntfs</A>

Toey

<A HREF="http://forums.btvillarin.com/index.php?act=ST&f=41&t=328&s=91c282f2e5207e99b7a652ee13b3512a" target="_new"><font color=green>My System Rigs</font color=green></A>
___________________________________________

<A HREF="http://forums.btvillarin.com/" target="_new"><b><font color=purple>BTVILLARIN.com</font color=purple></b></A> - <i><font color=orange>Your Computer Questions Answered</font color=orange></i>

 

[jmecor]

you might be using ntfs partition.

<font color=green>If your nose <b>RUNS</b>, and feet <b>SMELLS</b>.
Then you must be born <b>UP-SIDE DOWN</b>.</font color=green>

 

[janshim]

When I had the problem I was running FAT32. I have since upgraded to NTFS and the problem disappeared. Still, it remains a mystery. I have just purchase a Hitachi 7200 rpm 7k6 60GB disk for my other laptop. Will be interesting to see how well it performs.

 

[nach]

Reformat the disk thats being scanned.

The disk could be marked as dirty, or in fault tolerant terms, kaput.

 

[goblinking]

FAT32 can get file errors on it when incorrectly shut down (even if it *appears* to have shut down correctly) which cause Windows to want to scandisk at the next opportunity, i.e. during reboot.

Windows XP seems to load too much of itself before trying to scandisk, so that it can't successfully scandisk (since the files it's trying to scan are in use), and instead gives up and marks the drive for scandisking NEXT boot. Which can go on for ever.

NTFS however is a completely different file system, and due to its architecture is not susceptible to these particular file errors, which is why it doesn't try to scandisk now that you've changed to NTFS.