Grief with FrameMaker 11

Subject: Grief with FrameMaker 11
From: Ken Poshedly <poshedly -at- bellsouth -dot- net>
To: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 26 May 2015 20:06:22 +0000 (UTC)

We are having one heck of a problem with FrameMaker 11 files spontaneously converting into MIF files as well as FrameMaker book files crashing (closing) FrameMaker on three of the platforms in my group. Neither of these problems occur on my computer.

We're all running HP computers -- Windows XP on my "HP Pavilion" and Windows 7 on the three "HP Pro" computers. And we all create and work with files on the same network server. (I know some of you frown on that, but it works for us.)

And we now are even more attentive to making sure we're referencing our image files instead of embedding them, and trying to keep those image files down below several hundred kilobytes at most, though a larger one does occasionally sneak in.


Here's what happened today:

Chris in my department used the proper command sequence to successfully open Framemaker, then a Framemaker book that he's been working on for a week or so then sucessfully open all chapters in that book (via the book command to open all files). But this morning, most the 10 chapter files were now MIF files.

A check of the file listing for this book in Windows 7 showed all of them as ".fm" files along with the usual "Fm" icon. To check them, I opened each with Notepad and all opened with lines of readable, editable text. This is bad because that meant they were actually MIF files.

So one-by-one, I did a "save-as" to convert them back into actual FrameMaker files; I used Notepad once more to check and they all opened with the usual upper ASCII stuff and gobbledygook that meant they were NOT MIF files. This is good.

Later this afternoon:

1. I watched every keystroke and mouse movement that Chris in my department used to successfully open Framemaker, then that same Framemaker book and then sucessfully open all chapters in that book (via the book command to open all files). They were all FM files. So far so good.

2. Right after left-clicking on Print Book, then choosing Adobe as the printer (to create a postscript file), and checking the usual boxes to Print to File and Create Acrobat Data, and then Print, Frame crashed.

3. So I repeated steps 1 and 2 to successfully create not only the postscript file but then run that file through Adobe Distiller to get a totally proper pdf file.

There seems to be no pattern regarding file sizes or anything else. And as stated above, none of these MIF conversions or crash problems occur on my computer.

Is there a FM 11.0 bug or other cause that any of you may be aware of or do any of you have any suggestions. One of my FM "guru" friends suggested updating the HP Pro computer graphics card drivers.

These problems are, unfortunately, intermittent. Like one of the Murphy's Laws says, "The repair man will never have seen a problem quite like yours."

Help please?

Ken in Atlanta
Adobe TCS 5: Get the Best of both worlds: modern publishing and best in class XML \ DITA authoring |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Previous by Author: Freelancing and EIN
Next by Author: Re: Grief with FrameMaker 11
Previous by Thread: Re: What's the benefit in getting a PMP certification in project management?
Next by Thread: RE: Grief with FrameMaker 11

What this post helpful? Share it with friends and colleagues:

Sponsored Ads