Path:
eternal-september.org!reader02.eternal-september.org!news.eternal-september.org
!.POSTED!not-for-mail
From: Paul 
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: I never see the CHKDSK results
Date: Mon, 06 Nov 2017 22:22:06 -0500
Organization: A noiseless patient Spider
Lines: 53
Message-ID: 
References: 
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 7 Nov 2017 03:22:07 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
posting-host="d5cfd4191d4f1549d924cbdfd52b58c0";
 logging-data="24911";
mail-complaints-to="abuse{at}eternal-september.org";
posting-account="U2FsdGVkX1+p6oVOBIt9kZuHZvZoSBKaQnr1E9+5MNA="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
In-Reply-To: 
Cancel-Lock: sha1:jP9JKhUI364dZ1uTPkCDshFiX8g=
Xref: news.eternal-september.org microsoft.public.windowsxp.general:134449

james{at}nospam.com wrote:
> CHKDSK seems to run in a DOS prompt, and as soon as it finishes, it
> closes that dos window and I never see the results of the check. Whoever
> designed this is an idiot. The old Win9x Scandisk worked 100% better. 
> 
> 

Things that work well from Start : Run ...

    These are typically things that present their
    own stable dialog box.

       perfmon.msc         # Performance monitor graph
       diskmgmt.msc        # Disk Management
       devmgmt.msc         # Device Manager
       control.exe         # Control Panels
       regedit             # Registry Editor
       cmd.exe             # Command Prompt

The latter one, opens a Command Prompt window.

For a process that dumps a log to stdout, you'd want a
Command Prompt, as the Command Prompt will stay
open after the command runs.

    chkdsk D:
    chkdsk /?           # More info on CHKDSK. Parameters accepted
                        # vary from OS to OS, or whether you're using
                        # it from WinPE environment (emergency boot).

CHKDSK will not run immediately, if a volume is
busy. In particular, a CHKDSK of C: will cause
the actual check to be scheduled on the next boot.
A way to do this, is for the BootExecute key to have
a line added to it. And if that's not enough, you
can set the Dirty Bit on a volume, to cause autocheck
to pick it up on the next boot. That's an additional
mechanism for scheduling any partition you might want.

    chkdsk C:

When a CHKDSK runs at boot time, it generates a log
in the Event Viewer. Possibly under "Winlogon" ownership.

Another thing CHKDSK can do, is dump a file into
System Volume Information (where you don't have access).
The file is *binary* so a human cannot read it. I have
no idea what this is for, or whether it has anything
to do with the Event Viewer. Or what the story is. I
was just surprised to see a file with that name, in
SVI folder.

    Paul
--- Platinum Xpress/Win/WINServer v3.1