On Fri, 2005-02-18 at 00:53 +0000, Edward Fearon wrote:
> Hi everybody
>
> This is my first posting to this email address so forgive me if I get
> anything wrong.
>
> I was using OOO1.1.3 in suse Linux 9.1, and working on a document natively.
> I added frames and lots of graphics and also have autosave as well as backup
> switched on. Last night I closed down OOo and no problem. This morning
> however, I tried to open it up and my CPU maxed out at 100%. I killed OOo,
> and all went back to normal. I tried opening it again, same issue.
[snipped]
I think that if you want to save the contents of this file, you should
unzip the document and save the contents.xml. To reconstruct the
document do the following:
1. Open and save an empty document, say, empty.sxw
2. mkdir reconstruct
3. cd reconstruct
4. unzip <path_to>/empty.sxw
5. rm content.xml
6. cp <path_to>/saved_content.xml .
7. zip -r ../reconstruct.sxw * (or whatever suse needs)
8. Use OOo to open reconstruct.swx and rebuild.
This is brute force, I know, but it does work when the contents.xml are
intact. That the OOo file got damaged in the first place is odd but
hardware failures even intermittent ones can do this. Ensure that you
have autosave and make backups enabled in your copy of OOo that way you
have a good chance for recovery. In the case of your system, I would
recommend that you throughly check its integrity especially memory.
--
Documentation Co-Lead
PLEASE - keep list traffic on the list. Email sent directly to me may
be ignored utterly.
"Dinna meddle wi' things ye ken nuthin' aboot!"
J.Herriot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
