Re: FM crashes on print book to file (surprise! No?)
On 6/4/07, Combs, Richard [EMAIL PROTECTED] wrote: Bodvar Bjorgvinsson wrote: I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. In case Dov Isaacs isn't online today to promptly chastise you, permit me. ;-) ROFLMAO! You are welcome. And don't you tell me you don't enjoy it! ;-) Multiple/mixed Acrobat installations are a very, very bad idea. Dov has warned countless times that it can lead to unpredictable and unstable behavior. When you installed FM, you should not have installed Distiller 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). And it has all been said many times before, _but_ this has usually not been a problem when you first install the newer version of Distiller and then the older one. Now, you need to completely uninstall both Acrobat 6 and Distiller 7. After that's done, either reinstall one, but not the other, or wait until you get Acrobat 8, and then install it. Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 first. And this is exactly what I am going to do. :-) I believe the .joboptions files have moved around some in recent releases, but I don't recall the details. Google techwr-l.com for joboptions locations or something like that. I seem to recall having to copy my old ones somewhere after moving to Acro 7. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. Bodvar ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
Thanks for the link, Art. It will come in handy. Bodvar On 6/4/07, Art Campbell [EMAIL PROTECTED] wrote: The job option info is here at adobe: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=333453 I actually like this bug a lot, because it lets you isolate one or two settings files and reserve them for use in FM, but still keep as many as you want available in Acrobat. Makes always getting the right setting file in FM easy, cause there aren't any options. Art On 6/4/07, Combs, Richard [EMAIL PROTECTED] wrote: Bodvar Bjorgvinsson wrote: I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. In case Dov Isaacs isn't online today to promptly chastise you, permit me. ;-) Multiple/mixed Acrobat installations are a very, very bad idea. Dov has warned countless times that it can lead to unpredictable and unstable behavior. When you installed FM, you should not have installed Distiller 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). Now, you need to completely uninstall both Acrobat 6 and Distiller 7. After that's done, either reinstall one, but not the other, or wait until you get Acrobat 8, and then install it. Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 first. I believe the .joboptions files have moved around some in recent releases, but I don't recall the details. Google techwr-l.com for joboptions locations or something like that. I seem to recall having to copy my old ones somewhere after moving to Acro 7. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
FM crashes on print book to file (surprise! No?)
On 6/4/07, Combs, Richard wrote: > Bodvar Bjorgvinsson wrote: > > > I am using the Distiller 7 that came with FM. I also have > > installed Acrbat 6 pro. The odd thing though is that it seems > > that FM can see the old joboptions, but Distiller 7 can only > > see the ones that reside in its own default folder. > > In case Dov Isaacs isn't online today to promptly chastise you, permit > me. ;-) > ROFLMAO! You are welcome. And don't you tell me you don't enjoy it! ;-) > Multiple/mixed Acrobat installations are a very, very bad idea. Dov has > warned countless times that it can lead to unpredictable and unstable > behavior. When you installed FM, you should not have installed Distiller > 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). > And it has all been said many times before, _but_ this has usually not been a problem when you first install the newer version of Distiller and then the older one. > Now, you need to completely uninstall both Acrobat 6 and Distiller 7. > After that's done, either reinstall one, but not the other, or wait > until you get Acrobat 8, and then install it. > > Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 > first. And this is exactly what I am going to do. :-) > > I believe the .joboptions files have moved around some in recent > releases, but I don't recall the details. Google techwr-l.com for > "joboptions locations" or something like that. I seem to recall having > to copy my old ones somewhere after moving to Acro 7. > > HTH! > Richard > > > -- > Richard G. Combs > Senior Technical Writer > Polycom, Inc. Bodvar
FM crashes on print book to file (surprise! No?)
Thanks for the link, Art. It will come in handy. Bodvar On 6/4/07, Art Campbell wrote: > The job option info is here at adobe: > > http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=333453 > > I actually like this "bug" a lot, because it lets you isolate one or > two settings files and reserve them for use in FM, but still keep as > many as you want available in Acrobat. Makes always getting the right > setting file in FM easy, cause there aren't any options. > > Art > > On 6/4/07, Combs, Richard wrote: > > Bodvar Bjorgvinsson wrote: > > > > > I am using the Distiller 7 that came with FM. I also have > > > installed Acrbat 6 pro. The odd thing though is that it seems > > > that FM can see the old joboptions, but Distiller 7 can only > > > see the ones that reside in its own default folder. > > > > In case Dov Isaacs isn't online today to promptly chastise you, permit > > me. ;-) > > > > Multiple/mixed Acrobat installations are a very, very bad idea. Dov has > > warned countless times that it can lead to unpredictable and unstable > > behavior. When you installed FM, you should not have installed Distiller > > 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). > > > > Now, you need to completely uninstall both Acrobat 6 and Distiller 7. > > After that's done, either reinstall one, but not the other, or wait > > until you get Acrobat 8, and then install it. > > > > Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 > > first. > > > > I believe the .joboptions files have moved around some in recent > > releases, but I don't recall the details. Google techwr-l.com for > > "joboptions locations" or something like that. I seem to recall having > > to copy my old ones somewhere after moving to Acro 7. > > > > HTH! > > Richard > > > > > > -- > > Richard G. Combs > > Senior Technical Writer > > Polycom, Inc. > > richardDOTcombs AT polycomDOTcom > > 303-223-5111 > > -- > > rgcombs AT gmailDOTcom > > 303-777-0436 > > -- > > > > > > > > > > > > > -- > Art Campbell art.campbell at > gmail.com > "... In my opinion, there's nothing in this world beats a '52 Vincent >and a redheaded girl." -- Richard Thompson > No disclaimers apply. > DoD 358 >
Re: FM crashes on print book to file (surprise! No?)
Bodvar, Actually, I was asking if you were using the Distiller instance that ships with FM, or if you have a complete Acrobat installation... Art On 6/1/07, Bodvar Bjorgvinsson [EMAIL PROTECTED] wrote: My FNTCACHE.DAT was only 767 kb this morning. I deleted it nevertheless and rebooted. Now it is the same size as before (767 kb). And I am trying to print again. Result: Crash at the same point as before, page 13 in chapter 3. :-( To answer Art's questions: Platform: WinXP SP2. Acrobat Configuration: I guess you mean the the PDF settings of FrameMaker (since this happens as FM is printing out the PS file. I am using what I call TS-OnlineA4.joboption and it looks like this (I hope the list admins don't find this to long): snip -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
Art, Thank you for your concern and sorry for the misunderstanding. I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. However, I have been promised Acrobat 8 within the week, so I will check that one out as I said in an earlier posting. If that does not resolve the problem I will probably have to iron the hard drive as we say over here and do a clean install of everything. Maybe the plethora of updates (security and insecurity) of XP is doing some tricks on the system that influences FM in a disturbing way. Anyway, this behavior seems to be increasing. I have never before had this sort of situation with FM 7.2 that I could not find a way around with the help of the friends on the list or otherwise. For the present manual, this is not a great problem. I had printed the book several weeks ago in the same way without any problems, but found out that I had been a little bit hasty about the TOC, so I had to update the book and rerun the TOC and replaced it in the pdf file for printing. Now I am only trying to print the book in order to have the hyperlinking work in the pdf. But since it is primarily a hard copy document, this is not such a big issue. Bodvar On 6/4/07, Art Campbell [EMAIL PROTECTED] wrote: Bodvar, Actually, I was asking if you were using the Distiller instance that ships with FM, or if you have a complete Acrobat installation... Art On 6/1/07, Bodvar Bjorgvinsson [EMAIL PROTECTED] wrote: My FNTCACHE.DAT was only 767 kb this morning. I deleted it nevertheless and rebooted. Now it is the same size as before (767 kb). And I am trying to print again. Result: Crash at the same point as before, page 13 in chapter 3. :-( ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
The job option info is here at adobe: http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=333453 I actually like this bug a lot, because it lets you isolate one or two settings files and reserve them for use in FM, but still keep as many as you want available in Acrobat. Makes always getting the right setting file in FM easy, cause there aren't any options. Art On 6/4/07, Combs, Richard [EMAIL PROTECTED] wrote: Bodvar Bjorgvinsson wrote: I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. In case Dov Isaacs isn't online today to promptly chastise you, permit me. ;-) Multiple/mixed Acrobat installations are a very, very bad idea. Dov has warned countless times that it can lead to unpredictable and unstable behavior. When you installed FM, you should not have installed Distiller 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). Now, you need to completely uninstall both Acrobat 6 and Distiller 7. After that's done, either reinstall one, but not the other, or wait until you get Acrobat 8, and then install it. Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 first. I believe the .joboptions files have moved around some in recent releases, but I don't recall the details. Google techwr-l.com for joboptions locations or something like that. I seem to recall having to copy my old ones somewhere after moving to Acro 7. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: FM crashes on print book to file (surprise! No?)
Bodvar Bjorgvinsson wrote: I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. In case Dov Isaacs isn't online today to promptly chastise you, permit me. ;-) Multiple/mixed Acrobat installations are a very, very bad idea. Dov has warned countless times that it can lead to unpredictable and unstable behavior. When you installed FM, you should not have installed Distiller 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). Now, you need to completely uninstall both Acrobat 6 and Distiller 7. After that's done, either reinstall one, but not the other, or wait until you get Acrobat 8, and then install it. Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 first. I believe the .joboptions files have moved around some in recent releases, but I don't recall the details. Google techwr-l.com for joboptions locations or something like that. I seem to recall having to copy my old ones somewhere after moving to Acro 7. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 -- ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
FM crashes on print book to file (surprise! No?)
Bodvar, Actually, I was asking if you were using the Distiller instance that ships with FM, or if you have a complete Acrobat installation... Art On 6/1/07, Bodvar Bjorgvinsson wrote: > My FNTCACHE.DAT was only 767 kb this morning. I deleted it > nevertheless and rebooted. Now it is the same size as before (767 kb). > And I am trying to print again. > Result: Crash at the same point as before, page 13 in chapter 3. :-( > > To answer Art's questions: > Platform: WinXP SP2. > Acrobat Configuration: I guess you mean the the PDF settings of > FrameMaker (since this happens as FM is printing out the PS file. > I am using what I call TS-OnlineA4.joboption and it looks like this (I > hope the list admins don't find this to long): > -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358
FM crashes on print book to file (surprise! No?)
Art, Thank you for your concern and sorry for the misunderstanding. I am using the Distiller 7 that came with FM. I also have installed Acrbat 6 pro. The odd thing though is that it seems that FM can see the old joboptions, but Distiller 7 can only see the ones that reside in its own default folder. However, I have been promised Acrobat 8 within the week, so I will check that one out as I said in an earlier posting. If that does not resolve the problem I will probably have to "iron" the hard drive as we say over here and do a clean install of everything. Maybe the plethora of updates (security and insecurity) of XP is doing some tricks on the system that influences FM in a disturbing way. Anyway, this behavior seems to be increasing. I have never before had this sort of situation with FM 7.2 that I could not find a way around with the help of the friends on the list or otherwise. For the present manual, this is not a great problem. I had printed the book several weeks ago in the same way without any problems, but found out that I had been a little bit hasty about the TOC, so I had to update the book and rerun the TOC and replaced it in the pdf file for printing. Now I am only trying to print the book in order to have the hyperlinking work in the pdf. But since it is primarily a hard copy document, this is not such a big issue. Bodvar On 6/4/07, Art Campbell wrote: > Bodvar, > > Actually, I was asking if you were using the Distiller instance that > ships with FM, or if you have a complete Acrobat installation... > > Art > > On 6/1/07, Bodvar Bjorgvinsson wrote: > > My FNTCACHE.DAT was only 767 kb this morning. I deleted it > > nevertheless and rebooted. Now it is the same size as before (767 kb). > > And I am trying to print again. > > Result: Crash at the same point as before, page 13 in chapter 3. :-( > > >
FM crashes on print book to file (surprise! No?)
Bodvar Bjorgvinsson wrote: > I am using the Distiller 7 that came with FM. I also have > installed Acrbat 6 pro. The odd thing though is that it seems > that FM can see the old joboptions, but Distiller 7 can only > see the ones that reside in its own default folder. In case Dov Isaacs isn't online today to promptly chastise you, permit me. ;-) Multiple/mixed Acrobat installations are a very, very bad idea. Dov has warned countless times that it can lead to unpredictable and unstable behavior. When you installed FM, you should not have installed Distiller 7 (assuming you'd prefer the full Acrobat 6 to just Distiller 7). Now, you need to completely uninstall both Acrobat 6 and Distiller 7. After that's done, either reinstall one, but not the other, or wait until you get Acrobat 8, and then install it. Do *not* install Acrobat 8 without removing Acrobat 6 and Distiller 7 first. I believe the .joboptions files have moved around some in recent releases, but I don't recall the details. Google techwr-l.com for "joboptions locations" or something like that. I seem to recall having to copy my old ones somewhere after moving to Acro 7. HTH! Richard -- Richard G. Combs Senior Technical Writer Polycom, Inc. richardDOTcombs AT polycomDOTcom 303-223-5111 -- rgcombs AT gmailDOTcom 303-777-0436 --
Re: FM crashes on print book to file (surprise! No?)
I had the same problem this morning: Frame crashed whenever I tried to create a PDF, using various methods (save as PDF, print to PS, print to Adobe PDF printer driver instance, single Frame file or book, Frame 7.2 and Frame 7.0). I didn't have the character dropout problem, but I did follow Dov's recommendation and deleted the FNTCACHE.DAT file and rebooted. Everything works like a charm now. By the way, this FNTCACHE.DAT file was 2.3 GB, is that normal? -- Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto bvba Asselsstraat 65 9031 Gent Belgium T: +32 494 12 01 89 F: +32 9 366 50 32 BTW (VAT) BE 0886.192.394 skype: yves.barbion ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
My FNTCACHE.DAT was only 767 kb this morning. I deleted it nevertheless and rebooted. Now it is the same size as before (767 kb). And I am trying to print again. Result: Crash at the same point as before, page 13 in chapter 3. :-( To answer Art's questions: Platform: WinXP SP2. Acrobat Configuration: I guess you mean the the PDF settings of FrameMaker (since this happens as FM is printing out the PS file. I am using what I call TS-OnlineA4.joboption and it looks like this (I hope the list admins don't find this to long): /ASCII85EncodePages false /AllowTransparency false /AutoPositionEPSFiles true /AutoRotatePages /All /Binding /Left /CalGrayProfile (Gray Gamma 2.2) /CalRGBProfile (sRGB IEC61966-2.1) /CalCMYKProfile (U.S. Web Coated \050SWOP\051 v2) /sRGBProfile (sRGB IEC61966-2.1) /CannotEmbedFontPolicy /Warning /CompatibilityLevel 1.4 /CompressObjects /Tags /CompressPages true /ConvertImagesToIndexed true /PassThroughJPEGImages true /CreateJDFFile false /CreateJobTicket false /DefaultRenderingIntent /Default /DetectBlends true /ColorConversionStrategy /LeaveColorUnchanged /DoThumbnails false /EmbedAllFonts true /EmbedJobOptions false /DSCReportingLevel 0 /SyntheticBoldness 1.00 /EmitDSCWarnings false /EndPage -1 /ImageMemory 1048576 /LockDistillerParams false /MaxSubsetPct 100 /Optimize true /OPM 1 /ParseDSCComments true /ParseDSCCommentsForDocInfo true /PreserveCopyPage true /PreserveEPSInfo false /PreserveHalftoneInfo false /PreserveOPIComments false /PreserveOverprintSettings true /StartPage 1 /SubsetFonts true /TransferFunctionInfo /Apply /UCRandBGInfo /Remove /UsePrologue true /ColorSettingsFile (Color Management Off) /AlwaysEmbed [ true ] /NeverEmbed [ true ] /AntiAliasColorImages false /DownsampleColorImages true /ColorImageDownsampleType /Bicubic /ColorImageResolution 192 /ColorImageDepth -1 /ColorImageDownsampleThreshold 1.04167 /EncodeColorImages true /ColorImageFilter /DCTEncode /AutoFilterColorImages true /ColorImageAutoFilterStrategy /JPEG /ColorACSImageDict /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] /ColorImageDict /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] /JPEG2000ColorACSImageDict /TileWidth 256 /TileHeight 256 /Quality 15 /JPEG2000ColorImageDict /TileWidth 256 /TileHeight 256 /Quality 15 /AntiAliasGrayImages false /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 192 /GrayImageDepth -1 /GrayImageDownsampleThreshold 1.5 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] /GrayImageDict /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] /JPEG2000GrayACSImageDict /TileWidth 256 /TileHeight 256 /Quality 15 /JPEG2000GrayImageDict /TileWidth 256 /TileHeight 256 /Quality 15 /AntiAliasMonoImages true /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 192 /MonoImageDepth 4 /MonoImageDownsampleThreshold 1.5 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict /K -1 /AllowPSXObjects true /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.0 0.0 0.0 0.0 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.0 0.0 0.0 0.0 ] /PDFXOutputIntentProfile (None) /PDFXOutputCondition () /PDFXRegistryName (http://www.color.org) /PDFXTrapped /False /Description /JPN FEFF3053306e8a2d5b9a306f300130d330b830cd30b9658766f8306e8868793a304a3088307353705237306b90693057305f00200050004400460020658766f830924f5c62103059308b3068304d306b4f7f75283057307e305930023053306e8a2d5b9a30674f5c62103057305f00200050004400460020658766f8306f0020004100630072006f0062006100740020304a30883073002000520065006100640065007200200035002e003000204ee5964d30678868793a3067304d307e30593002 /DEU
FM crashes on print book to file (surprise! No?)
I had the same problem this morning: Frame crashed whenever I tried to create a PDF, using various methods (save as PDF, print to PS, print to Adobe PDF printer driver instance, single Frame file or book, Frame 7.2 and Frame 7.0). I didn't have the "character dropout" problem, but I did follow Dov's recommendation and deleted the FNTCACHE.DAT file and rebooted. Everything works like a charm now. By the way, this FNTCACHE.DAT file was 2.3 GB, is that normal? -- Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto bvba Asselsstraat 65 9031 Gent Belgium T: +32 494 12 01 89 F: +32 9 366 50 32 BTW (VAT) BE 0886.192.394 skype: yves.barbion
FM crashes on print book to file (surprise! No?)
My FNTCACHE.DAT was only 767 kb this morning. I deleted it nevertheless and rebooted. Now it is the same size as before (767 kb). And I am trying to print again. Result: Crash at the same point as before, page 13 in chapter 3. :-( To answer Art's questions: Platform: WinXP SP2. Acrobat Configuration: I guess you mean the the PDF settings of FrameMaker (since this happens as FM is printing out the PS file. I am using what I call TS-OnlineA4.joboption and it looks like this (I hope the list admins don't find this to long): << /ASCII85EncodePages false /AllowTransparency false /AutoPositionEPSFiles true /AutoRotatePages /All /Binding /Left /CalGrayProfile (Gray Gamma 2.2) /CalRGBProfile (sRGB IEC61966-2.1) /CalCMYKProfile (U.S. Web Coated \050SWOP\051 v2) /sRGBProfile (sRGB IEC61966-2.1) /CannotEmbedFontPolicy /Warning /CompatibilityLevel 1.4 /CompressObjects /Tags /CompressPages true /ConvertImagesToIndexed true /PassThroughJPEGImages true /CreateJDFFile false /CreateJobTicket false /DefaultRenderingIntent /Default /DetectBlends true /ColorConversionStrategy /LeaveColorUnchanged /DoThumbnails false /EmbedAllFonts true /EmbedJobOptions false /DSCReportingLevel 0 /SyntheticBoldness 1.00 /EmitDSCWarnings false /EndPage -1 /ImageMemory 1048576 /LockDistillerParams false /MaxSubsetPct 100 /Optimize true /OPM 1 /ParseDSCComments true /ParseDSCCommentsForDocInfo true /PreserveCopyPage true /PreserveEPSInfo false /PreserveHalftoneInfo false /PreserveOPIComments false /PreserveOverprintSettings true /StartPage 1 /SubsetFonts true /TransferFunctionInfo /Apply /UCRandBGInfo /Remove /UsePrologue true /ColorSettingsFile (Color Management Off) /AlwaysEmbed [ true ] /NeverEmbed [ true ] /AntiAliasColorImages false /DownsampleColorImages true /ColorImageDownsampleType /Bicubic /ColorImageResolution 192 /ColorImageDepth -1 /ColorImageDownsampleThreshold 1.04167 /EncodeColorImages true /ColorImageFilter /DCTEncode /AutoFilterColorImages true /ColorImageAutoFilterStrategy /JPEG /ColorACSImageDict << /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] >> /ColorImageDict << /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] >> /JPEG2000ColorACSImageDict << /TileWidth 256 /TileHeight 256 /Quality 15 >> /JPEG2000ColorImageDict << /TileWidth 256 /TileHeight 256 /Quality 15 >> /AntiAliasGrayImages false /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 192 /GrayImageDepth -1 /GrayImageDownsampleThreshold 1.5 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict << /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] >> /GrayImageDict << /QFactor 0.76 /HSamples [2 1 1 2] /VSamples [2 1 1 2] >> /JPEG2000GrayACSImageDict << /TileWidth 256 /TileHeight 256 /Quality 15 >> /JPEG2000GrayImageDict << /TileWidth 256 /TileHeight 256 /Quality 15 >> /AntiAliasMonoImages true /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 192 /MonoImageDepth 4 /MonoImageDownsampleThreshold 1.5 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict << /K -1 >> /AllowPSXObjects true /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.0 0.0 0.0 0.0 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.0 0.0 0.0 0.0 ] /PDFXOutputIntentProfile (None) /PDFXOutputCondition () /PDFXRegistryName (http://www.color.org) /PDFXTrapped /False /Description << /JPN /DEU /FRA /PTB /DAN /NLD /ESP /SUO /ITA /NOR /SVE /ENU >> >> setdistillerparams << /HWResolution [96 96] /PageSize [595.276 841.890] >> setpagedevice There is nothing suspicious to me here except maybe this part: /AlwaysEmbed [ true ] /NeverEmbed [ true ] Actually this is a Distiller 6 settings and resides in the Acrobat Distiller 6 folder, but it has worked for me before even though FM 7.2 comes with Distiller 7. Any problems with this anyone? Bodvar On 6/1/07, Yves Barbion wrote: > I had the same problem this morning: Frame crashed whenever I tried to > create a PDF, using various methods (save as PDF, print to PS, print to > Adobe PDF printer driver instance, single Frame file or book, Frame 7.2 and > Frame 7.0). > > I didn't have the "character dropout" problem, but I did follow Dov's > recommendation and deleted the FNTCACHE.DAT file and rebooted. Everything > works like a charm now. By the way, this FNTCACHE.DAT file was 2.3 GB, is > that normal? > > > > -- > Yves Barbion > Documentation Architect >
FM crashes on print book to file (surprise! No?)
I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). On a few occasions I have plagued the list with my complaints about FM (mainly 7.2) crashing on printing a book to ps. I have now spent half the day trying to produce an online PDF with bookmarks. No problem printing to ps without bookmarks, so we have that one in the clear. It started by FM crashing on a certain file (chapter 3) on a specific page, no matter whether I had the files open or not. Having them open only added the extra work of removing the recovery files. Having removed these three times, I went for the closed files printing. Also I MIF-washed the files but go no better results. I tested the offending file by itself and it printed to file with bookmarks ok, but printing from the book, it always crashed FM at the same page. A couple of pages earlier, around the point where the pdf started to lack contents seriously (yes, I managed to pdf the ps part, and I also had a look at the ps in GSView which showed less content), there was a OLEd Visio file. I found the pdf and eps-ed it and replaced the graphics. Same result. I found a Xref marker on the crashing page and deleted it, and now it went a couple of pages further. I removed FM 7.2 (plus patch), restarted the PC and installed all (FM + patches) again. No change. I started a new document, imported the formats and then the contents and replaced the file. Now it went all the way down to one of the last chapters, where it crashed again with the same messages. No Xref on that page, only a table (and this file got a lot of tables). Now I did as with chapter 3, started a new document, copied etc. and started the printing again. And what now. Now I got as far as to the same page in chapter 3 as in the first tries. I am out of guesses. What can I do? And why cannot FM give any humanly understandable hints? For 8.0, why not add internal checkpoints that tells us what exactly is causing the crashing? It should not be that difficult when the print process hits an offending item to have the application point that out. Is there a malfunction in the Xref marker, is the graphic not kosher, etc. Any help out there, please? I am going home now. Will check the mail in the morning. Bodvar Bjorgvinsson Supervisor Publishing Air Atlanta Icelandic. http://www.airatlanta.com ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
What's your platform and Acrobat configuration? On 5/31/07, Bodvar Bjorgvinsson [EMAIL PROTECTED] wrote: I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). On a few occasions I have plagued the list with my complaints about FM (mainly 7.2) crashing on printing a book to ps. I have now spent half the day trying to produce an online PDF with bookmarks. No problem printing to ps without bookmarks, so we have that one in the clear. It started by FM crashing on a certain file (chapter 3) on a specific page, no matter whether I had the files open or not. Having them open only added the extra work of removing the recovery files. Having removed these three times, I went for the closed files printing. Also I MIF-washed the files but go no better results. I tested the offending file by itself and it printed to file with bookmarks ok, but printing from the book, it always crashed FM at the same page. A couple of pages earlier, around the point where the pdf started to lack contents seriously (yes, I managed to pdf the ps part, and I also had a look at the ps in GSView which showed less content), there was a OLEd Visio file. I found the pdf and eps-ed it and replaced the graphics. Same result. I found a Xref marker on the crashing page and deleted it, and now it went a couple of pages further. I removed FM 7.2 (plus patch), restarted the PC and installed all (FM + patches) again. No change. I started a new document, imported the formats and then the contents and replaced the file. Now it went all the way down to one of the last chapters, where it crashed again with the same messages. No Xref on that page, only a table (and this file got a lot of tables). Now I did as with chapter 3, started a new document, copied etc. and started the printing again. And what now. Now I got as far as to the same page in chapter 3 as in the first tries. I am out of guesses. What can I do? And why cannot FM give any humanly understandable hints? For 8.0, why not add internal checkpoints that tells us what exactly is causing the crashing? It should not be that difficult when the print process hits an offending item to have the application point that out. Is there a malfunction in the Xref marker, is the graphic not kosher, etc. Any help out there, please? I am going home now. Will check the mail in the morning. Bodvar Bjorgvinsson Supervisor Publishing Air Atlanta Icelandic. http://www.airatlanta.com ___ -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FM crashes on print book to file (surprise! No?)
Hi Bodvar, have you tried switching off Generate Tagged PDF in PDF Setup Tags? Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto bvba Asselsstraat 65 9031 Gent Belgium T: +32 494 12 01 89 F: +32 9 366 50 32 BTW (VAT) BE 0886.192.394 skype: yves.barbion Bodvar Bjorgvinsson wrote: I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). On a few occasions I have plagued the list with my complaints about FM (mainly 7.2) crashing on printing a book to ps. I have now spent half the day trying to produce an online PDF with bookmarks. No problem printing to ps without bookmarks, so we have that one in the clear. It started by FM crashing on a certain file (chapter 3) on a specific page, no matter whether I had the files open or not. Having them open only added the extra work of removing the recovery files. Having removed these three times, I went for the closed files printing. Also I MIF-washed the files but go no better results. I tested the offending file by itself and it printed to file with bookmarks ok, but printing from the book, it always crashed FM at the same page. A couple of pages earlier, around the point where the pdf started to lack contents seriously (yes, I managed to pdf the ps part, and I also had a look at the ps in GSView which showed less content), there was a OLEd Visio file. I found the pdf and eps-ed it and replaced the graphics. Same result. I found a Xref marker on the crashing page and deleted it, and now it went a couple of pages further. I removed FM 7.2 (plus patch), restarted the PC and installed all (FM + patches) again. No change. I started a new document, imported the formats and then the contents and replaced the file. Now it went all the way down to one of the last chapters, where it crashed again with the same messages. No Xref on that page, only a table (and this file got a lot of tables). Now I did as with chapter 3, started a new document, copied etc. and started the printing again. And what now. Now I got as far as to the same page in chapter 3 as in the first tries. I am out of guesses. What can I do? And why cannot FM give any humanly understandable hints? For 8.0, why not add internal checkpoints that tells us what exactly is causing the crashing? It should not be that difficult when the print process hits an offending item to have the application point that out. Is there a malfunction in the Xref marker, is the graphic not kosher, etc. Any help out there, please? I am going home now. Will check the mail in the morning. Bodvar Bjorgvinsson Supervisor Publishing Air Atlanta Icelandic. http://www.airatlanta.com ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/yves.barbion%40gmail.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: FM crashes on print book to file (surprise! No?)
I posted a similar message to the framers, Acrobat, and InDesign lists. I had Frame 7.2 p158 and Acrobat 7.0.8 (not 7.0.9) installed for quite some time with no problems. I then upgraded my CS2 with CS3 upgrade, which came with Acrobat 8. I then got frequent, random Frame crashes when PDFing as you describe. I went through similar troubleshooting steps to no avail. I also use Publi PDF (http://www.grafikhuset.net/international/) to create custom PDFs from Frame. I got crashes from Frame when printing both to the Adobe PDF printer instance and to a Publi PDF print queue. Publi PDF's tech support suspected either a Windows GDI font problem or a FrameMaker 'PostScript injection' problem (i.e. when Frame injects private PostScript data into the data stream generated via Windows GDI). In reply to the character dropout issue with Frame, Dov Isaacs replied to the list that the fix is to delete the C:\WINDOWS\system32\FNTCACHE.DAT file and reboot, and ideally write a script that deletes that file every time you power down. Dov further stated that, Since there is nothing that FrameMaker as a program can do to corrupt that system file or even open it, the problems are probably secondary to some issue associated with FrameMaker's novel use of its own character set in combination with standard Windows GDI calls. I put those two issues together, did what they said, and also tweaked Adobe PDF Printer Properties based on recommendations for older versions of Distiller. And, if you're on Acrobat 8, see Adobe Tech Note 333453 regarding where to place custom joboptions settings. Now, after all that, for some reason, I still get a Frame crash at the book level IF it's the first PDF I try to create after bootup. If, however, I PDF a single Frame file first (so far, always with success), then PDF the whole book, it works for me. That's my workaround. Hope it helps. Jay -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Art Campbell Sent: Thursday, May 31, 2007 2:19 PM To: Bodvar Bjorgvinsson Cc: framers@lists.frameusers.com Subject: Re: FM crashes on print book to file (surprise! No?) What's your platform and Acrobat configuration? On 5/31/07, Bodvar Bjorgvinsson [EMAIL PROTECTED] wrote: I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). On a few occasions I have plagued the list with my complaints about FM (mainly 7.2) crashing on printing a book to ps. I have now spent half the day trying to produce an online PDF with bookmarks. No problem printing to ps without bookmarks, so we have that one in the clear. It started by FM crashing on a certain file (chapter 3) on a specific page, no matter whether I had the files open or not. Having them open only added the extra work of removing the recovery files. Having removed these three times, I went for the closed files printing. Also I MIF-washed the files but go no better results. I tested the offending file by itself and it printed to file with bookmarks ok, but printing from the book, it always crashed FM at the same page. A couple of pages earlier, around the point where the pdf started to lack contents seriously (yes, I managed to pdf the ps part, and I also had a look at the ps in GSView which showed less content), there was a OLEd Visio file. I found the pdf and eps-ed it and replaced the graphics. Same result. I found a Xref marker on the crashing page and deleted it, and now it went a couple of pages further. I removed FM 7.2 (plus patch), restarted the PC and installed all (FM + patches) again. No change. I started a new document, imported the formats and then the contents and replaced the file. Now it went all the way down to one of the last chapters, where it crashed again with the same messages. No Xref on that page, only a table (and this file got a lot of tables). Now I did as with chapter 3, started a new document, copied etc. and started the printing again. And what now. Now I got as far as to the same page in chapter 3 as in the first tries. I am out of guesses. What can I do? And why cannot FM give any humanly understandable hints? For 8.0, why not add internal checkpoints that tells us what exactly is causing the crashing? It should not be that difficult when the print process hits an offending item to have the application point that out. Is there a malfunction in the Xref marker, is the graphic not kosher, etc. Any help out there, please? I am going home now. Will check the mail in the morning. Bodvar Bjorgvinsson Supervisor Publishing Air Atlanta Icelandic. http://www.airatlanta.com ___ -- Art Campbell [EMAIL PROTECTED] ... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl. -- Richard Thompson No disclaimers apply. DoD 358
FM crashes on print book to file (surprise! No?)
I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). On a few occasions I have plagued the list with my complaints about FM (mainly 7.2) crashing on printing a book to ps. I have now spent half the day trying to produce an online PDF with bookmarks. No problem printing to ps without bookmarks, so we have that one in the clear. It started by FM crashing on a certain file (chapter 3) on a specific page, no matter whether I had the files open or not. Having them open only added the extra work of removing the recovery files. Having removed these three times, I went for the closed files printing. Also I MIF-washed the files but go no better results. I tested the "offending" file by itself and it printed to file with bookmarks ok, but printing from the book, it always crashed FM at the same page. A couple of pages earlier, around the point where the pdf started to lack contents seriously (yes, I managed to pdf the ps part, and I also had a look at the ps in GSView which showed less content), there was a OLEd Visio file. I found the pdf and eps-ed it and replaced the graphics. Same result. I found a Xref marker on the crashing page and deleted it, and now it went a couple of pages further. I removed FM 7.2 (plus patch), restarted the PC and installed all (FM + patches) again. No change. I started a new document, imported the formats and then the contents and replaced the file. Now it went all the way down to one of the last chapters, where it crashed again with the same messages. No Xref on that page, only a table (and this file got a lot of tables). Now I did as with chapter 3, started a new document, copied etc. and started the printing again. And what now. Now I got as far as to the same page in chapter 3 as in the first tries. I am out of guesses. What can I do? And why cannot FM give any humanly understandable hints? For 8.0, why not add internal checkpoints that tells us what exactly is causing the crashing? It should not be that difficult when the print process hits an offending item to have the application point that out. Is there a malfunction in the Xref marker, is the graphic not kosher, etc. Any help out there, please? I am going home now. Will check the mail in the morning. Bodvar Bjorgvinsson Supervisor Publishing Air Atlanta Icelandic. http://www.airatlanta.com
FM crashes on print book to file (surprise! No?)
What's your platform and Acrobat configuration? On 5/31/07, Bodvar Bjorgvinsson wrote: > I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). > > On a few occasions I have plagued the list with my complaints about FM > (mainly 7.2) crashing on printing a book to ps. I have now spent half > the day trying to produce an online PDF with bookmarks. No problem > printing to ps without bookmarks, so we have that one in the clear. > > It started by FM crashing on a certain file (chapter 3) on a specific > page, no matter whether I had the files open or not. Having them open > only added the extra work of removing the recovery files. Having > removed these three times, I went for the closed files printing. > > Also I MIF-washed the files but go no better results. > > I tested the "offending" file by itself and it printed to file with > bookmarks ok, but printing from the book, it always crashed FM at the > same page. > > A couple of pages earlier, around the point where the pdf started to > lack contents seriously (yes, I managed to pdf the ps part, and I also > had a look at the ps in GSView which showed less content), there was a > OLEd Visio file. I found the pdf and eps-ed it and replaced the > graphics. Same result. > > I found a Xref marker on the crashing page and deleted it, and now it > went a couple of pages further. > > I removed FM 7.2 (plus patch), restarted the PC and installed all (FM > + patches) again. > No change. > > I started a new document, imported the formats and then the contents > and replaced the file. Now it went all the way down to one of the last > chapters, where it crashed again with the same messages. No Xref on > that page, only a table (and this file got a lot of tables). > > Now I did as with chapter 3, started a new document, copied etc. and > started the printing again. And what now. Now I got as far as to the > same page in chapter 3 as in the first tries. > > I am out of guesses. What can I do? And why cannot FM give any humanly > understandable hints? > > For 8.0, why not add internal checkpoints that tells us what exactly > is causing the crashing? It should not be that difficult when the > print process hits an offending item to have the application point > that out. Is there a malfunction in the Xref marker, is the graphic > not kosher, etc. > > Any help out there, please? I am going home now. Will check the mail > in the morning. > > Bodvar Bjorgvinsson > Supervisor Publishing > Air Atlanta Icelandic. > http://www.airatlanta.com > ___ > -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358
FM crashes on print book to file (surprise! No?)
Hi Bodvar, have you tried switching off "Generate Tagged PDF" in PDF Setup > Tags? Yves Barbion Documentation Architect Adobe-Certified FrameMaker Instructor Scripto bvba Asselsstraat 65 9031 Gent Belgium T: +32 494 12 01 89 F: +32 9 366 50 32 BTW (VAT) BE 0886.192.394 skype: yves.barbion Bodvar Bjorgvinsson wrote: > I am starting to get annoyed with FrameMaker. (Sorry for a lengthy > message). > > On a few occasions I have plagued the list with my complaints about FM > (mainly 7.2) crashing on printing a book to ps. I have now spent half > the day trying to produce an online PDF with bookmarks. No problem > printing to ps without bookmarks, so we have that one in the clear. > > It started by FM crashing on a certain file (chapter 3) on a specific > page, no matter whether I had the files open or not. Having them open > only added the extra work of removing the recovery files. Having > removed these three times, I went for the closed files printing. > > Also I MIF-washed the files but go no better results. > > I tested the "offending" file by itself and it printed to file with > bookmarks ok, but printing from the book, it always crashed FM at the > same page. > > A couple of pages earlier, around the point where the pdf started to > lack contents seriously (yes, I managed to pdf the ps part, and I also > had a look at the ps in GSView which showed less content), there was a > OLEd Visio file. I found the pdf and eps-ed it and replaced the > graphics. Same result. > > I found a Xref marker on the crashing page and deleted it, and now it > went a couple of pages further. > > I removed FM 7.2 (plus patch), restarted the PC and installed all (FM > + patches) again. > No change. > > I started a new document, imported the formats and then the contents > and replaced the file. Now it went all the way down to one of the last > chapters, where it crashed again with the same messages. No Xref on > that page, only a table (and this file got a lot of tables). > > Now I did as with chapter 3, started a new document, copied etc. and > started the printing again. And what now. Now I got as far as to the > same page in chapter 3 as in the first tries. > > I am out of guesses. What can I do? And why cannot FM give any humanly > understandable hints? > > For 8.0, why not add internal checkpoints that tells us what exactly > is causing the crashing? It should not be that difficult when the > print process hits an offending item to have the application point > that out. Is there a malfunction in the Xref marker, is the graphic > not kosher, etc. > > Any help out there, please? I am going home now. Will check the mail > in the morning. > > Bodvar Bjorgvinsson > Supervisor Publishing > Air Atlanta Icelandic. > http://www.airatlanta.com > ___ > > > You are currently subscribed to Framers as yves.barbion at gmail.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/yves.barbion%40gmail.com > > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. >
FM crashes on print book to file (surprise! No?)
I posted a similar message to the framers, Acrobat, and InDesign lists. I had Frame 7.2 p158 and Acrobat 7.0.8 (not 7.0.9) installed for quite some time with no problems. I then upgraded my CS2 with CS3 upgrade, which came with Acrobat 8. I then got frequent, random Frame crashes when PDFing as you describe. I went through similar troubleshooting steps to no avail. I also use Publi PDF (http://www.grafikhuset.net/international/) to create custom PDFs from Frame. I got crashes from Frame when printing both to the Adobe PDF printer instance and to a Publi PDF print queue. Publi PDF's tech support suspected "either a Windows GDI font problem or a FrameMaker 'PostScript injection' problem (i.e. when Frame injects private PostScript data into the data stream generated via Windows GDI)". In reply to the "character dropout" issue with Frame, Dov Isaacs replied to the list that the fix is to delete the C:\WINDOWS\system32\FNTCACHE.DAT file and reboot, and ideally write a script that deletes that file every time you power down. Dov further stated that, "Since there is nothing that FrameMaker as a program can do to corrupt that system file or even open it, the problems are probably secondary to some issue associated with FrameMaker's novel use of its own character set in combination with standard Windows GDI calls." I put those two issues together, did what they said, and also tweaked Adobe PDF Printer Properties based on recommendations for older versions of Distiller. And, if you're on Acrobat 8, see Adobe Tech Note 333453 regarding where to place custom joboptions settings. Now, after all that, for some reason, I still get a Frame crash at the book level IF it's the first PDF I try to create after bootup. If, however, I PDF a single Frame file first (so far, always with success), then PDF the whole book, it works for me. That's my workaround. Hope it helps. Jay -Original Message- From: framers-bounces+jrush=c-cor@lists.frameusers.com [mailto:framers-bounces+jrush=c-cor.com at lists.frameusers.com] On Behalf Of Art Campbell Sent: Thursday, May 31, 2007 2:19 PM To: Bodvar Bjorgvinsson Cc: framers at lists.frameusers.com Subject: Re: FM crashes on print book to file (surprise! No?) What's your platform and Acrobat configuration? On 5/31/07, Bodvar Bjorgvinsson wrote: > I am starting to get annoyed with FrameMaker. (Sorry for a lengthy message). > > On a few occasions I have plagued the list with my complaints about FM > (mainly 7.2) crashing on printing a book to ps. I have now spent half > the day trying to produce an online PDF with bookmarks. No problem > printing to ps without bookmarks, so we have that one in the clear. > > It started by FM crashing on a certain file (chapter 3) on a specific > page, no matter whether I had the files open or not. Having them open > only added the extra work of removing the recovery files. Having > removed these three times, I went for the closed files printing. > > Also I MIF-washed the files but go no better results. > > I tested the "offending" file by itself and it printed to file with > bookmarks ok, but printing from the book, it always crashed FM at the > same page. > > A couple of pages earlier, around the point where the pdf started to > lack contents seriously (yes, I managed to pdf the ps part, and I also > had a look at the ps in GSView which showed less content), there was a > OLEd Visio file. I found the pdf and eps-ed it and replaced the > graphics. Same result. > > I found a Xref marker on the crashing page and deleted it, and now it > went a couple of pages further. > > I removed FM 7.2 (plus patch), restarted the PC and installed all (FM > + patches) again. > No change. > > I started a new document, imported the formats and then the contents > and replaced the file. Now it went all the way down to one of the last > chapters, where it crashed again with the same messages. No Xref on > that page, only a table (and this file got a lot of tables). > > Now I did as with chapter 3, started a new document, copied etc. and > started the printing again. And what now. Now I got as far as to the > same page in chapter 3 as in the first tries. > > I am out of guesses. What can I do? And why cannot FM give any humanly > understandable hints? > > For 8.0, why not add internal checkpoints that tells us what exactly > is causing the crashing? It should not be that difficult when the > print process hits an offending item to have the application point > that out. Is there a malfunction in the Xref marker, is the graphic > not kosher, etc. > > Any help out there, please? I am going home now. Will check the mail > in the morning. > > Bodvar Bjorgvinsson > Supervisor Publishing > Air Atlanta Icelandic. > http://www.airatlanta.com >
