On Thu, 24 May 2012 06:53:54 -0700, "Tecknomage"
wrote in article
...

On Wed, 23 May 2012 11:32:44 -0400, Zaphod Beeblebrox
wrote:

On Wed, 23 May 2012 06:07:48 -0700, "Tecknomage"
wrote in article
...

On Tue, 22 May 2012 09:51:49 -0400, Zaphod Beeblebrox
wrote:

On Tue, 22 May 2012 05:57:09 -0700, "Tecknomage"
wrote in article
...

On Tue, 22 May 2012 02:58:08 -0400, Yousuf Khan
wrote:

On 21/05/2012 10:06 AM, Tecknomage wrote:
On Fri, 18 May 2012 13:34:25 -0400, Yousuf Khan
wrote:

On 18/05/2012 11:32 AM, Tecknomage wrote:
You don't understand.

I want to see the /v info *during the reboot-run*, NOT have to use
Event Logs. That is, exactly how I see it using Command Prompt run.

It'll record the chkdsk output into Event logs even for reboot runs.

Also, IF I remember correctly, the /v info is not in the Event Logs
when run from Explorer [Tools]. I will have to check this later.

It looks like verbose out to me in the event logs.

Yousuf Khan


My apologies, you are correct. The screen does not show verbose, but
the Event Log entry does.

As old as I am I can still learn.

No problem, glad to help.

Yousuf Khan


SIDE COMMENT: This is typical Microdunce, have the screen display
different from the Event Log. They SHOULD be the same.

No, the event log should always be verbose, even if the screen output
has been limited. That way, the info is always available in the log
without having to set the parameter.

Makes perfect sense to me, anyway.

I agree with the Event Log entry, but IMHO the screen output NOT being
the same does NOT make sense. The problem with that is it is hiding
info from the every-day user who does not know about Event Logs.

Users need to know all the results when they run any test.

In my experience, when dealing with the average computer user the
verbose content does two things: First, it obscures important
information, and second, causes them to panic.

In my mind, MS got this one right. They get plenty of other things
wrong, but not this one. YMMV


You seem to be one of the dumb-down people. Dumb things down to the
lowest denominator rather than educate people up.

Nope, not really, but if folks don't want to educate themselves there
isn't much I can (or am willing to) do.


My philosophy is to always educate people up, especially in
technology. So they 'panic,' you just inform them why they shouldn't.

After the 100th time, it gets old. If they want to learn, I'll assist
where I can. If not, I'm happy for those moments where the information
provided is sufficient to let you know there is or isn't a problem.
Even happier when the full detail is provided in a more permanent way
in logs, etc., without having to specify that I want it.

And in the case of chkdsk verbose output, only users curious about the
info would have a question. Most would not even note the difference
even if they looked at the screen display.

When I help people with their computer problems I have them sit with
me and I talk about what I am doing and why, as I do it. They may not
really care, but at least they've heard and may learn something.

Note, I've been doing this since the mid 90's. Even though I'm
retired, I still do this for friends.

So, you are a relative newcomer ;-). I've been doing it even longer,
and I've gotten to the place where I offer to teach, but am not
bothered if they don't want to learn. Everyone has their specialties -
although I take flights to vacation or for work, I can't fly an
airplane and have no desire to learn, but that doesn't make me less
intelligent than my relatives who can. Similarly, they are computer
users (just barely) who have no desire to learn the internals and
details.

As always, to each his own.

--
Zaphod

Voted "Worst Dressed Sentient Being in the Known Universe" for seven
years in a row.