When chkdsk is run on bootup due to one or more 'dirty bits' being on,
it gives the cryptic note that it 'made changes', but the linger time
is too short to really read it. I went through all the .log files on
C drive looking for the chkdsk log - nada.

Off to Google - 1/4 mil hits, gotta be paydirt here. A few usoft KB
articles and several other sources convince me that the only
repository for chkdsk logging is the application events log in control
panel. Off to application events. Sure 'nuf it's there - sorta:

" Checking file system on C:
The type of the file system is FAT32.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 74C0-56DC
Windows has made corrections to the file system.
6806248 KB total disk space.
41108 KB in 316 hidden files.
7364 KB in 1416 folders.
3697056 KB in 27130 files.
3060716 KB are available.

4096 bytes in each allocation unit.
1701562 total allocation units on disk.
765179 allocation units available on disk. "

Now I'm back to square one - is there any way to determine what chkdsk
thought was wrong with the file system, and what were the
'corrections' that it made?

W2K SP4 + Rollup 1
--
Pete Gebel pfgebel(deletethis)@crisperiodcom
Have the best day possible - all things considered

On Tue, 07 Feb 2006 10:57:46 GMT, tanstafl <(E-Mail Removed)> wrote:

>Now I'm back to square one - is there any way to determine what chkdsk
>thought was wrong with the file system, and what were the
>'corrections' that it made?

CHKDSK C: /F > chkdsk.log

You will have a text record of everything that was done.


--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

The chkdsk that runs at boot is called autochk, and you review it's logs in the event viewer.

--
--
Steven

May you have the peace and freedom that come from abandoning all hope of having a better past.
--- - --- - - - - - - - -- - - - --- - ------ - - --- - - -- - - - -- - - -
"tanstafl" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
> When chkdsk is run on bootup due to one or more 'dirty bits' being on,
> it gives the cryptic note that it 'made changes', but the linger time
> is too short to really read it. I went through all the .log files on
> C drive looking for the chkdsk log - nada.
>
> Off to Google - 1/4 mil hits, gotta be paydirt here. A few usoft KB
> articles and several other sources convince me that the only
> repository for chkdsk logging is the application events log in control
> panel. Off to application events. Sure 'nuf it's there - sorta:
>
> " Checking file system on C:
> The type of the file system is FAT32.
>
> One of your disks needs to be checked for consistency. You
> may cancel the disk check, but it is strongly recommended
> that you continue.
> Windows will now check the disk.
> Volume Serial Number is 74C0-56DC
> Windows has made corrections to the file system.
> 6806248 KB total disk space.
> 41108 KB in 316 hidden files.
> 7364 KB in 1416 folders.
> 3697056 KB in 27130 files.
> 3060716 KB are available.
>
> 4096 bytes in each allocation unit.
> 1701562 total allocation units on disk.
> 765179 allocation units available on disk. "
>
> Now I'm back to square one - is there any way to determine what chkdsk
> thought was wrong with the file system, and what were the
> 'corrections' that it made?
>
> W2K SP4 + Rollup 1
> --
> Pete Gebel pfgebel(deletethis)@crisperiodcom
> Have the best day possible - all things considered

find the command prompt & type: chkdsk/?
this will give you a summary of what it does.
& for more options type: help

On Tue, 07 Feb 2006 15:32:38 GMT, (E-Mail Removed) (Bob) wrote:

>On Tue, 07 Feb 2006 10:57:46 GMT, tanstafl <(E-Mail Removed)> wrote:
>
>>Now I'm back to square one - is there any way to determine what chkdsk
>>thought was wrong with the file system, and what were the
>>'corrections' that it made?
>
>CHKDSK C: /F > chkdsk.log
>
>You will have a text record of everything that was done.

Thanks for the pointer. I tried it using D: since I didn't want to
reboot. Didn't produce a logfile - but then there wasn't anything to
fix, so the jury's still out. Googled again using your idea, got a
hit that suggested an alternate syntax:
CHKDSK C: /F > C:\ CHKDSKLOG.TXT . But it also implied that all it
would contain was the contents that would be placed in the event log -
which of course is worthless. I'll try canceling autochk after the
next BSOD (ouch!) and run your syntax manually. In the meantime, do
you have a pointer to your chkdsk.log info, maybe I can divine a lead
to do more research. Thanx
--
Pete Gebel pfgebel(deletethis)@crisperiodcom
Have the best day possible - all things considered

On Tue, 7 Feb 2006 19:22:58 -0500, "BerkHolz, Steven"
<(E-Mail Removed)> wrote:

>The chkdsk that runs at boot is called autochk, and you review it's logs in the event viewer.
>
Thanks for the clarification. Googling for autochk didn't show up
anything remarkable. From the usoft article, it seems autochk is just
frontend logic for deciding whether to run chkdsk - but I'll dig
deeper manana. The search is still ongoing for getting something a
teeny bit more verbose than the "Windows has made corrections to the
file system." line in the Event Viewer. :-) Minutia like what was
wrong and what did you do to fix it?

