OpenOffice.org Saves my Day, Again
 | ||
 | Email weblog link | |
 | Discuss | |
 | Blog this |
Jonathan Gennick
May. 02, 2003 05:44 AM
Permalink
Awhile back I wrote about my experience installing OpenOffice.org for my family, pointing out that it's just the right introduction to open source for many people. I said then that OpenOffice.org saved my day, because it gave me an office suite I could freely install for my children. This week OpenOffice.org saved my day again, by recovering the contents of a corrupt, but very critical, Microsoft Word file.
It was Wednesday morning, 30 April. I was several pages into editing a chapter written in Microsoft Word when things took a bad turn. Word got very sluggish, and then "locked up". Windows Task Manager showed winword.exe monopolizing 99% of my CPU. The CPU (on my Thinkpad) got hot enough that the fan kicked in. Finally, Word died of some fatal error, dutifully reported the error to home base in Redmond, restarted itself, and "recovered" my file. Except Word didn't recover my file, not really. The problem began to repeat itself the moment I began typing again. I suspected some sort of internal corruption with my document file.
After several of Word's error, restart, recover cycles my heart began to sink. I was not keen to lose the file with all the edits I'd made so far. I went to Microsoft's web site and spent about 45 minutes downloading and installing all the available Microsoft Word updates, but to no avail. I tried saving to a new filename, but the problem persisted. I created a new, blank, Word file, and copied the chapter text from the problem file to the new file, but the corruption was copied too. I opened and saved the file using Word 2000, which I believe to be more stable than Word XP, but still the problem lived on.
Finally I got to thinking that perhaps Word was just too darn good at copying it's own files, and that I needed to pass my file through something other than Word in order to filter out the corruption. Opening the problem file in OpenOffice.org, I saw that the file contents looked intact, so I saved the file as an OpenOffice.org, sxw file. Then I opened that sxw file using OpenOffice.org, and saved the file again, this time as a Word file. With a bit of trepidation, I then opened the new Word file using Word and began typing. Everything worked! All my previous edits were intact. All the text was intact, including revision marks and embedded comments. The corruption was gone. Happy, and very relieved, I went to lunch.
I know that OpenOffice.org is not perfect—it has its own problems—but I find it very ironic that Word couldn't fix it's own file, that the only way I could find to save my Microsoft Word document was to filter it through a competing office suite, and an open source office suite at that. And this despite the fact that Microsoft has apparently gone to great lengths to add document recovery features to Word. My kudos to the OpenOffice.org team for developing a product robust enough to save my day, again.
Speaking of OpenOffice.org, I've been editing three books for which all the writing and editing has been done using OpenOffice.org The first of these books, C++ In A Nutshell by Ray Lischner, just went to print Tuesday this week. The other two OpenOffice.org-produced titles, which are moving through the production process now, are Essential CVS by Jennifer Vesperman, and UML Pocket Reference by Dan Pilone.
Jonathan Gennick is an O'Reilly Media, Inc. editor specializing in database and programming titles.
Showing messages 1 through 13 of 13.
-
Had also the same problem, same fix.
2003-05-13 01:08:35 anonymous2 [Reply | View]
With Win Word 97 I had a similar problem, The document suddenly started to crash any MSWord which tried to open it. The way through OO saved me the info.
Thanks OO guys.
bheufelder(at)bluewin.ch
-
Um...Open Office?
2003-05-09 07:47:17 anonymous2 [Reply | View]
As an O'Reilly contributor catering to a heavily geek crowd, shouldn't he have at least taken the time, before writing this article, to realize that Open Office is a trademarked name and that the office suite that is the basis for Sun's StarOffce is actually called OpenOffice.org?
-
Another rescue trick
2003-05-06 11:12:35 anonymous2 [Reply | View]
Another trick to rescue a corrupt file in MS Word is to turn on the paragraph marks with the toolbar, select all the document *except for the last paragraph mark*, and then copy and paste into a new document. A lot of information (so usually a lot of the corruption) is stored in that last paragraph mark.
Random Helpdesk Analyst and MS Word expert :)
-
Star Office 5.2 saved my bacon many times
2003-05-06 02:54:10 anonymous2 [Reply | View]
during my final year at university, I was trying out StarOffice 5.2 on my pc.A friend had corrupted a word 97 document, the night before the work was due in, so I thought I would try opening it in StarOffice. It opened fine other than a few formatting issues. Everyone was amazed. Since then I've always had a copy of StarOffice or OpenOffice on my PC.
-
Powerpoint
2003-05-05 05:29:13 anonymous2 [Reply | View]
Last year I had a similar problem with Powerpoint; it was unable to open a presentation produced by itself.
Impress used as a filter did the job without problems.
-
OO calc saved my day
2003-05-05 03:31:09 anonymous2 [Reply | View]
Same problem with an excel sheet.
Just opened it in OpenOffice Calc, and told my users to start installing this wonderful office suite.
They don't use it 100%, but we're slowly moving onto a clean, GPL office suite.
Thomas Mathiesen
-
openoffice
2003-05-03 19:03:10 anonymous2 [Reply | View]
So why is everyone still using Mircosoft word.
-
and the sxw file is half the size of the doc ;)
2003-05-03 14:09:21 anonymous2 [Reply | View]
Had the same experience ... and the sxw file is half the size (and sometimes even smaller) of the WORD doc file ;)
-
Word 97 couldn't open a Word 97 file
2003-05-03 06:07:41 arvedhs [Reply | View]
I recall about five or so years ago when I prepared a resume with Word 97. I was getting asistance from a professional on resume preparation, and this was meant to be something that she could review. Well, _her_ copy of Word 97 couldn't even open the file.
I know the floppy was OK, because I took it back home, and I was again able to look at the document on _my_ machine.
This sort of blew me away...Word 97 not being able to even open a Word 97 document.
In the final analysis, going along with previous comments, you can just do some hard work and open a Word file with a text editor or a hex editor, and start looking through all the bloat for your critical text.
-
OpenOffice saved my bacon with an Excel file
2003-05-02 10:44:43 kbixler [Reply | View]
Just last week, I had a similar problem with an Excel file. The data on the spreadsheet wasn't important, but the contents of the VBA macro I was writing would've taken me several hours to recreate. When I saved the spreadsheet at the end of the day (after having save multiple times throughout the day), I got a message saying that "Excel.exe has generated errors" and it quit. I rebooted, opened the spreadsheet, got the same error.
After about a half hour of poking around Microsoft's website it dawned on me that I could try opening it in OpenOffice. I opened it, did a "save as" and saved it to Excel format under a different name. When I re-opened it in Excel, some of the formatting was lost, but all my VBA code was there with all my changes, including the ones from the last save that killed Excel. I was very happy.
-
Word file rescues
2003-05-02 09:51:34 anonymous2 [Reply | View]
I've also used OO.org for this purpose. A couple of other tips for problem Word files:
- In Word, try saving to a non-DOC format file, like RTF, then open that file
- Keep a copy of AbiWord around to help rescue Word files in a similar fashion to the technique used with OO.org. I've had AbiWord work when OO.org or Word tricks wouldn't work
-
Monoculture
2003-05-02 09:22:29 nygard [Reply | View]
This is a fabulous example of the value gained when we move off of a monoculture. Word and OO, by virture of being different implementations, are not vulnerable to the same problems.
| Showing messages 1 through 13 of 13. |
Return to weblogs.oreilly.com.
Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc., disclaims any and all liabililty for that content, its accuracy, and opinions it may contain.
This work is licensed under a
Creative Commons License.
Dave Hall
FDRLab Data Recovery Centre Consultant
http://www.fdrlab.com/