CHKDSK and File system corruption

S

sharon669

Hi all, first sorry for my English

I have 2 hard drives installed,
C = 80GB, D= 250Gb
Drive C is 1 year's old, drive D is brand new Western Digital, both
SATA interface.

Few days ago I formatted c partition, and installed fresh copy of XP
pro.
Previous version became slow, but file system was 100% ok, no
corruptions, no HD failure, nothing.
I let the installation to reboot the computer, and came back after 10
min, then I saw CHKDSK output "Deleting index entry FILE_NAME in index
$_-_ of file ______."
http://www.planetnana.co.il/develop/CHKDSK.htm
I took this picture and stopped CHKDSK (to late fortunately...80% done)
The entire D drive was corrupted, some folders was deleted, and 90% of
the files are corrupt, folder structure remain the same, file names
remain the same,

I have backup from 2 month ago,
This picture shows FS difference (current and backup) :
http://www.planetnana.co.il/develop/CHKDSK1.htm
And this image shows the content corruption of typical html file (name
stayed the same):
http://www.planetnana.co.il/develop/CHKDSK2.htm

How is it possible??
Why will CHKDSK ruin perfect FS (previous XP with SP2 used this drive
with no problem)??
Is there any way I can reverse CHKDSK operation ?

Thank you very much for your help.
Sorry for reposting.
Sharon
 
R

R. McCarty

I believe that as part of the install process XP will check the "Dirty"
flag on all volumes available for it to mount. If the flag is "Dirty" it
will proceed to a Chkdsk. Unfortunately, changes made by it are
not easily undone. It's data structures it is changing not some type
of Format or Partition which many Disk Management tools can roll
back. In cases like yours, I take a Image of the corrupted volume.
This way I can attempt recovery without the risk of further damage
to the original drive/contents by using the image.

A two month loss is bad but not as bad as a complete loss. Personally,
I use a weekly backup schedule and if any significant changes are
planned do an immediate image before installing/upgrading anything.
 
S

sharon669

I believe that as part of the install process XP will check the "Dirty"
flag on all volumes available for it to mount. If the flag is "Dirty" it
will proceed to a Chkdsk. Unfortunately, changes made by it are
not easily undone. It's data structures it is changing not some type
of Format or Partition which many Disk Management tools can roll
back. In cases like yours, I take a Image of the corrupted volume.
This way I can attempt recovery without the risk of further damage
to the original drive/contents by using the image.

A two month loss is bad but not as bad as a complete loss. Personally,
I use a weekly backup schedule and if any significant changes are
planned do an immediate image before installing/upgrading anything.











- Show quoted text -
Click to expand...

Thank you,

Is there any software you recommend to take Image of the drive ?
As far as I know "ghost" wont take 1:1 is it true ?
 
R

R. McCarty

For Imaging I use Acronis True Image Home 10. Using the Boot
CD-R ( Created from with Windows after installing ). If the PC
doesn't have an alternate partition or disk for destination of the
image I'll use a small portable FireLite USB drive to hold the image
until I can burn it to Optical media. In your case you may not have
a physical disk large enough to hold the damaged volume image.
TI has variable compression rates and using the maximum value
you might get a compression level of 50-60% ( depending on the
data type being imaged ).
Once created you can extract data from the .tib ( Image module )
directly or restore the entire image to a drive equal to the source
drive's size and continue your recovery efforts.
 
A

Andy

Hi all, first sorry for my English

I have 2 hard drives installed,
C = 80GB, D= 250Gb
Drive C is 1 year's old, drive D is brand new Western Digital, both
SATA interface.

Few days ago I formatted c partition, and installed fresh copy of XP
pro.
Previous version became slow, but file system was 100% ok, no
corruptions, no HD failure, nothing.
I let the installation to reboot the computer, and came back after 10
min, then I saw CHKDSK output "Deleting index entry FILE_NAME in index
$_-_ of file ______."
http://www.planetnana.co.il/develop/CHKDSK.htm
I took this picture and stopped CHKDSK (to late fortunately...80% done)
The entire D drive was corrupted, some folders was deleted, and 90% of
the files are corrupt, folder structure remain the same, file names
remain the same,

