W
W C Hull
Last week I posted a message asking for help on a chkdsk issue. Although
several people contributed to the discuession, I did not get a solution to
my problem and wanted to give it another try.
The problem I'm having is the fact that after installing and then removing
some software, I can no longer get chkdsk to run at the next restart by
running chkdsk from a command window. Each time I enter chkdsk c: /F or
chkdsk c: /R from a command window I get asked if I want chkdsk to run at
the next restart. I always answer yes but the next time I restart my system
chkdsk does not start. Instead my system just boots to there logon prompt.
After last week I know that I can launch chkdsk from the Windows Recovery
Console if I boot from my install CD. I can also trick my system into
running a chkdsk by setting the dirty bit with the FSUTIL program. My
suspicion is that when chkdsk is invoked from a command window it must set
something that is examined upon a restart and whatever needs to be set is
either missing or can't be changed. My problem is that I don't know what is
needed to determine what is wrong and how to fix it.
If anyone know a solution to this issue or knows exactly what is set when
chkdsk is run form the command window, please reply to this post.
Thanks,
several people contributed to the discuession, I did not get a solution to
my problem and wanted to give it another try.
The problem I'm having is the fact that after installing and then removing
some software, I can no longer get chkdsk to run at the next restart by
running chkdsk from a command window. Each time I enter chkdsk c: /F or
chkdsk c: /R from a command window I get asked if I want chkdsk to run at
the next restart. I always answer yes but the next time I restart my system
chkdsk does not start. Instead my system just boots to there logon prompt.
After last week I know that I can launch chkdsk from the Windows Recovery
Console if I boot from my install CD. I can also trick my system into
running a chkdsk by setting the dirty bit with the FSUTIL program. My
suspicion is that when chkdsk is invoked from a command window it must set
something that is examined upon a restart and whatever needs to be set is
either missing or can't be changed. My problem is that I don't know what is
needed to determine what is wrong and how to fix it.
If anyone know a solution to this issue or knows exactly what is set when
chkdsk is run form the command window, please reply to this post.
Thanks,