|
-
March 26th, 2002, 06:53 AM
#1
chkdsk keeps auto running
is there anyway of stopping(disabling) chkdsk running at startup it says checking hard disk for consitancy but i have let it run a few times even done the full surface scan but it keeps coming up.
i have also changed the hard disk just in case it was trying to tell me the hard disk was on its way out like scandisk does
p4 1.8ghz
40gb seagate/*maxtor hdd(replacement)
512mb ram
Ntfs file system
Thanx Mike
-
March 26th, 2002, 10:13 AM
#2
Have you tried running it from within the console (say booting from the CDROM or from safe mode)? That solved the problem for me (I had a bad directory in the Temporary Internet Files).
-
March 26th, 2002, 10:19 AM
#3
Well, since this is a feature that is enabled through the registry and triggered by something when Windows isn't shutdown properly, odds are you cannot disable unless you can find the correct registry setting to PERMANANTLY disable it. However, to control the setting while in Windows, you can get to the process of running a checkdisk by the following...
http://support.microsoft.com/search/...;en-us;Q315265
I'm not sure if this will give you any more control than that however. Let me know if this helps.
------------------
Systems Administrator
A+, Net+, i-Net+, CIW-A
MCP/2K, MCP+I, MCSE/NT4
-
March 26th, 2002, 10:29 AM
#4
I believe the "dirty flag" is actually set somewhere in the drive itself (some table about its state). If Windows sees that bit as set, it'll check the drive. I looked around for a program that would remove it, but I couldn't find it, and as it turned out it was a good thing because I did have some errors.
-
March 26th, 2002, 12:24 PM
#5
Still in need of disabling chkdsk. I beleive this PAGE may help
Although I have not tried it, it seems to be somewhat what you are asking.... 
------------------
Who is General Failure and why is he reading my hard disk?
[This message has been edited by CornerPocket (edited 03-26-2002).]
8-ball, cornerpocket.............game! 
-
March 26th, 2002, 03:16 PM
#6
By the way, the way I found out that a folder was corrupted is through a find for a file so if you have some time you might try doing a find for *.* (all files) on the drive and see if any errors or warnings come up.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|