Re: Corrupt File

philo wrote:
"Bill Sharpe" <wfsnopam@xxxxxxxxxxxx> wrote in message
news:Oim3eXqTIHA.4104@xxxxxxxxxxxxxxxxxxxxxxx
philo wrote:
"Bill Sharpe" <wfsnopam@xxxxxxxxxxxx> wrote in message
news:eefj4fkTIHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
I am having a problem trying to delete a leftover file, eqnedt32.cnt,
on
my D: drive. Any attempt to rename, move, or delete the file gives me a
"File or folder is corrupt and unreadable. Please run chkdsk" message.
I
have also tried to remove the containing folder, but I get the same
result.
I have run chkdsk /f and /r on drive D:. Neither finds any bad sectors.

My concern is that every few days I get a Windows startup message
saying
Windows needs to check disk d:. If I let it go ahead and check it runs
chkdsk and doesn't find any errors. I could live with the one bad file
here if Windows wouldn't insist on offering to check the disk at
startup. This happens a couple times a week at startup.

I am using Windows XP Pro with SP2. I have tried ccleaner, which
indicates that it is removing the file or its containing folder, but
the
offending file is still there after ccleaner runs.

Any suggestions are welcome.

Go to the website of the harddrive's mfg
andf get their diagnostic utility and run it ..
the drive may be failing


A Google search located this thread:
http://www.wilderssecurity.com/showthread.php?t=145505

The corrupt file is from a recovered Acronis True Image backup.
Apparently this is not a hard disk problem. There are several solutions
offered in the thread, including using Linux to delete the offending
file or creating another True Image file backup without the offending
file, formatting the drive, and restoring the backup.

I will investigate the first approach, which appears much less drastic
than the second one...

Bill


Depending where the file is...
you may be able to boot to the repair console and delete it from there


The file is not on the system drive. According to one message in the lengthy thread I quoted, this approach has been tried and has not worked. But thanks for the suggestion.

Bill
.

Relevant Pages

  • Re: Error at logon screen prevents access, Error code 0x80040057 pops up
    ... Microsoft Knowledge Base Article: ... When Chkdsk Runs at Startup ... To quote Jerold Schulman - Windows: ...
    (microsoft.public.windowsxp.basics)
  • Re: chdsk runs out of space trying to recover $Extend$ObjId
    ... The down pointer of current index entry with length 0x18 is invalid. ... Eventually chkdsk displays a message to the effect that is has ... If I avoid the chkdsk I can boot into windows xp pro, ... $Extend\$ObjId is corrupt. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Cannot open volume for direct access
    ... When you schedule the Chkdsk utility to run a startup, ... Windows has finished checking the disk. ...
    (microsoft.public.windowsxp.general)
  • Re: File Corrupt Message(s) -- Fix that, make more
    ... I don't recall the initial error, only Windows' offer to fix it. ... _really_ wanky is when Chkdsk gets going and begins reporting lots of ... My XP Pro system reported a corrupt file, ...
    (microsoft.public.windowsxp.general)
  • Re: Corrupt File
    ... Please run chkdsk" message. ... My concern is that every few days I get a Windows startup message ...
    (microsoft.public.windowsxp.help_and_support)