today i try to open my saved *fm document but framemaker crashes all the time. The *.backup.fm also the same, *.recover.fm does not exist!
I need help as soon as possible!
It could be that the document is corrupt, or more likely, there is something in it that Frame doesn't like. You haven't specified which version of FM you are using. If you are using FM9 or FM10, try to close all pods and/or reset the workspace. Some pods require analysis of a document to populate their contents, so perhaps it is a bug in the GUI that is causing the crash.
Also, are you using any aftermarket plugins? If so, you might consider disabling those to see if they might have a bug that is causing the crash.
we use FM10 with the latest release and without any addons, plugins or staff like this. Please gif me a procedure to close all reqired pods and RESET the workspace! It sounds very interesting/helpful and easy to implement.
Sorry for my english, i'm not an native english speaker.
In the upper right corner of the FrameMaker window, next to the minimize/maximize/close buttons, there is the workspace button with the current workspace name as the text. Click that button and select Reset Workspace. For individual pods, you can double click the tabs to minimize them. Or, to close them completely, right-click a tab and select Close.
I do not know if this will help you. I only offer it as a suggestion because I know that the workspace tools do a bit of processing when you open a file and there could be something unexpected happening. It is what I would try first.
I don't have any more concrete ideas, especially as I am not at your computer to step through some other possibilities. If you want to send me the file, I'll try to open it, but I understand that you may not be able to send it. firstname.lastname@example.org.
If you can't send the file, I would just try everything imaginable to get FM to open it. Especially valuable would be routines that force a resave action afterwards. I might try things like:
- Rename it, give it a different extension, put it into different folders, etc.
- Open and close pods, toolbars, etc in different combinations
- Stick the file in a book and attempt a book update
- Attempt to insert a text inset from the file (from another file)
- Attempt to optimize the file for PDF
Be sure to back it up before messing around like this.
I'd like to try my hand at recovering this file. You can send it to email@example.com.
If you can't send the file can you please send a an image the first window of the file opened in MS Word, or better, a text editor. It will be mostly goblegook but there is sometimes some good information available by viewing the binary in a text editor.
Finally, if you are on a Mac or Unix/Linux or have access to either of these, you may be able to recover SOME information by opening a command line window and issuing this command:
strings -arch all filename.fm > strings.txt
Strings looks for ASCII strings in a binary file. With some clean up you can often recover most of the content, with some quirky search and replace routines to clean it up. Knowing GREP search and replace helps a lot.
No doubt there is an equivalent to the "strings" command on the PC, but I have no idea what that might be.
If you don't get a large part of your content from the stings command, give up. The file is very badly corrupted.