Chkdsk from WinXp, starts at start up.

[thuffner3]

Morning all,
My system just started acting up. During a system start up WinXp wants to run the chkdsk utility. I bypass this as it has seemed to do things in the past that I was not happy with. Anyway.
Once into WinXP, I see that Chkdsk stops at a file called "mscvr71.dll"
It is a file associated with Yahoo messenger. It tells me that the file is corrupt or damaged and can't go any further. I tried to delete it. But that does not work.
Is there a work around for this?

TIA
Neil

 

[Lemon law]

First, try run---chkdsk /f which will not run until you restart windows---but might fix it---just plain chkdsk just checks but does not fix much of anything. If that does not work
then try second.

Second---download a good copy of mscvr71.dll for win xp from anyone of a number of dll download sites---then do a search for where windows places that dll.
Then rename your corrupt copies of that dll as something like mscvr71.bac---and then place your good downloaded copy of that dll into that directory.

 

[bsobel]

I bypass this as it has seemed to do things in the past that I was not happy with. Anyway.

Translation: My file system is corrupt and Windows wants to fix it. But since it's corrupt it I might lose data and I don't want to.

Let chkdsk run, it exists for a reason.

 

[thuffner3]

Originally posted by: bsobel

I bypass this as it has seemed to do things in the past that I was not happy with. Anyway.

Translation: My file system is corrupt and Windows wants to fix it. But since it's corrupt it I might lose data and I don't want to.

Let chkdsk run, it exists for a reason.

If chkdsk stops at the file from within windowsXP, why would I believe that it wouldn't stop from the start up?
There are multiple copies of the file MXVCR71.DLL on my system, Attempting to rename or delete this file yields the same message. FILE IS CORRUPT OR DAMAGED.

TIA
Neil

 

[bsobel]

Originally posted by: thuffner3

Originally posted by: bsobel

I bypass this as it has seemed to do things in the past that I was not happy with. Anyway.

Translation: My file system is corrupt and Windows wants to fix it. But since it's corrupt it I might lose data and I don't want to.

Let chkdsk run, it exists for a reason.

If chkdsk stops at the file from within windowsXP, why would I believe that it wouldn't stop from the start up?
There are multiple copies of the file MXVCR71.DLL on my system, Attempting to rename or delete this file yields the same message. FILE IS CORRUPT OR DAMAGED.

TIA
Neil

Chkdsk from within windows on the boot volume is scanning only and not doing any repair. You have to do the repair from executive mode while the disk is locked, hence it happening during the reboot.