D
Doug Hoeffel \(eMVP\)
Hello:
I'm using XPe SP1 with RAM-based EWF on a HD. Only my NTFS boot partition
is protected by the EWF. I have 2 other NTFS partitions. At startup, my
registry is setup to run chkdsk if the dirty bit is set on my 2 non-EWF
protected partitions. I had a corrupt partition but the dirty bit was not
set, i.e. I did a "chkntfs D:" but the results stated that the dirty bit
was not set. When I ran chkdsk, i..e chkdsk D: /F, it found and fixed
corruptions.
Has anyone seen this before? I don't think this is related to EWF since I
have run tests before to check that chkdsk will run if the dirty bit does
get set. With the EWF enabled, I do a "fsutil dirty set D:" from the cmd
prompt, reboot, and I can see chkdsk run.
TIA... Doug
I'm using XPe SP1 with RAM-based EWF on a HD. Only my NTFS boot partition
is protected by the EWF. I have 2 other NTFS partitions. At startup, my
registry is setup to run chkdsk if the dirty bit is set on my 2 non-EWF
protected partitions. I had a corrupt partition but the dirty bit was not
set, i.e. I did a "chkntfs D:" but the results stated that the dirty bit
was not set. When I ran chkdsk, i..e chkdsk D: /F, it found and fixed
corruptions.
Has anyone seen this before? I don't think this is related to EWF since I
have run tests before to check that chkdsk will run if the dirty bit does
get set. With the EWF enabled, I do a "fsutil dirty set D:" from the cmd
prompt, reboot, and I can see chkdsk run.
TIA... Doug