I have backup from 2 month ago,
This picture shows FS difference (current and backup) :
http://www.planetnana.co.il/develop/CHKDSK1.htm
And this image shows the content corruption of typical html file (name
stayed the same):
http://www.planetnana.co.il/develop/CHKDSK2.htm

How is it possible??
Click to expand...

Most likely because the fresh copy of XP lacks service pack 1 or 2,
which means that it can only access up to the 137 GB point (28-bit LBA
capability) in a large disk.
Why will CHKDSK ruin perfect FS (previous XP with SP2 used this drive
with no problem)??
Click to expand...

Because SP2 enables 48-bit LBA capability in Windows XP.
Is there any way I can reverse CHKDSK operation ?
Click to expand...

Install SP2 and run chkdsk again.
 
S

sharon669

Most likely because the fresh copy of XP lacks service pack 1 or 2,
which means that it can only access up to the 137 GB point (28-bit LBA
capability) in a large disk.


Because SP2 enables 48-bit LBA capability in Windows XP.


Install SP2 and run chkdsk again.






- Show quoted text -- Hide quoted text -

- Show quoted text -
Click to expand...

Thank you very much for the information,

I installed SP2, and Acronis True Image Home 10.
As I restarted the computer, CHKDSK started and prompt “the volume is
dirty†and started running file verification (step 1 of 3), there was
no confirmation, or escape option.
I immediately rebooted the computer, and I disconnected D drive from
the power cord.
I don’t want CHKDSK to operate on the drive before I backup the drive
with the Acronis soft.

I tried :
CHAKDSK /X d:
And even renaming CHKDSK from exe to txt (I don’t know how it started
again?)
I am unable to set the drive’s dirty flag using:
fsutil dirty set
Because the drive is disconnected,
I tried connecting the SATA cable after windows finish loading and
hoped it will act like pnp, but it didn’t ïŒ
Nothing helps.

What can I do to backup the drive first?
 
C

cquirke (MVP Windows shell/user)

I have 2 hard drives installed,
C = 80GB, D= 250Gb
Drive C is 1 year's old, drive D is brand new Western Digital, both
SATA interface.
Click to expand...

D: is > 137G, so OS must be OK with that.
Few days ago I formatted c partition, and installed fresh copy of XP
pro.
Click to expand...

What SP level?
- XP Gold (original "fit to ship" release) is lethal > 137G
- XP SP1 is safe > 137G in most but not all contexts
- XP SP2 is safe > 137G

Specifically, if XP "Gold" is EVER allowed to AutoChk or ChkDsk that
big D:, it is very likely to screw it up.

The contexts in which XP SP1 is unsafe > 137G usually apply where the
OS is booting and running off the drive, e.g. writing a RAM dump after
a system error, possibly hibernating to disk, etc.
I let the installation to reboot the computer, and came back after 10
min, then I saw CHKDSK output "Deleting index entry FILE_NAME in index
$_-_ of file ______."
http://www.planetnana.co.il/develop/CHKDSK.htm
I took this picture and stopped CHKDSK (to late fortunately...80% done)
The entire D drive was corrupted, some folders was deleted, and 90% of
the files are corrupt, folder structure remain the same, file names
remain the same,
Click to expand...
I have backup from 2 month ago,
This picture shows FS difference (current and backup) :
http://www.planetnana.co.il/develop/CHKDSK1.htm
And this image shows the content corruption of typical html file (name
stayed the same):
http://www.planetnana.co.il/develop/CHKDSK2.htm
Click to expand...
How is it possible??
Click to expand...

You allowed the duhfault behavior of XP, e.g. to "automatically fix
file system errors" on startup if volumes are marked as "dirty" (as
they may be after a bad exit).
Why will CHKDSK ruin perfect FS (previous XP with SP2 used this drive
with no problem)??
Click to expand...

AutoChk and ChkDsk /F are quite cavalier, operating on the ASSumption
they are Right, and that if they don't need something, then neither do
you. When they get it wrong, they get it spectacularly wrong... it's
a clasic dumb-ass machine thing.

