A Windows XP help forum. PCbanter

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.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

I never see the CHKDSK results



 
 
Thread Tools Display Modes
  #1  
Old November 7th 17, 01:26 AM posted to microsoft.public.windowsxp.general
No_Name
external usenet poster
 
Posts: 177
Default I never see the CHKDSK results

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.


Ads
  #3  
Old November 7th 17, 04:22 AM posted to microsoft.public.windowsxp.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default I never see the CHKDSK results

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
  #4  
Old November 7th 17, 04:40 AM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default I never see the CHKDSK results

In message ,
writes:
On Mon, 06 Nov 2017 18:26:31 -0600,
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.


Did you open the command prompt from the start/program/accessories
tab. I just did it and the screen stayed open giving me the regular
report when it was done. If you do it from the run bar it will close
when it stops


In other words, if you're doing Start | Run, then typing the command
there, it will do as you describe; if you're starting a command prompt
(Start | Run | [type] cmd, or Start | Programs | Accessories | Command
Prompt), and typing the command there, it will remain open when it
finishes.

Though as Paul says, it probably won't do what you expect if it's C:
you're scanning anyway (but at least you'll see what it says).

You might also like: from Windows Explorer (or I think My Computer),
right-click on the drive, choose Properties | Tools; there's a disc
checker there.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"We're plumbing shallows we didn't know existed here" - Jeremy Paxman (as
quizmaster of "University Challenge"), 1998 (when losing team suddenly put on a
spurt by showing knowledge of things like the Eurovision Song Contest ...)
  #6  
Old November 7th 17, 05:10 AM posted to microsoft.public.windowsxp.general
Some Guy
external usenet poster
 
Posts: 9
Default I never see the CHKDSK results

Nil wrote:

The old Win9x Scandisk worked 100% better.


No, it didn't.


Yes it did, if your (FAT32) file tables or other stuctures needed
fixing. Checkdisk (DOS 7/8) does not fix any such problems - doesn't
even look for them. Checkdisk (2K, XP, etc) - different story.

ndd.exe is another dos-level drive-checking utility that's worth having
and using. The one I have in c:\windows\command is 650kb, 7-28-2001.
  #8  
Old November 7th 17, 08:32 PM posted to microsoft.public.windowsxp.general
Nil[_5_]
external usenet poster
 
Posts: 1,731
Default I never see the CHKDSK results

On 06 Nov 2017, Some Guy wrote in
microsoft.public.windowsxp.general:

Yes it did, if your (FAT32) file tables or other stuctures needed
fixing. Checkdisk (DOS 7/8) does not fix any such problems -
doesn't even look for them. Checkdisk (2K, XP, etc) - different
story.


Is this documented somewhere? I'm skeptical. I'm pretty certain I've
repaired FAT32 disks with Windows 7's CHKDSK in the past, though it was
quite a while ago.

But besides that, the OP was comparing CHKDSK to the old DOS Scandisk
utility. Neither it or the DOS versions of CHKDSK could address NTFS
file systems, so it's not a fair comparison.

ndd.exe is another dos-level drive-checking utility that's worth
having and using. The one I have in c:\windows\command is 650kb,
7-28-2001.

  #11  
Old November 8th 17, 04:23 AM posted to microsoft.public.windowsxp.general
J. P. Gilliver (John)[_4_]
external usenet poster
 
Posts: 2,679
Default I never see the CHKDSK results

In message , Ben Myers
writes:
On 11/6/2017 7:26 PM, 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.


Click "Start", "Run", type "cmd /k chkdsk /f" into the "Open" box and
click "OK". If you just want chkdsk to scan for errors and not actually
perform repairs, leave off the "/f" switch. To stop the scan, press Ctrl-C.

Ben

I think he _was_ running it via Start | Run - that's the problem; it
closes the window when it's finished, before you have a chance to see
the summary. As others have said, run it from a command prompt (either
Start | Run | "cmd" or Start | Prograns | Accessories | Command Prompt),
then the window will stay open when it's finished. (Close either by
clicking the X as usual, or typing "exit".) But as others have also
said, it won't necessarily run on the disc (or partition) the OS is on.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Every time I think I know where it's at, they move it.
  #13  
Old November 8th 17, 10:37 AM posted to microsoft.public.windowsxp.general
No_Name
external usenet poster
 
Posts: 177
Default I never see the CHKDSK results

On Tue, 07 Nov 2017 14:32:17 -0500, Nil
wrote:

On 06 Nov 2017, Some Guy wrote in
microsoft.public.windowsxp.general:

Yes it did, if your (FAT32) file tables or other stuctures needed
fixing. Checkdisk (DOS 7/8) does not fix any such problems -
doesn't even look for them. Checkdisk (2K, XP, etc) - different
story.


Is this documented somewhere? I'm skeptical. I'm pretty certain I've
repaired FAT32 disks with Windows 7's CHKDSK in the past, though it was
quite a while ago.

But besides that, the OP was comparing CHKDSK to the old DOS Scandisk
utility. Neither it or the DOS versions of CHKDSK could address NTFS
file systems, so it's not a fair comparison.

ndd.exe is another dos-level drive-checking utility that's worth
having and using. The one I have in c:\windows\command is 650kb,
7-28-2001.


Yes, I was talking about SCANDISK in Win98. If we get a power outage,
when 98 starts up, it runs scandisk (unless I cancel it) and it has a
check box that allows it to automatiucally fix errors, or just tell me
about them. No need to go to the command line or any of that. It just
works and works easy. But yea, my drive in Win98 is FAT32.

I tried to run scandisk (the one from Win98) in XP once, on a NTFS
drive. That was long ago, and I cant remember just what happened. All I
do recall is that it did not work.

Yes, I have been running CHKDSK from START, RUN.... and I created an
icon in my utilities folder to make it one click. BUt I never have seen
the results. I guess I know now to use it from the command prompt.


  #14  
Old November 8th 17, 09:18 PM posted to microsoft.public.windowsxp.general
Nil[_5_]
external usenet poster
 
Posts: 1,731
Default I never see the CHKDSK results

On 07 Nov 2017, T wrote in
microsoft.public.windowsxp.general:

Not to ask too stupid a question, but is there a copy of a
boot time chkdsk output somewhere in log after the system boots
up?


When CHKDSK runs at boot time, the results are saved in Windows
Application log. Use the Event Viewer and look for Winlogin Event ID
1001.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 07:52 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.