Corrupted files

Incognitia · Newbie Joined: 28 Jan 2012 Posts: 2

So, we have several .odt and .doc files that have recently decided they won't open.

Been trying this on two Win 7 64 bit comps running OOo 3; have also tried unzipping with WinRar and using Notepad, Wordpad and MS Works.

Some of the corrupted files when instructed to open don't respond, and when attempting to copy them I get "Error 0x80070570: The file or directory is corrupted and unreadable". Others open quite happily, but show as hundreds of pages of ###########.

Other files on the same disk open quite happily.

So, I am at a loss - is this a Windows problem, an OOo problem, a virus?
How can I predict which files will be corrupted, and which will be fine?
Is there any way to recover the corrupted files?

There are many, many hours of work in .doc and .odt files on this computer, so finding some resolution to at least ensure no more files become corrupted is vital.

Thanks in advance.

floris_v · Posted: Sat Jan 28, 2012 3:00 pm Post subject:

Files filled with #'s are lost, sadly. See 22 pages term paper replaced with pound signs. The cause for such corruption may be a crash of the computer just as Writer is writing a file to disk.
I can't help with the other error - except that it probably occurs in files saved in Word format, and then it might have the same cause. Is that a laptop and do you frequently suffer from power loss or do you have other crashes?
_________________
LibreOffice 3.6.3; OOo 3.4.1 on Windows Vista
Join the Official community forum - in several languages, including Nederlandstalig forum

Incognitia · Newbie Joined: 28 Jan 2012 Posts: 2

Okay, so one file out of three is dead. I think we've managed to recover most of the content for that from other sources, so it's manageable.

The laptop it's on is remarkably well behaved, and has been consistently powered and not crashed since the last time the documents were opened successfully.

I'd love to find a way to recover the files, but as I said, the biggest concern for me is finding out what the cause was and trying to avoid it, without having to check every .odt and .doc file on the whole hard drive...