After going "hmm, invalid file, delete" 2000 times, most humans would
re-check their assumptions, but "kill, bury, deny" AutoChk or ChkDsk
just keep on chugging until everything is irreversibly dead. After
all, what maintain an "undo" if you are "always right"?
Is there any way I can reverse CHKDSK operation ?
Click to expand...

Nope.

What you can do, is:
- make sure yopur XP is SP2 before reconnecting the 250G
- kill AutoChk by editing BootExecute appropriately

To disable AutoChk on all volumes except C:, do this...

autocheck autochk /k:D /k:E /k:F /k:G /k:H /k:I /k:J /k:K /k:L /k:M
/k:N /k:O /k:p /k:Q /k:R /k:S /k:T /k:U /k:V /k:W /k:X /k:Y /k:Z *

....or to just disable it on D:, do this:

autocheck autochk /k:D *

Here's a .REG that does this:

<paste>

Windows Registry Editor Version 5.00

; This sets to...
;
; autocheck autochk /k:D /k:E /k:F /k:G /k:H /k:I /k:J /k:K /k:L /k:M
/k:N /k:O /k:p /k:Q /k:R /k:S /k:T /k:U /k:V /k:W /k:X /k:Y /k:Z *
;
; ...so as to AutoChk only C: after bad exits

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,\
00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,\
00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,\
00,00,00

; This is the Undo, to return to kill/bury/deny default:

