S
Stan Hilliard
How can I make CHKDSK pause so I can read what it did prior to
starting windows XP-Pro?
starting windows XP-Pro?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
R. McCarty
Invoke the command from within a Command Prompt window:
Click Start, Run ( type ) Cmd [Enter]
Click Start, Run ( type ) Cmd [Enter]
L
Lem
Stan said:How can I make CHKDSK pause so I can read what it did prior to
starting windows XP-Pro?
After Windows starts
- Start > Run > [type] eventvwr [click OK]
- look in the "Application" log for an entry from Source = "winlogon"
(if you want to make things easier, open event viewer before you run
chkdsk and clear the log so there won't be many entries to scroll through).
--
Lem -- MS-MVP
To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm
P
Pegasus [MVP]
R. McCarty said:Invoke the command from within a Command Prompt window:
Click Start, Run ( type ) Cmd [Enter]Chkdsk C:
This won't work. Drive C: is normally the System Drive and is therefore
locked. Chkdisk will inform the OP that it will run at the next reboot, when
the OP won't be able to pause the display in order to see the messages. He
must examine the Event Viewer messages, as suggested by Lem.
T
Tim Meddick
No, but it will run and just report problems (it won't fix) if run WITHOUT
the /f switch on the c: system drive.
--
Cheers, Tim Meddick, Peckham, London.
the /f switch on the c: system drive.
--
Cheers, Tim Meddick, Peckham, London.
Pegasus said:R. McCarty said:Invoke the command from within a Command Prompt window:
Click Start, Run ( type ) Cmd [Enter]Chkdsk C:
This won't work. Drive C: is normally the System Drive and is therefore
locked. Chkdisk will inform the OP that it will run at the next reboot,
when the OP won't be able to pause the display in order to see the
messages. He must examine the Event Viewer messages, as suggested by Lem.
J
Jose
How can I make CHKDSK pause so I can read what it did prior to
starting windows XP-Pro?
CHKDSK is used (usually) to check for hardware problems with the disk
and maybe try to correct them.
Why is CHKDSK even running or are you running it manually?
If it runs by itself, it sounds like you have a problem that needs
investigation.
If you are running it manually, why are you doing that? It takes
long time, doesn't it?
It will not hurt anything if you just want to check things.
P
Pegasus [MVP]
R. McCarty said:My example included no Chkdsk qualifiers and will work for a
simple/cursory Chkdsk. What you're saying is true if you try &
run Chkdsk with /F or /R in a Cmd Prompt Window.
The OP said "I can read what it did". This to me implies the /F or /R
switch. Without these switches chkdsk will only report things but it won't
"do" anything to the file system.
T
Tim Meddick
CHKDSK will run automatically on boot if there are ANY minor inconsistencies
on any drives. In point of fact CHKDSK runs EVERY TIME YOUR COMPUTER STARTS
and scans for the 'dirty bit' (not a bit of dirt but a 'bit' on the drive
that marks it as 'dirty' in need of correction). If run either by being
called by an inconsistency on a drive or by using CHKDSK /F at the prompt
and answering 'y' for yes to the question 'do you want chkdsk to run on next
boot' then it doesn't give you time to read it's results output as Windows
XP is loading. Lem's response was the best citing that CHKDSK's output from
running at boot-time can be re-viewed in the Applications section of the
'Event Viewer' on the 'Administrator's Tools' menu.
--
Cheers, Tim Meddick, Peckham, London.
CHKDSK is used (usually) to check for hardware problems with the disk
and maybe try to correct them.
Why is CHKDSK even running or are you running it manually?
If it runs by itself, it sounds like you have a problem that needs
investigation.
If you are running it manually, why are you doing that? It takes
long time, doesn't it?
It will not hurt anything if you just want to check things.
on any drives. In point of fact CHKDSK runs EVERY TIME YOUR COMPUTER STARTS
and scans for the 'dirty bit' (not a bit of dirt but a 'bit' on the drive
that marks it as 'dirty' in need of correction). If run either by being
called by an inconsistency on a drive or by using CHKDSK /F at the prompt
and answering 'y' for yes to the question 'do you want chkdsk to run on next
boot' then it doesn't give you time to read it's results output as Windows
XP is loading. Lem's response was the best citing that CHKDSK's output from
running at boot-time can be re-viewed in the Applications section of the
'Event Viewer' on the 'Administrator's Tools' menu.
--
Cheers, Tim Meddick, Peckham, London.
How can I make CHKDSK pause so I can read what it did prior to
starting windows XP-Pro?
CHKDSK is used (usually) to check for hardware problems with the disk
and maybe try to correct them.
Why is CHKDSK even running or are you running it manually?
If it runs by itself, it sounds like you have a problem that needs
investigation.
If you are running it manually, why are you doing that? It takes
long time, doesn't it?
It will not hurt anything if you just want to check things.
J
Jake Marley
No, but it will run and just report problems (it won't fix) if run WITHOUT
the /f switch on the c: system drive.
Please tell us how you choose the command line switches that will be
used when Windows schedules a CHKDSK to be run on a restart.
You've found something that I don't think anyone else knows about.
Pegasus said:R. McCarty said:Invoke the command from within a Command Prompt window:
Click Start, Run ( type ) Cmd [Enter]
Chkdsk C:
This won't work. Drive C: is normally the System Drive and is therefore
locked. Chkdisk will inform the OP that it will run at the next reboot,
when the OP won't be able to pause the display in order to see the
messages. He must examine the Event Viewer messages, as suggested by Lem.
T
Tim Meddick
The post suggested that the OP could run CHKDSK from the COMMAND PROMPT and
there are two switches that can be used by the autorun CHKDSK at boot-time
initiated by the two corresponding switches at the COMMAND PROMPT They are:
CHKDSK C: /F produces the autorun command AUTOCHK /P \??\C:
CHKDSK C: /R produces the autorun command AUTOCHK /R \??\C:
....you can use the /p and /r switches with chkdsk when run from Recovery
Console
--
Cheers, Tim Meddick, Peckham, London.
there are two switches that can be used by the autorun CHKDSK at boot-time
initiated by the two corresponding switches at the COMMAND PROMPT They are:
CHKDSK C: /F produces the autorun command AUTOCHK /P \??\C:
CHKDSK C: /R produces the autorun command AUTOCHK /R \??\C:
....you can use the /p and /r switches with chkdsk when run from Recovery
Console
--
Cheers, Tim Meddick, Peckham, London.
Jake Marley said:No, but it will run and just report problems (it won't fix) if run WITHOUT
the /f switch on the c: system drive.
Please tell us how you choose the command line switches that will be
used when Windows schedules a CHKDSK to be run on a restart.
You've found something that I don't think anyone else knows about.
Pegasus said:Invoke the command from within a Command Prompt window:
Click Start, Run ( type ) Cmd [Enter]
Chkdsk C:
This won't work. Drive C: is normally the System Drive and is therefore
locked. Chkdisk will inform the OP that it will run at the next reboot,
when the OP won't be able to pause the display in order to see the
messages. He must examine the Event Viewer messages, as suggested by
Lem.
J
Jake Marley
The post suggested that the OP could run CHKDSK from the COMMAND PROMPT and
Welp... I think you missed the point that CHJDSK cannot be run from
the command prompt on the system drive.
J
Jake Marley
The post suggested that the OP could run CHKDSK from the COMMAND PROMPT and
[irrelevant material snipped]
Welp... it looks as if you missed the fact that one can NOT run CHKDSK
on the system disk from the Windows command prompt.
T
Tim Meddick
Yes it CAN without the /f switch and THAT was what the reply by 'R. McCarty'
was about. I simply backed him up when 'Pegasus' said it could not. Read
his rebuttal:-
....and so it is CHKDSK (Command Prompt) will give you exactly the same
report whether the /f switch is used or not. It will just give you the same
report time and time again because it won't be fixing any of the problems it
finds without specifying /f.
was about. I simply backed him up when 'Pegasus' said it could not. Read
his rebuttal:-
My example included no Chkdsk qualifiers.....
....and so it is CHKDSK (Command Prompt) will give you exactly the same
report whether the /f switch is used or not. It will just give you the same
report time and time again because it won't be fixing any of the problems it
finds without specifying /f.
T
Tim Meddick
No, the OP said he Can't read what it did and asked how he might go about
find such a way as to be able to read what it did.
This led to Lem's reply to "use Event Viewer..." why else would he have
given that advice.
find such a way as to be able to read what it did.
This led to Lem's reply to "use Event Viewer..." why else would he have
given that advice.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.