It is worse than I suspected. There was no error saving or closing the files. OpenOffice is crashing while attempting to open the ODT files. Then is unable to recover them. I tried to open two other files in the same directory all with the same results. I have a screenshot, if you would like me to send it.
Maurice, I have no idea what you are referring to. This is the same font size I have always used which is set to ‘Normal’. I can read it fine without my glasses, nor is it overly large. You are the first person that has complained.
On Mon, 03 Sep 2012 19:02:10 -0400, Maurice Howe <email@example.com> wrote:
> Good. Now that 'incubator' has re-sent your note, we can all read it.
> -----Original Message-----
> From: Maurice Howe [mailto:firstname.lastname@example.org]
> Sent: Monday, September 03, 2012 6:48 PM
> To: email@example.com; firstname.lastname@example.org
> Subject: RE: OpenOffice unable to restore file or open it
> Good grief! Don't use 4 point type for ANYthing!! You waste your time
> everybody else's.
>Maurice D. Howe
> 616 Lacey Drive
> Endwell, NY 13760
> From: Rod Lockwood [mailto:email@example.com]
> Sent: Monday, September 03, 2012 6:22 PM
> To: OpenOffice Users Mailing List
> Subject: OpenOffice unable to restore file or open it
> I have a text document that apparently did not close properly when
> OpenOffice. Starting OpenOffice 3.41 does not trigger the file
> process. When I click on the file to open it, OpenOffice crashes because
> there is already a shadow file in existance. It begins the file
> but does not recover the shadow file. So I wind up not being able to do
> anything. Deleting the shadow file does not work. OpenOffice cannot open
> document, even though it creates a new shadow document.
> This is why I never liked this system. I much prefer the system used by
> text editor and the way it was done in the old days. Simply save the
> file to
> disc as a normal file with a .BAK extension every 15 minutes (or whatever
> your preference is). That way if the original file is corrupt, you simply
> delete the corrupt file, rename the backed up file and you are good to
> At the most you lose your allotted time of work. And saving the file
> manually obviously didn't make a difference. So forget about any
> lectures on
> how I should manually save my work periodically.
> It does not interfere with the undo process. It does not create multiple
> files, just the one back up file. A simple text editor is able to do
> this. I
> have never lost a file using this old-fashioned system of automatically
> backing up the file. Now I will have to recreate this file from scratch
> from memory.