FrameMaker crashes when selecting print book file

[asuroiu]

I have recenctly update to TCS4. FrameMaker crashes when I select Print Book but will produce a PDF is I select Save As PDF.

Anyone else experiencing this and have a resolution?

[Jeff_Coatsworth]

SetPrint is a free plug-in that sets your default Windows printer to the AdobePDF one while inside FM - meanwhile, your apps running at the same time can continue to have their physical printer set as the Windows default too. No more flipping back and forth or having to set AdobePDF as the default each time you run FM. Great tool.

So the individual files can print to PDF, but the book doesn't? You talk about printing to .ps - do you need to control something in the PDF creation that you aren't just printing straight to PDF?

[Rob from Mustang land]

Dear Jeff:

I am familiar with the free plug-in, used it for a while. I only print to pdf these days, apart from the occasional letter.

Since the pdf converter is always the default printer I did not use the PrintSet freebie after my last hard drive crash.

I will try it again, but please see that other people are having the same problem in this forum. Yes, I do need the extra control. Especially as I use many referenced graphics, which crash the Save to pdf option.

Rob..

[Jeff_Coatsworth]

Just had some time to play with a new install of TCS4 on my Win7 Pro 64-bit laptop too - I'm getting the same crash as everybody else too when printing the book - FM11.0.0.380.

Used a brand new FM11 test book and files to play with - it crashes with the Print Book command and the Print Selected Files command too. Just tried it with a legacy FM10 book too, same error. Wheels have fallen off the wagon with this one.

[Bob_Niland]

> ... on my Win7 Pro 64-bit laptop ...

Since Win7/64 Pro supports the optional XP Mode, is there any chance you could install XPM and try it?

[Jeff_Coatsworth]

Sorry Error, I didn't realize you were asking me ;>)

I don't have the time to try that out, but I suspect it wouldn't make any difference because FM10 is running fine on the same box.

[Harpreet_seehra1]

Its working fine at my end.

Lets try run Framemaker in the full Administrative mode ,it migt fix it.

Harpreet.

[Jeff_Coatsworth]

Just tried that - no luck, still crashes. I'm still trying to find Priyank's flag to turn off CMYK

[Harpreet_seehra1]

when you save as pdf,the pdf setup box appears and at the bottom there is an option to toggle between CMYK and RGB

[Guest]

FYI...already set to RGB on my machine. No change...still inelegantly crashes. Poof!

[Jeff_Coatsworth]

got it - tried it both ways - still crashes on Print Book

[Guest]

Tried running as Administrator...still crashes. no change in behavior

[Rob from Mustang land]

Gott sei Dank!

At last somebody will take it seriously,

Rob

[DieterGust]

Switch Fm to structured mode (settings) and try again.

The solution I just got from Adobe worked for me.

Hth Dieter

[Rob from Mustang land]

That is great

I am still waiting for Adobe to contact me.

Does one switch in mid stream?

Or exit and change?

[Jeff_Coatsworth]

You can make your changes through the Edit > Preferences menu. FM will want you to exit & restart FM to switch over. I just tried it and it does get you further when trying the Print Book command, but the screen was all shrunken and dialog boxes unreadable. I’d still like to work in Unstructured and not have this crash happen. I’ve forwarded my crash logs and test book to Adobe this morning, but haven’t heard anything back yet from my contact there.

[DieterGust]

>. 2 just tried it and it does get you further when trying the Print Book command, but the screen was all shrunken and dialog boxes unreadable."

The question is: Can switching to structured mode be seen as a reliable workaround?

What do you mean with "shrunken and unreadable dialog boxes"

Your answer irritates me: The dialog boxes are in both modes the same.
"Structured FrameMaker" adds several pods and menu items but the Print Book dialog is not affected at all.
So if printing works using Structured FrameMaker one might define a certain workspace which hides all structured functionality.

Dieter

[Jeff_Coatsworth]

Sorry, I probably should have taken a screen shot to illustrate what I was getting, but I ran out of time.

After I switched the Preferences over to Structured and restarted FM, I got a floating toolbar about half-height, up overtop of my main menu bar. When I went to print the book, a warning dialog popped up about something needing to be saved, but the dialog box was in a micro-font that couldn't be read very well. I don't know if I needed to play around with the screen size or load in another workspace to fix the screen appearance.

What are the implications of working in an unstructured manner in structured FM? I have no experience with structured FM and all my docs are unstructured.

[DieterGust]

Seen from a non-structured point of view there should be no difference at all, except some "strange" new menu items, some new pods and the Structure Window.
Structured FM Mode activates in addition to the new menus and pods a kind of "layer" covering relationships between elements originally coming from an EDD (Element Definition Document - another FM construct not relevant for Unstructured FM).
If you open an unstructured document this structure layer is empty.  So once again: Working with unstructured documents using Structured FM Mode should make no difference at all.

All annoying toolbars, pods and addtional windows you may close and you save this UI then as  a new workspace (you may use also the empty workspace).

If you switch the printer during the print dialog, then a message appears saying that the font information for your system has been changed. If you can't read this kind of alerts the UI system font may be damaged, but this has nothing to do with the "harmless" switching between "Structured" and "Unstructured FrameMaker".

Dieter

[Jeff_Coatsworth]

Good to know - I'll have to poke around and see what's causing my screen to look so weird. At least this is a temp workaround for those needing to print books (not me - I rarely print a book to PDF these days). It will buy Adobe some time to work on the issue in the unstructured interface.

[DieterGust]

You can be sure that Adobe will react on this issue. FM has been well known for its stability - this issue dosn't fit at all to this image - so switching to Structured FM can be a workaround on the fly only.

[Jeff_Coatsworth]

Kapil Verma (Sr. Product Manager FM) has just posted an update over on the Frameusers mailing list with attachments for a workspace environment for an unstructured user to work in a structured mode without most of the structured menus and toolbars hanging around. Here's the link to his posting:

http://lists.frameusers.com/pipermail/framers/2012-September/026796.html

Update - Arnis has posted it here with the attachments - http://forums.adobe.com/thread/1073069

Message was edited by: Jeff_Coatsworth

[Arnis Gubins]

Adobe have identified the bug in FM11 and full info, along with the required files, is posted in the following Forum message:

FM 11 - Book Printing to .PS issue - Cause and solution

This is the same content as referred to by Jeff.

[Kapil_Verma]

Hello Everyone,

this issue has been fixed by a patch that was released in early October. Your system should notify you automatically about the availability of this update. Alternatively, you can download and install the update from http://www.adobe.com/support/downloads/detail.jsp?ftpID=5506

thanks,

Kapil Verma

[Rob from Mustang land]

I would like to expand on this. First thanks Kapil for the list serv post. I received no other notification from Adobe so other customers might not be aware of the fix.

Second TCS4 purchasers are entitled to Acrobat 11 as well, which includes another discrete FM11 update, a companion piece.

I would like to add that the fix works perfectly for this happy camper.

After using structured FM, I notice that FM11 in unstructured creates an unasked for HTML mapping page. If you have many paragraph formats,

these mapping pages go over Frame's generous allowance of 100 reference pages, which may explain soem of the reports of a slow pdf creation.

Rob Shell

p.s.

I am deleting all my HTML mapping passages.