Printable View
Seem to be getting this a lot ... whilst not really a problem what the hell am I doing that's causing this ?
'a disk check has been scheduled' to appear on every bootup - not just xp but w2k too.
& I ain't telling it to do it !!!! ( I will have 'historically' but not since the last time I booted)
Pressumably I have some orphan key floating about in my registry that isn't gettting got rid of after completion ? So ....
It's all those dodgy apps you keep running -ed :p
Have you considered that you might have a disk problem that windows is picking up?
Of the 'affected' systems, two have multiple drives which I do tend to pull 'in & out' frequently ;) ... so up untill this point I was guessing as you have ... but then I realised it did it every boot, despite having 'sucessfully' completed before, & on ones that only have one drive (so I can't have been messing with them ! :D)
Most puzzled ... I figure though thats there is a key which fires this - something does !
(I've got a new system set up here, with a virgin xp pro install & nothing else - now that's doing it ! - though its been 'on' my network to get updates - mmmm maybe I have some 'nasty' lurking ??? (though what the hell wants to run checkdisk for me ? - that seems 'friendly' not malicious !)
Arrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr rrrrrrrrrrrrrrrrrrrrrrrrrrgh ! suss-ed it .... mobsync.exe was present on 'em all ... so offline files & caching somehow confus-ed it into thinking they should be present locally & weren't always (I have all the patches etc saved locally for 'ease of use' {sure this made it easy 'ed didn't it ? :rolleyes:}) - another lesson learnt the hard way :knife: :D
Thanks anyway Gary ;)
Quote:
Originally Posted by gazzak
:thumbs2: :thumbs2: :thumbs2: :thumbs2: :thumbs2:Quote:
Originally Posted by confus-ed
Ah so you are coming around to my way of thinking then ? :D -mobsync.exe being the synchronisation tool for windows that M$ windows is itself a 'nasty' ! :devil:
I'm not clear what the answer was. I have the same problem. How do I fix it?Quote:
Originally Posted by confus-ed
Quote:
Originally Posted by dr g
Welcome to Windrivers Dr g
One thing is for sure, Ed probably did it the confus-ed way!
start, run
chkdsk X: /r
Replace the X with the drive letter it tells you it want to run the scheduled scan on. Let the whole thing run, agree to it. It should reset the flags properly this time.
Thanks very much for the clarification. This request seems to come and go inexplicably. To add insult to injury, the preboot process takes about an hour to complete. For some reason, the preemptive scan you outlined runs at normal speed, but dosn't reset the flag.Quote:
Originally Posted by NooNoo
Do you think this is caused by XT or Norton Systemworks, my AV app. If the latter, I'll try uninstalling it.
This is a pain. I'm locked out of any access for an hour.
For clarification {If I'm capabale of that :D} my error was caused by the entry "mobsync.exe" in each of my machines startups (they having previously been part of a network) - removing that entry fixed each one ;)
Now I'm about to cause some more confusion as I'm 'surprised' at Noo's answer..
An Explanation of the New /C and /I Switches That Are Available to Use with Chkdsk.exe - Microsoft Knowledge Base Article - 314835
'My' error was EVERY boot so it didn't take a rocket scientist to figure out it was something in startup somewhere ... but can you clarify this bitQuote:
If the /R switch is in effect, CHKDSK runs a fourth pass to look for bad sectors in the volume's free space. CHKDSK attempts to read every sector on the volume to confirm that the sector is usable. Even without the /R switch, CHKDSK always reads sectors that are associated with metadata. Sectors that are associated with user data are read during earlier phases of CHKDSK if the /R switch is specified.
When CHKDSK finds an unreadable sector, NTFS adds the cluster that contains that sector to its list of bad clusters. If the bad cluster is in use, CHKDSK allocates a new cluster to do the job of the bad cluster. If you are using a fault-tolerant disk, NTFS recovers the bad cluster's data and writes the data to the newly allocated cluster. Otherwise, the new cluster is filled with a pattern of 0xFF bytes.
If NTFS encounters unreadable sectors during the course of normal operation, NTFS remaps the sectors in the same way that it does when CHKDSK runs. Therefore, using the /R switch is usually not essential. However, using the /R switch is a convenient way to scan the entire volume if you suspect that a disk might have bad sectors.
(btw you should always get the option to 'skip' it {press any key when it says})Quote:
This request seems to come and go inexplicably
because that says 'more likely' to me that it isn't always getting shut down 'correctly' ... there's a range of stuff can cause this besides just pulling power 'unexpectedly' (things like write-behind caching on disks etc) - if sucessfully running a chkdsk with the '/r' switch doesn't fix it (so that's check directory structure & map out bad sectors) then come back & tell us some more ;)