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
|
|||
|
|||
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 |
#2
|
|||
|
|||
I never see the CHKDSK results
|
#3
|
|||
|
|||
I never see the CHKDSK results
|
#5
|
|||
|
|||
I never see the CHKDSK results
|
#6
|
|||
|
|||
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. |
#7
|
|||
|
|||
I never see the CHKDSK results
|
#8
|
|||
|
|||
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. |
#9
|
|||
|
|||
I never see the CHKDSK results
|
#10
|
|||
|
|||
I never see the CHKDSK results
|
#11
|
|||
|
|||
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. |
#12
|
|||
|
|||
I never see the CHKDSK results
On Wed, 8 Nov 2017 03:23:11 +0000, "J. P. Gilliver (John)"
wrote: 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. If you do this a lot you can just create an icon on the desktop. |
#13
|
|||
|
|||
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
|
|||
|
|||
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. |
#15
|
|||
|
|||
I never see the CHKDSK results
|
|
Thread Tools | |
Display Modes | |
|
|