>"tanstafl" <(E-Mail Removed)> wrote in message news:(E-Mail Removed)...
>> When chkdsk is run on bootup due to one or more 'dirty bits' being on,
>> it gives the cryptic note that it 'made changes', but the linger time
>> is too short to really read it. I went through all the .log files on
>> C drive looking for the chkdsk log - nada.
>>
>> Off to Google - 1/4 mil hits, gotta be paydirt here. A few usoft KB
>> articles and several other sources convince me that the only
>> repository for chkdsk logging is the application events log in control
>> panel. Off to application events. Sure 'nuf it's there - sorta:
>>
>> " Checking file system on C:
>> The type of the file system is FAT32.
>>
>> One of your disks needs to be checked for consistency. You
>> may cancel the disk check, but it is strongly recommended
>> that you continue.
>> Windows will now check the disk.
>> Volume Serial Number is 74C0-56DC
>> Windows has made corrections to the file system.
>> 6806248 KB total disk space.
>> 41108 KB in 316 hidden files.
>> 7364 KB in 1416 folders.
>> 3697056 KB in 27130 files.
>> 3060716 KB are available.
>>
>> 4096 bytes in each allocation unit.
>> 1701562 total allocation units on disk.
>> 765179 allocation units available on disk. "
>>
>> Now I'm back to square one - is there any way to determine what chkdsk
>> thought was wrong with the file system, and what were the
>> 'corrections' that it made?
>>
>> W2K SP4 + Rollup 1

--
Pete Gebel pfgebel(deletethis)@crisperiodcom
Have the best day possible - all things considered

On Tue, 7 Feb 2006 20:28:24 -0600, "phillip maurice
nelson"<(E-Mail Removed)> wrote:

>find the command prompt & type: chkdsk/?
>this will give you a summary of what it does.
> & for more options type: help

Thanks for the suggestion. Unfortunately, my talent for
procrastination has now bit me. On this system, DOS windows close
immediately after execution is done -dunno why :-( On a 3Ghz system
that window is done and gone without even flickering the screen.

Never was motivated to pursue it - guess it's time now. Do you
perchance happen to know of a switch, option or registry key that
would keep the window open until closed manually? If it's not on the
top of your head, don't research it. Better for me to do my own
digging.
--
Pete Gebel pfgebel(deletethis)@crisperiodcom
Have the best day possible - all things considered

Hi, Pete.

If you Run a "DOS" command from the Start | Run prompt, it will close the
window when it is finished. (Unless you include the the switch to keep it
open, which I can't remember right now.)

But if you Run Cmd.exe, it should open a "DOS" window - which will stay open
until you close it by typing Exit at the prompt. I enclose "DOS" in quotes
to emphasize that this is not true MS-DOS, but only the Cmd.exe program (the
"Windows command interpreter"), which emulates MS-DOS in Win2K/XP/Vista.
You can use Cmd.exe's Properties window to customize the way it works on
YOUR computer.

Once in the "DOS" window, type cmd /? to get a mini-Help file showing the
many available switches you can use with the command. In fact, you can type
any "DOS" command, followed by /?, to see such a Help file. Dir /?, for
example, will show you many ways to see a Directory (Folder). And chkdsk /?
will show you the switches available with Chkdsk.exe. More details are in
the Windows Help and Support file (Press F1 from almost anywhere in
Windows).

I'm using the Vista beta at the moment and some things have changed since
Win2K. But this part still operates much as it did 6 years ago this month,
when Windows 2000 came to market. Six years is a long time to procrastinate
about learning such a basic tool for using Windows! Of course, that's the
biased opinion of a guy who used MS-DOS for years before Windows 1.0
arrived. ;^} Even today, there are many jobs that can be handled much
better in a "DOS" window than by using the GUI, and there are some jobs that
can only be done that way, so it's a very useful tool to know about.

> Better for me to do my own
> digging.

Right! ;<) And remember, what you learn will benefit you, not just to put
out today's fire, but for as long as you use your computer - which might be
the rest of your life. It's worth your investment!

RC
--
R. C. White, CPA
San Marcos, TX
(E-Mail Removed)
Microsoft Windows MVP

"tanstafl" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Tue, 7 Feb 2006 20:28:24 -0600, "phillip maurice
> nelson"<(E-Mail Removed)> wrote:
>
>>find the command prompt & type: chkdsk/?
>>this will give you a summary of what it does.
>> & for more options type: help
>
> Thanks for the suggestion. Unfortunately, my talent for
> procrastination has now bit me. On this system, DOS windows close
> immediately after execution is done -dunno why :-( On a 3Ghz system
> that window is done and gone without even flickering the screen.
>
> Never was motivated to pursue it - guess it's time now. Do you
> perchance happen to know of a switch, option or registry key that
> would keep the window open until closed manually? If it's not on the
> top of your head, don't research it. Better for me to do my own
> digging.
> --
> Pete Gebel pfgebel(deletethis)@crisperiodcomd

On Tue, 7 Feb 2006 20:28:24 -0600, "phillip maurice
nelson"<(E-Mail Removed)> wrote:

>find the command prompt & type: chkdsk/?
>this will give you a summary of what it does.
> & for more options type: help

What is "/L:size"? What log file?


--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan

On Wed, 08 Feb 2006 08:20:45 GMT, tanstafl <(E-Mail Removed)> wrote:

>do you have a pointer to your chkdsk.log info, maybe I can divine a lead
>to do more research.

I do not know of any. You can always query the KB with keywords
gleened from the output.


--

"It has been said that politics is the second oldest profession.
I have learned that it bears a striking resemblance to the first."
--Ronald Reagan