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.
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.
On Mon, 06 Nov 2017 18:26:31 -0600, james@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.
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
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.
The old Win9x Scandisk worked 100% better.
No, it didn't.
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.
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--- Platinum Xpress/Win/WINServer v3.1
having and using. The one I have in c:\windows\command is 650kb,
7-28-2001.
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.
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.
On 11/6/2017 7:26 PM, james@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.
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
In message <ottq7j0a1e@enews6.newsguy.com>, Ben Myers ><benjmyers@REMOVEmyactv.net> writes:
On 11/6/2017 7:26 PM, james@nospam.com wrote:I think he _was_ running it via Start | Run - that's the problem; it
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
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.
On 06 Nov 2017, Some Guy <Some@Guy.C0M> 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.
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?
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.
On 07 Nov 2017, T <T@invalid.invalid> 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.
On 07 Nov 2017, T <T@invalid.invalid> 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.
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 113 |
Nodes: | 10 (0 / 10) |
Uptime: | 122:18:10 |
Calls: | 373 |
Files: | 6 |
Messages: | 110,810 |