Copy link to clipboard
Copied
I'm sorry if this information was covered elsewhere, I didn't get any results when I searched for it...and I know there is information in these forums about crashes!
Anyway... After upgrading my 32-bit Windows Vista system (Service Pack 1) to FrameMaker 10, I started having frequent crashes (mostly when I save all the chapters in my book and then try to save the book itself).
My co-worker also has a 32-bit Windows Vista system, but he started experiencing the crashes BEFORE the Version 10 upgrade. His FrameMaker crashes when he is using a completely different application (for example, he minimizes FrameMaker and replies to an e-mail message).
I have 4 GB of RAM with a 3.00 GHz processor
I checked FrameMaker for upgrades, but it said that there weren't any available. Our Systems team keeps our OS updated, so I'm sure it is up-to-date. Can anyone tell me what else I can do to prevent these crashes?????
Copy link to clipboard
Copied
I have a similar system with the exception of the XP service pack (I have SP3 installed). FM used to crash much more often before then it does now. However, there have many variables in my system so I can only guess. Maybe a move from SP1 to SP3 might help system stability in regards to FrameMaker.
Even SP1a is at least seven years old.
However, if you do upgrade to SP3, visit this forum thread for the inevitable fonts issue.
Copy link to clipboard
Copied
Julie,
You did not tell us which FrameMaker version you were using previously. I assume it was FrameMaker 7.x.
I noticed a certain instability with books and generated files that were were created in pre-Unicode FrameMaker versions (until 7.2) and opened in Unicode-aware FrameMaker (8.0 or later). I experienced crashes with some books mainly during the book update procedure. An influencing factor was whether all files were open during book update. But it was not consistent, so it could also be connected to some content in the documents.
I deleted those old migrated books and generated files and recreated them; that solved my issues.
Another option for really old files would be a »MIF wash«: Save as MIF and open the MIF files again, saving them as .fm over the originals.
- Michael
Copy link to clipboard
Copied
Another thing: Was your FrameMaker 10 installed from DVD (or CD-ROM)?
If so, could you please re-install the product after copying the installer to hard disk. It was reported somewhere that the Adobe installer may not receive proper notification from the underlying Microsoft install tools if something with the optical medium fails. This apparently could lead to incomplete/instable installations.
- Michael
Copy link to clipboard
Copied
My apologies! I upgraded from Version 9.
I did use the CD to install the upgrade. My coworker uninstalled and reinstalled his software yesterday and it seemed to correct the problem. I will do so today.
Thank you so much for your feedback.
Copy link to clipboard
Copied
I'd try the MIF wash first....
It may very well fix the problem -- this isn't an uncommon problem.
It's become my SOP to MIF wash all older version files....