In Run I entered chkdsk C: /f and responded with 'Y' to the message
asking if I wanted this to be done on reboot. But on that next reboot
there was no chkdsk process, just a normal load of XP.

Anyone able to shed light on that please?

--
Terry, East Grinstead, UK

You forgot to press [ENTER] AFTER pressing Y???

Maybe you forgot - it's my guess that you did.

==

Cheers, Tim Meddick, Peckham, London. :-)




"Terry Pinnell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In Run I entered chkdsk C: /f and responded with 'Y' to the message
> asking if I wanted this to be done on reboot. But on that next reboot
> there was no chkdsk process, just a normal load of XP.
>
> Anyone able to shed light on that please?
>
> --
> Terry, East Grinstead, UK

P.S. You should also be able to 'summon' 'chkdsk /f' to run on reboot by
going to the system [c:] drive's icon in Explorer, then right-click and
choose 'Properties'

In the 'properties' page for [c:] drive click on the 'Tools' tab and then on
the 'Error checking' section 'Check Now' button.

To run 'chkdsk /f' on reboot; check mark the 'Automatically fix file system
errors' box and click [Start] button.
You will get a message box telling you the 'disk check could not be
completed because the drive is in use' then asking you 'do you want to run
the scan on the next reboot' - click on 'Yes'

To run 'chkdsk /r' on reboot; check mark BOTH boxes, then do the same as
above and answer 'Yes' when asked.

If you don't check either box, then chkdsk WILL run on the drive, but in the
background, and results will be displayed in Window's message boxes instead
of the text-style 'Command Prompt'

==

Cheers, Tim Meddick, Peckham, London. :-)




"Tim Meddick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> You forgot to press [ENTER] AFTER pressing Y???
>
> Maybe you forgot - it's my guess that you did.
>
> ==
>
> Cheers, Tim Meddick, Peckham, London. :-)
>
>
>
>
> "Terry Pinnell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> In Run I entered chkdsk C: /f and responded with 'Y' to the message
>> asking if I wanted this to be done on reboot. But on that next reboot
>> there was no chkdsk process, just a normal load of XP.
>>
>> Anyone able to shed light on that please?
>>
>> --
>> Terry, East Grinstead, UK
>
>

Thanks Tim, about to reboot right now to try that.

(Yes, I did use Enter after the 'Y' earlier.)

--
Terry, East Grinstead, UK


"Tim Meddick" <(E-Mail Removed)> wrote:

>P.S. You should also be able to 'summon' 'chkdsk /f' to run on reboot by
>going to the system [c:] drive's icon in Explorer, then right-click and
>choose 'Properties'
>
>In the 'properties' page for [c:] drive click on the 'Tools' tab and then on
>the 'Error checking' section 'Check Now' button.
>
>To run 'chkdsk /f' on reboot; check mark the 'Automatically fix file system
>errors' box and click [Start] button.
>You will get a message box telling you the 'disk check could not be
>completed because the drive is in use' then asking you 'do you want to run
>the scan on the next reboot' - click on 'Yes'
>
>To run 'chkdsk /r' on reboot; check mark BOTH boxes, then do the same as
>above and answer 'Yes' when asked.
>
>If you don't check either box, then chkdsk WILL run on the drive, but in the
>background, and results will be displayed in Window's message boxes instead
>of the text-style 'Command Prompt'
>
>==
>
>Cheers, Tim Meddick, Peckham, London. :-)
>
>
>
>
>"Tim Meddick" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> You forgot to press [ENTER] AFTER pressing Y???
>>
>> Maybe you forgot - it's my guess that you did.
>>
>> ==
>>
>> Cheers, Tim Meddick, Peckham, London. :-)
>>
>>
>>
>>
>> "Terry Pinnell" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> In Run I entered chkdsk C: /f and responded with 'Y' to the message
>>> asking if I wanted this to be done on reboot. But on that next reboot
>>> there was no chkdsk process, just a normal load of XP.
>>>
>>> Anyone able to shed light on that please?
>>>
>>> --
>>> Terry, East Grinstead, UK
>>
>>
>