; [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

; [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

; [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

</paste>

Watch out for line wrap in the above stuff!



--------------- ----- ---- --- -- - - -
Click to expand...
Tech Support: The guys who follow the
'Parade of New Products' with a shovel.
 
S

sharon669

I have 2 hard drives installed,
C = 80GB, D= 250Gb
Drive C is 1 year's old, drive D is brand new Western Digital, both
SATA interface.
Click to expand...

D: is > 137G, so OS must be OK with that.
Few days ago I formatted c partition, and installed fresh copy of XP
pro.
Click to expand...

What SP level?
- XP Gold (original "fit to ship" release) is lethal > 137G
- XP SP1 is safe > 137G in most but not all contexts
- XP SP2 is safe > 137G

Specifically, if XP "Gold" is EVER allowed to AutoChk or ChkDsk that
big D:, it is very likely to screw it up.

The contexts in which XP SP1 is unsafe > 137G usually apply where the
OS is booting and running off the drive, e.g. writing a RAM dump after
a system error, possibly hibernating to disk, etc.
I let the installation to reboot the computer, and came back after 10
min, then I saw CHKDSK output "Deleting index entry FILE_NAME in index
$_-_ of file ______."
http://www.planetnana.co.il/develop/CHKDSK.htm
I took this picture and stopped CHKDSK (to late fortunately...80% done)
The entire D drive was corrupted, some folders was deleted, and 90% of
the files are corrupt, folder structure remain the same, file names
remain the same,
I have backup from 2 month ago,
This picture shows FS difference (current and backup) :
http://www.planetnana.co.il/develop/CHKDSK1.htm
And this image shows the content corruption of typical html file (name
stayed the same):
http://www.planetnana.co.il/develop/CHKDSK2.htm
How is it possible??
Click to expand...

You allowed the duhfault behavior of XP, e.g. to "automatically fix
file system errors" on startup if volumes are marked as "dirty" (as
they may be after a bad exit).
Why will CHKDSK ruin perfect FS (previous XP with SP2 used this drive
with no problem)??
Click to expand...

AutoChk and ChkDsk /F are quite cavalier, operating on the ASSumption
they are Right, and that if they don't need something, then neither do
you. When they get it wrong, they get it spectacularly wrong... it's
a clasic dumb-ass machine thing.

After going "hmm, invalid file, delete" 2000 times, most humans would
re-check their assumptions, but "kill, bury, deny" AutoChk or ChkDsk
just keep on chugging until everything is irreversibly dead. After
all, what maintain an "undo" if you are "always right"?
Is there any way I can reverse CHKDSK operation ?
Click to expand...

Nope.

What you can do, is:
- make sure yopur XP is SP2 before reconnecting the 250G
- kill AutoChk by editing BootExecute appropriately

To disable AutoChk on all volumes except C:, do this...

autocheck autochk /k:D /k:E /k:F /k:G /k:H /k:I /k:J /k:K /k:L /k:M
/k:N /k:O /k:p /k:Q /k:R /k:S /k:T /k:U /k:V /k:W /k:X /k:Y /k:Z *

...or to just disable it on D:, do this:

autocheck autochk /k:D *

Here's a .REG that does this:

<paste>

Windows Registry Editor Version 5.00

; This sets to...
;
; autocheck autochk /k:D /k:E /k:F /k:G /k:H /k:I /k:J /k:K /k:L /k:M
/k:N /k:O /k:p /k:Q /k:R /k:S /k:T /k:U /k:V /k:W /k:X /k:Y /k:Z *
;
; ...so as to AutoChk only C: after bad exits

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,­\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,­\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,­\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,­\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,­\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,­\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,­\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,­\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,­\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,­\
00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,­\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,­\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,­\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,­\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,­\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,­\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,­\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,­\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,­\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,­\
00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager]
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\

00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2f,00,6b,00,3a,00,44,00,­\

20,00,2f,00,6b,00,3a,00,45,00,20,00,2f,00,6b,00,3a,00,46,00,20,00,2f,00,6b,­\

00,3a,00,47,00,20,00,2f,00,6b,00,3a,00,48,00,20,00,2f,00,6b,00,3a,00,49,00,­\

20,00,2f,00,6b,00,3a,00,4a,00,20,00,2f,00,6b,00,3a,00,4b,00,20,00,2f,00,6b,­\

00,3a,00,4c,00,20,00,2f,00,6b,00,3a,00,4d,00,20,00,2f,00,6b,00,3a,00,4e,00,­\

20,00,2f,00,6b,00,3a,00,4f,00,20,00,2f,00,6b,00,3a,00,50,00,20,00,2f,00,6b,­\

00,3a,00,51,00,20,00,2f,00,6b,00,3a,00,52,00,20,00,2f,00,6b,00,3a,00,53,00,­\

20,00,2f,00,6b,00,3a,00,54,00,20,00,2f,00,6b,00,3a,00,55,00,20,00,2f,00,6b,­\

00,3a,00,56,00,20,00,2f,00,6b,00,3a,00,57,00,20,00,2f,00,6b,00,3a,00,58,00,­\

20,00,2f,00,6b,00,3a,00,59,00,20,00,2f,00,6b,00,3a,00,5a,00,20,00,2a,00,00,­\
00,00,00

; This is the Undo, to return to kill/bury/deny default:

; [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

; [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

; [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager]
;
"BootExecute"=hex(7):61,00,75,00,74,00,6f,00,63,00,68,00,65,00,63,00,6b,00,­20,\
;
00,61,00,75,00,74,00,6f,00,63,00,68,00,6b,00,20,00,2a,00,00,00,00,00

</paste>

Watch out for line wrap in the above stuff!
--------------- ----- ---- --- -- - - -
Click to expand...

Tech Support: The guys who follow the
'Parade of New Products' with a shovel.


--------------- ----- ---- --- -- - - -- Hide quoted text -
Click to expand...

- Show quoted text -
Click to expand...

Thank you for the reg file, I merged it to the registry with no
success,
i uninstalled SP2, and I still get "dirty volume" prompt and CHKDSK
running,
i will reformat C drive, install XP (Gold edition), clone the drive to
image file (using Acronis True Image Home 10), upgrade to SP2, and
then let CHKDSK do its thing,
Hope it will help.
 

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.

Ask a Question

Similar Threads

CHKDSK NTFS file system corruption boot screen message flooding(SOLVED) 2
Please Help - Really weird File System or Chkdsk problem 5
odd chkdsk error 1
Chkdsk reports "The type of file system is RAW." etc. 1
CHKDSK failed to solve file system errors 9
Xp Pro SP2 disk space reporting 3
Is chkdsk useless 2
HELP System Volume Information and others 4

Top