... Frame 10 has a charming habit of losing formatting when it crashes. Frame has always had that "feature". The only thing that is usually safe to open after a crash is your previously saved .fm file, or a .backup file. If Frame managed to create a .recover, open it separately, and only use it copy back the latest local edits. Go no longer between saves than you care to re-create. Be advised that Frame can sometime crash DURING save. Check the timestamp on the .fm file in question to see if it is now questionable. I primarily use FM7.1 on Unix, and it crashes a lot, due apparently to some degenerate intersection of our odd page layout and massively networked document files. Sometimes I get a .recover, usually not. Sometimes I get a crash message on the console (usually 7103). Sometimes the crash crashes, so we routinely have a non-writeable "core" directory in every document dir, to prevent time-consuming creation of useless huge core dump files. Sometimes Frame just winks out without a trace. In addition to managing any damage to the .fm file, it is not uncommon for the crash to screw up the page numbering declared in the .book file for all .fm files in the book (open or not), that are after the .fm file that crashed. Easy to fix, but wierd. Each document directory here has, among other subdirectories, one which is used to store working/backup/recover files after crashes. Because Frame crashes can be due to latent corruption in the .fm file, you can be editing a book and discover way late that major sections have turned to garbage. Having archives helps.
... View more