Terry Pinnell <(E-Mail Removed)> wrote:

>Thanks Tim, about to reboot right now to try that.
>
>(Yes, I did use Enter after the 'Y' earlier.)

That sure took a long time on this 750 GB drive - about 5 hours!

But I was at lunch when it finally reached 100% of the last stage and
when I got back my PC was rebooted into my familiar desktop. I'd
assumed I'd get some sort of report, no?

Is there maybe a log somewhere please? There must be *something* to
show for 5 hours, even if only 'No problems found'!

--
Terry, East Grinstead, UK

Terry,
I know for sure that chkdsk's output IS logged and can be viewed in
'Event Viewer' ('Start Menu' > 'Administrative Tools' > 'Event Viewer')
*when* , that is, it runs because of what's called the 'dirty bit' being
detected. However, I'm not so sure whether or not it's logged there when
run by a request by the user.

It's the same issue with a file in the root directory, containing the same
output, called BOOTEX.LOG

It's definitely created when chkdsk runs on boot when it detects the 'dirty
bit' , but I don't know if it's created when chkdsk is 'called' by a user
request (chkdsk /f - typed at the 'Command Prompt').

==

Cheers, Tim Meddick, Peckham, London. :-)



"Terry Pinnell" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> Terry Pinnell <(E-Mail Removed)> wrote:
>
>>Thanks Tim, about to reboot right now to try that.
>>
>>(Yes, I did use Enter after the 'Y' earlier.)
>
> That sure took a long time on this 750 GB drive - about 5 hours!
>
> But I was at lunch when it finally reached 100% of the last stage and
> when I got back my PC was rebooted into my familiar desktop. I'd
> assumed I'd get some sort of report, no?
>
> Is there maybe a log somewhere please? There must be *something* to
> show for 5 hours, even if only 'No problems found'!
>
> --
> Terry, East Grinstead, UK

"Tim Meddick" <(E-Mail Removed)> wrote:

>Terry,
> I know for sure that chkdsk's output IS logged and can be viewed in
>'Event Viewer' ('Start Menu' > 'Administrative Tools' > 'Event Viewer')
>*when* , that is, it runs because of what's called the 'dirty bit' being
>detected. However, I'm not so sure whether or not it's logged there when
>run by a request by the user.
>
>It's the same issue with a file in the root directory, containing the same
>output, called BOOTEX.LOG
>
>It's definitely created when chkdsk runs on boot when it detects the 'dirty
>bit' , but I don't know if it's created when chkdsk is 'called' by a user
>request (chkdsk /f - typed at the 'Command Prompt').
>
>==
>
>Cheers, Tim Meddick, Peckham, London. :-)
>
>
>
>"Terry Pinnell" <(E-Mail Removed)> wrote in message
>news(E-Mail Removed)...
>> Terry Pinnell <(E-Mail Removed)> wrote:
>>
>>>Thanks Tim, about to reboot right now to try that.
>>>
>>>(Yes, I did use Enter after the 'Y' earlier.)
>>
>> That sure took a long time on this 750 GB drive - about 5 hours!
>>
>> But I was at lunch when it finally reached 100% of the last stage and
>> when I got back my PC was rebooted into my familiar desktop. I'd
>> assumed I'd get some sort of report, no?
>>
>> Is there maybe a log somewhere please? There must be *something* to
>> show for 5 hours, even if only 'No problems found'!
>>
>> --
>> Terry, East Grinstead, UK
>

Thanks Tim. No sign of BOOTEX.LOG in the roots of either of the two
HDs on which I used the 'full' CHKDSK, C: and I:, so maybe that means
they were both clean. Still would have liked a note to that effect
somewhere!

--
Terry, East Grinstead, UK

Terry Pinnell <(E-Mail Removed)> wrote:

>"Tim Meddick" <(E-Mail Removed)> wrote:
>
>>Terry,
>> I know for sure that chkdsk's output IS logged and can be viewed in
>>'Event Viewer' ('Start Menu' > 'Administrative Tools' > 'Event Viewer')
>>*when* , that is, it runs because of what's called the 'dirty bit' being
>>detected. However, I'm not so sure whether or not it's logged there when
>>run by a request by the user.

Tim,

Please to report that I found reports for both C: and I: in Event
Viewer > Applications (Winlogon source).

Here's an extract:

Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

732563968 KB total disk space.
204117300 KB in 377672 files.
140124 KB in 39827 indexes.
0 KB in bad sectors.
515984 KB in use by the system.
65536 KB occupied by the log file.
527790560 KB available on disk.

Do you know what (if any) would be the effect of those ' unused index
entries' please?

--
Terry, East Grinstead, UK

Terry,
I was going to run 'chkdsk' / press [Y] / reboot on MY
computer and see if anything was logged to the 'Event Viewer', but then
saw your post.

I'm really glad that you've found the chkdsk 'log'.

As for the messages that appear; every computer I have run 'chkdsk' on
says something very much like :


Cleaning up 4 unused index entries from index $SDH of file 0x9
Cleaning up 4 unused security descriptors.


....I have just run it and, on my PC, it's saying something a bit more
serious now (I ran it in a dos-box but, I will run it in RC later).

I don't think it will actually 'clear up' what it says that it's
clearing up, unless you run it with the '/f' switch, however, but I
could be wrong.

Due to the fact that it [virtually] always saying something like that on
every computer I use, I think it's normal and something to be expected,
it even [sometimes] says that it's actually "not a corruption".

It's only when you run chkdsk without the /f switch (to see if it
NEEDS to be run WITH the /f switch) in Windows, and it gives the
message :


Chkdsk could not continue in read-only mode.
Errors were found but not fixed.
Run chkdsk /f to fix these errors.


....(I'm writing this chkdsk 'output' from memory, so it's not that
accurate, but you should recognise the message)

When chkdsk tells you (in it's output) that it has FOUND errors and
needs to be run WITH the /f switch included, that you need to take any
action of any sort.


==

Cheers, Tim Meddick, Peckham, London. :-)




"Terry Pinnell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Terry Pinnell <(E-Mail Removed)> wrote:
>
>>"Tim Meddick" <(E-Mail Removed)> wrote:
>>
>>>Terry,
>>> I know for sure that chkdsk's output IS logged and can be
>>> viewed in
>>>'Event Viewer' ('Start Menu' > 'Administrative Tools' > 'Event
>>>Viewer')
>>>*when* , that is, it runs because of what's called the 'dirty bit'
>>>being
>>>detected. However, I'm not so sure whether or not it's logged there
>>>when
>>>run by a request by the user.
>
> Tim,
>
> Please to report that I found reports for both C: and I: in Event
> Viewer > Applications (Winlogon source).
>
> Here's an extract:
>
> Cleaning up 4 unused index entries from index $SII of file 0x9.
> Cleaning up 4 unused index entries from index $SDH of file 0x9.
> Cleaning up 4 unused security descriptors.
> CHKDSK is verifying file data (stage 4 of 5)...
> File data verification completed.
> CHKDSK is verifying free space (stage 5 of 5)...
> Free space verification is complete.
> CHKDSK discovered free space marked as allocated in the
> master file table (MFT) bitmap.
> Windows has made corrections to the file system.
>
> 732563968 KB total disk space.
> 204117300 KB in 377672 files.
> 140124 KB in 39827 indexes.
> 0 KB in bad sectors.
> 515984 KB in use by the system.
> 65536 KB occupied by the log file.
> 527790560 KB available on disk.
>
> Do you know what (if any) would be the effect of those ' unused index
> entries' please?
>
> --
> Terry, East Grinstead, UK