If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
Normally I run chkdsk from Command Prompt. Example: chkdsk d: /f /v Is there a way to have the chkdsk-run (Explorer, right-click drive, [Tools][Error-checking]) run with the /v option? I assume there must be a Registry entry to run chkdsk from [Tools]. So can this be done? -- =========== Tecknomage =========== Computer Systems Specialist ComputerHelpForum.org Staff Member IT Technician San Diego, CA |
Ads |
#2
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
On 17/05/2012 1:20 PM, Tecknomage wrote:
Normally I run chkdsk from Command Prompt. Example: chkdsk d: /f /v Is there a way to have the chkdsk-run (Explorer, right-click drive, [Tools][Error-checking]) run with the /v option? I assume there must be a Registry entry to run chkdsk from [Tools]. So can this be done? If you're looking to see the application message during the run, then you can find them located in the Event Logs. They are located in Application Log, source Wininit, Event ID 1001. Best part of it is that you don't have sit there and watch it as it goes, you can just come back to it and look at its output when its done, and you won't have to worry about messages scrolling off. Yousuf Khan |
#3
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
On Thu, 17 May 2012 23:30:27 -0400, Yousuf Khan
wrote: On 17/05/2012 1:20 PM, Tecknomage wrote: Normally I run chkdsk from Command Prompt. Example: chkdsk d: /f /v Is there a way to have the chkdsk-run (Explorer, right-click drive, [Tools][Error-checking]) run with the /v option? I assume there must be a Registry entry to run chkdsk from [Tools]. So can this be done? If you're looking to see the application message during the run, then you can find them located in the Event Logs. They are located in Application Log, source Wininit, Event ID 1001. Best part of it is that you don't have sit there and watch it as it goes, you can just come back to it and look at its output when its done, and you won't have to worry about messages scrolling off. Yousuf Khan 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. 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. -- =========== Tecknomage =========== Computer Systems Specialist ComputerHelpForum.org Staff Member IT Technician San Diego, CA |
#4
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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 |
#5
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. Thanks -- =========== Tecknomage =========== Computer Systems Specialist ComputerHelpForum.org Staff Member IT Technician San Diego, CA |
#6
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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 |
#7
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. -- ==== Tecknomage ==== Imponderable: If a man is alone in the woods, and he says something, and no woman is around to disagree, is he still wrong? - Pickles 1997 |
#8
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. -- Zaphod Vell, Zaphod's just zis guy, ya know? - Gag Halfrunt |
#9
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. -- =========== Tecknomage =========== Computer Systems Specialist ComputerHelpForum.org Staff Member IT Technician San Diego, CA |
#10
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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 -- Zaphod "So [Trillian], two heads is what does it for a girl?" "...Anything else [Zaphod]'s got two of?" - Arthur Dent |
#11
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. My philosophy is to always educate people up, especially in technology. So they 'panic,' you just inform them why they shouldn't. 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. -- =========== Tecknomage =========== Computer Systems Specialist ComputerHelpForum.org Staff Member IT Technician San Diego, CA |
#12
|
|||
|
|||
MVPs - chkdsk Run from Explorer Tools
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. |
Thread Tools | |
Display Modes | |
|
|