FrameMaker 11 very slow to create PDF

Hello All
Using FrameMaker 11 (TCS4) on Windows Vista SP2 (32-bit), dual-core 2.8GHz, 4GB RAM.
I have a book file with nine chapters, title, TOC and Index, adding up to about 550 pages when printed. It used to take about 10 minutes to create PDF using FrameMaker 9. Now that we have upgraded to FM11 it takes over 90 minutes. The chapters contain screenshots as well as text, and I am printing the whole book as one file.
I have tried this using Save Book As (then choosing PDF), printing to Adobe PDF as .ps and then distilling, and Save as PDF, all with similar results.
Then, because I was working across our network, I copied all the files to my local drive and tried again. Same results. I have also set the printer to not start printing until all pages are spooled.
Watching the activity in the printer dialog, I see that pages are spooled quickly (about 1-2 sec/page) if the chapter file is small (up to 40 pages). But in the case of large files (up to 140 pages) each page takes over 10 seconds to spool, and some take 20 seconds. I wondered if this indicates insufficient RAM?
I've read lots of useful information about PDF creation from FM, and tried most of the recommendations (including Dov's recommendations for printer/Distiller settings from years back), but nothing makes a difference.
Any recommendations are welcome. Thanks.
Roger Shuttleworth
London, Canada

Based on the number of recent complaints about PDF rendering performance, it rather looks like there might be a problem with the newer FM releases. I can't personally say, because we're still on FM7/Unix, and don't use our FM9/Win764 versions for production.
Printing to .ps and Distilling separately should help at least get your FM GUI prompt back sooner, and unless Adobe has broken it, the full Acrobat Pro product can be set to have Distiller "watch" directories for new .ps files, and generate PDFs without any user attention.
It would be interesting to know if the rendering process is multi-threaded to any significant degree. if so, having more cores in your CPU would help.
I'm also wondering if FM11 gets any benefit from installation on Win64.
And at the risk of stimulating conspiracy theories, would using Framemaker Server print any faster? I at least presume that it would free up the workstations during print.
Per-core CPU clocks hit the wall 10 years ago. Per core perf has been creeping up since then, with most of the per-chip gain in the form of more cores. Application coders, however, seem to be assuming that per-core performance is still ramping up at 2x@2yr as a side effect of Moore's Conjecture.

Similar Messages

  • Very slow rederting of PDF files

    Keynote rendering of pdf gives amazing quality. However with a PDF which contains scientific data and many line objects it can be very very slow. For example a file which is 500KB can take 11 sec to render.
    Exporting from Illustrator to tiff or PSD (150 dpi) usually result in noticable quality reduction, and also takes all the advantage of being able to presernt PDF in the first place.
    Is there any simple workaround?
    Thanks
    Mickey
    PB alu 1.67   Mac OS X (10.4.7)  

    It seems that there a difference between the PDF rendering engine of keynote (which I suspect is the same one of preview) and the one of Adobe. The same PDF could be compressed to a very small file and open in a snap in Acrobat. But for preview it took few second to render. After cutting bits in an out I found the problematic object and remade it. This sloved the problem.
    As a side effect I found out that by using Show package content, you can find the pasted PDF and edit it directly with Illustrator, without having to cut and paste or save and insert.

  • Slow to create pdfs over 50 pages or so

    Hello,
    I'm having an issue where users are trying to create pdfs from docs that are 50-150 pages.  In the progress, it seems like the first 50 pages or so usually goes quickly, but then after that it slows down to a page every few seconds.  They're using Acrobat 8 Pro, but it seems to occur with Acrobat 6 as well.  Has anyone got any suggestions for how to speed this up?
    Thanks

    Since they are printing to the Adobe PDF printer, my suggestion won't help since that is what they are doing. Try to empty the TEMP folder and see if that helps. I have also seen folks who open the world and expect every home to work great (OK, a word comparison, but maybe close a few other applications or look if antivirus or such is hogging the processor. The process monitor from Sysinternals (MS now has this) is useful for looking at the processor use. Simply using ctrl-alt-del and viewing the processes (click on the CPU button 2 times to put the most active programs at top) that may be hogging memory.

  • Acrobat 9.3.3 very slow to open PDFs in Windows 7

    Ever since I upgraded to 9.3.3 (standard version) pdfs have been extremely low to open up.  Is this a known issue?  A cursory search through the knowledge base did not reveal anything recent that would suggest that this is common.
    Any help would be most appreciated.

    Had the same problem on Windows XP after Installing Patch 9.3.3.
    The problem could be solved by reseting the user settings.
    Rename the following REGKEYS:
    HKEY_CURRENT_USER \ Software \ Adobe \ Acrobat Reader
    HKEY_CURRENT_USER \ Software \ Adobe \ Adobe Acrobat
    to
    HKEY_CURRENT_USER \ Software \ Adobe \ Acrobat Reader_Old
    HKEY_CURRENT_USER \ Software \ Adobe \ Adobe Acrobat_Old
    The keys are created at the next start with the basic settings.

  • OSX lion is very slow after joining pdfs in preview.

    I regualrly have to join several PDF files into one document. They way I am doing this at the moment is through preview i.e. simply dragging and dopping the files over one another in the thumbnail side bar. However, at some point the computer invariably freezes showing me the spinning wheel of death for perhaps 15mins. Some times I cannot revover and have to force a hard reboot. Other times, I can get it to soft reboot after waiting for ages. The funny thing is the resulting file is fine since I can access after it after performing the reboot.
    Any ideas why this is and how I can avoid it since it wasts alot of time.
    Specs of my MacBook are:
    Processor 2.8 Ghz Intel Core i7
    Memory 4GB 1333 Mhz DDR3
    I have 600 GB of hard disc space free
    I am running OSX 10.7.3
    The total size of the documents I want to join amounted to less than 4 Mb so I don't think I should be running out of memory.
    Any help appreciated
    Cheers
    Jim

    Thank for the reply. There were actually a huge number of messages in the console when I was trying to perform this action. I've filtered them here by the keyword preview:
    16/05/2012 21:05:34.854 Preview: snapshot of document took: 0.00633901 secs, calling unblockUserInteraction
    16/05/2012 21:05:36.871 Preview: writing of document took: 2.01655 secs, success = YES
    16/05/2012 21:06:14.834 Preview: snapshot of document took: 0.000631988 secs, calling unblockUserInteraction
    16/05/2012 21:06:15.253 Preview: writing of document took: 0.418326 secs, success = YES
    16/05/2012 21:06:54.000 kernel: [829|501] Preview          async. scan: #'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/window_1.data' act=0x00000006 rsn='ETYP1' ln='1457'
    16/05/2012 21:07:06.000 kernel: [829|501] Preview          async. scan: #'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/window_2.data' act=0x00000006 rsn='ETYP1' ln='1457'
    16/05/2012 21:07:18.000 kernel: [829|501] Preview          async. scan: @'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/data.data' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:07:18.000 kernel: [776|501] mdworker         async. scan: #'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/window_2.data' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:07:30.000 kernel: [829|501] Preview          async. scan: @'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/windows.plist' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:08:06.000 kernel: [776|501] mdworker         async. scan: #'/Users/foo/Library/Containers/com.apple.Preview/Data/Library/Saved Application State/com.apple.Preview.savedState/data.data' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:08:18.000 kernel: [857|501] SFLSharedPrefsTo async. scan: #'/Users/foo/Library/Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSh aredFileList.plist' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:08:30.000 kernel: [857|501] SFLSharedPrefsTo async. scan: #'/Users/foo/Library/Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSh aredFileList.plist.lockfile' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:08:42.000 kernel: [857|501] SFLSharedPrefsTo async. scan: @'/Users/foo/Library/Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSh aredFileList.plist.f9KnTo8' act=0x00000002 rsn='ETYP1' ln='1457'
    16/05/2012 21:08:54.000 kernel: [857|501] SFLSharedPrefsTo async. scan: @'/Users/foo/Library/Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSh aredFileList.plist' act=0x00000003 rsn='ETYP1' ln='1457'
    Actually, I noticed that imdediately after these messages, the following message was printed to the console hundreds of times:
    16/05/2012 21:25:14.119 esets_daemon: warning[00de0000]: Cannot accept connection: Too many open files
    This coencided with the slow down so perhaps preview is interfering with my antivirus software some how?
    Again, any help appreciated.
    Cheers
    Jim

  • Very slow printout of pdf

    PLEASE HELP! I am using a Microsoft Windows XP with an Epson DX4850 printer. My business letterhead is on a pdf and normally prints out fairly quickly, until that is, I recently upgraded to Adobe Reader 8. Subsequently, our pdf letterheads now take up to 3 to 4 minutes to print out - an excruciating long time!

    It seems that there a difference between the PDF rendering engine of keynote (which I suspect is the same one of preview) and the one of Adobe. The same PDF could be compressed to a very small file and open in a snap in Acrobat. But for preview it took few second to render. After cutting bits in an out I found the problematic object and remade it. This sloved the problem.
    As a side effect I found out that by using Show package content, you can find the pasted PDF and edit it directly with Illustrator, without having to cut and paste or save and insert.

  • How to speed up a very slow query creating HTML commands

    Hi, I’m generating HTML code that I will later send via dbmail (@body_format ='HTML'). There are about 11K records in the table and it takes over 9 hours to run. Any suggestions on how to increase throughput? or am I just stuck with it
    declare @html_3 varchar (max) = ' '
    select @@html_3 = @html_3 + '<tr> <td>' + cast (RegionID as varchar) + '</td><td>'
                    + RegionName + '</td><td>'
                     + cast (FileID as varchar) + '</td><td>'
                     + cast (FileNum as varchar) + '</td><td>'
                  + FileStatus + '</td><td>'
         + DeliveryStatus + '</td><td>'
         +TaskName + '</td><td>'
          + cast (EventStartDate as varchar) + '</td><td>'
      + cast (DeliveryEventLogID as varchar) + '</td><td>'
     + DeliveryServer + '</td><td>'
     + IISServer + '</td><td>'
     + UserName + '</td><td>'
     + DeliverEvent + '</td><td>'
     + NotificationEvent + '</td><td>'
     + DeliveryComments + '</td><td>'
                   + PronoComments + '</td></tr>'
    from ##PronoDetailRpt
    print @html_3

    If you have only 11K records, and if what you posted is the entire query, it should take nowhere near 9 hours to complete, even on a wimpy server. It might be that some other process is blocking your global temporary table.  
    Look at the process that is populating the
    ##PronoDetailRpttable. Is that running simultaneously as you are trying to run this query?
    Try selecting a single record from the table. Does that complete in a short time? i.e., run SELECT TOP (1) * FROM ##PronoDetailRpt;
    Run sp_who2 in a separate window while this query is running to see if there is anything blocking this
    query. There is a BlkBy column that will give you this information.
    EDIT: By the way, always specify a length for VARCHAR.  So instead of CAST (RegionID AS VARCHAR) use something like CAST (RegionID AS VARCHAR(32)) where the length is larger than the longest string you expect, or if you don't know how long it
    could be, use CAST (RegionID AS VARCHAR(MAX))

  • Acrobat 9 slow to open pdf files through proxy

    We are finding that it is very slow to open pdf files from various web sites
    though the BorderManager proxy with Acrobat Reader version 9. This is not
    the case with earlier versions of Acrobat Reader. We are using
    BorderManager 3.8 sp 5. Has anyone else experienced this issue? Is there a
    proxy.cfg setting I should be looking to change?
    Thanks,
    Brad Johnson
    __________ Information from ESET NOD32 Antivirus, version of virus signature database 3928 (20090311) __________
    The message was checked by ESET NOD32 Antivirus.
    http://www.eset.com

    In article <AbUtl.4166$[email protected]>, Brad Johnson
    wrote:
    > Has anyone else experienced this issue? Is there a
    > proxy.cfg setting I should be looking to change?
    >
    I think this was an issue with older versions of BM that was addressed
    with a proxy.cfg setting. Try the one from tip #63 at the URL below.
    Craig Johnson
    Novell Support Connection SysOp
    *** For a current patch list, tips, handy files and books on
    BorderManager, go to http://www.craigjconsulting.com ***

  • Like to Create PDF that includes portrait & Landscape pages

    I have a HP Scanner which allows me to create PDF documents. I have these very important documents about "My Learning Disability" the issue is that some pages are printed in Portrait and others are in Landscape. I really need to know if its possible to create a PDF with my specific needs? I have the latest addition of Adobe Acrobat Reader.
    HP SCANJET G4010
    Currently when I scan the pages are all portrait which makes some of them sideways on my Monitor
    Thank you Very Much

    Reader cannot create PDFs. You'd need to ask in the Acrobat Forum, as your scanner probably uses it to make the PDF.

  • PS CS3 Smart Sharpen very slow for LCE

    PS CS3 Smart Sharpen is very slow to create a preview and then be applied to the image, at least when using a low amount and high radius, eg 20, 50, for local contrast enhancement (LCE). I'm now running Vista 64, but I think it happened even under XP 32.
    Is this a common issue or is there some way of speeding things up with Smart Sharpen?
    Cheers, John

    A solution!
    It turns out the problem in my case was in fact Suitcase. Previously, I'd tried turning it off, but that didn't fix the problem, so this time, I uninstalled it completely and the problem disappeared. I then began re-adding it (installed 15.0.1, upgraded it, etc.) and the problem resurfaced with the addition of the Photoshop-specific plugin. Deleting that plugin solved the problem. So it seems that "disabling" Suitcase by stopping the TypeCore doesn't seem to actually disable all of the tentacles it sticks into your system.
    You can find the plugin here: Applications / Adobe Photoshop CS6 / Plug-ins / Automate / ExtensisFontManagementPSCS6.plugin
    (After a restart, I also had to delete the font cache, as described here http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html but your mileage may vary.)
    Alternately, if you don't want to delete the plugin, disabling it from within Photoshop seems to work as well. To do that, go to File > Automate > Extensis, click Preferences..., then deselect Enable Suitcase Fusion 4 Auto-Activation.
    Fortunately, the plugin doesn't seem necessary at all to use the the core functionality of Suitcase (enabling and disabling fonts) in Photoshop. I didn't even know what these app-specific plugins did until researching this problem, and I still don't quite understand the point of them. I guess they allow you to let the apps for which they're installed do a little bit more of their own management (enable a font via Suitcase that isn't enabled system-wide), but that seems like more control than I need--if I'm enabling a font, I want all my software to be able to use it.
    Anyway, the problem seems to be completely solved on my system now, though I just did all this, so more testing over the next few days is required. I'll post here if any issues crop up. I'm interested in hearing if this solves it for anyone else as well.

  • FAQ: Creating PDF Files from FrameMaker v.6 & earlier Documents -- Why you should not use "save as PDF"! -- Windows & MacOS Only!

    An issue that has come up over and over again on several FrameMaker and Acrobat/PDF email lists as well on the corresponding Adobe User-to-User forums is that of creation of PDF files. FrameMaker 5.5.6 and 6 have what looks like a convenient feature that is supposed to allow you to create PDF files via simply saving the document as a PDF file. I have gone on record as advising end-users not to use this approach for reliable creation of PDF files from FrameMaker documents under Windows and MacOS with FrameMaker 6 and earlier. Why do I most vociferously offer this advice and why doesn't the problem get fixed? And how SHOULD you create PDF files from FrameMaker?
    GOOD NEWS
    I will start with the good news. The "next major version" of FrameMaker will indeed have "save as PDF" re-implemented in a manner that it will be as reliable as printing to the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS. I am personally working with the FrameMaker development organization to make sure this really happens and is fully and properly tested and debugged! Furthermore, this next major revision of FrameMaker, unlike FrameMaker 6, will come with a Distiller installer that will properly install the "Acrobat Distiller" printer instance under Windows and the "Create Adobe PDF" desktop printer on the Macintosh (of course assuring that the latest PostScript driver is also automatically and correctly installed).
    DON'T USE "SAVE AS PDF"
    But what's wrong with "save as PDF" as currently implemented?
    The following are some of the SYMPTOMS reported over the last few years by FrameMaker users that were traced back to use of "save as PDF" under FrameMaker:
    (1) No PDF file is produced at all, possibly with a log file showing not-readily apparent PostScript errors during distillation.
    (2) The PDF file "loses" color in images. All or some images (raster, bitmap images, NOT vector artwork) appear in the PDF file in grayscale.
    (3) The resultant PDF file is on the wrong paper size, i.e., the document's logical page size does not match the output page size as seen in Acrobat or Acrobat Reader.
    (4) Some or all text in the resultant PDF file is blotchy looking or overly bold.
    (5) Some or all text in the resultant PDF file cannot be searched or indexed.
    (6) Some or all text in the resultant PDF file appears in Courier or in some other substitution font.
    (7) Interword or intercharacter spacing is a bit irregular in the resultant PDF file.
    (8) Content is missing in the margin areas of the page, i.e. you cannot do full-page bleeds.
    (9) Some or all page content is missing (other than margin areas).
    (10) Relatively inefficient PDF is generated.
    If this list by itself isn't enough for you, please note that some of these symptoms are very subtle and may escape attention when the PDF is first viewed or printed. Oftimes, it is when one attempts to manipulate the PDF file in Acrobat or repurpose its content or even view or print on a system other than the one on which the PDF file was created, that some of these symptoms make themselves obnoxiously visible (or invisible in some cases I won't make any bad jokes here about graphic examples!).
    It is important to understand that FrameMaker does NOT have its own native ability to create PDF. Any and all PDF created from FrameMaker documents is actually done by creating PostScript via the PostScript driver and having the Acrobat Distiller create PDF from that PostScript. The only exception to this is creation of PDF via the Acrobat PDFWriter driver, which is likewise not recommended (see below).
    In order for "save as PDF" to work correctly, FrameMaker must do the equivalent of calling Printer Setup and selecting the "Acrobat Distiller" printer instance under Windows or the "Create Adobe PDF" desktop printer under MacOS followed by setting the driver's options correctly for paper size, page range, etc., followed by sending the proper commands to the driver to create PostScript.
    Contrary to popular belief, PostScript as generated by the Windows and MacOS PostScript drivers is VERY device-dependent. The information in the PPD file associated with a printer driver instance provides critical parameters for generation of PostScript including:
    Whether the printer supports color (Acrobat Distiller does)
    What PostScript language level is supported (Acrobat Distiller 4.x and Acrobat Distiller 5.x are both PostScript language level 3)
    Whether native TrueType support is available (Acrobat supports native TrueType as Type 42 fonts)
    Available binary communications (Acrobat Distiller supports pure binary and ASCII, but NOT TCP, TBCP, or PJL)
    Resident fonts (Acrobat Distiller doesn't really have resident fonts)
    Available paper sizes and custom paper size availability (Acrobat Distiller supports a wide range of predefined sizes and continually variable "custom" sizes up to 200" by 200")
    Margins / printable areas (for PDF and the Acrobat Distiller, there are no margins in which imaging is not permitted)
    Device resolution (Acrobat Distiller can be set to any value from 72 to 4000 dpi; as a convenience, the Acrobat Distiller PPD provides a series of values for use by the driver. Since there is no inherent "resolution" of a PDF file, this parameter is used only for purposes of allowing PostScript programs that query for such a value to be satisfied and for the driver to be able to communicate this value to the operating system and/or application as required.)
    Paper handling (totally irrelevant to Acrobat Distiller if input or output tray selection via "setpagedevice" is found in the PostScript stream, it is ignored by Acrobat Distiller)
    Thus, if the wrong printer driver instance is selected (i.e., it isn't associated with the Acrobat Distiller PPD file) or that driver instance is improperly configured, improper PostScript will result and one or more of the symptoms described above can occur. As currently implemented, FrameMaker depending upon version will not necessarily choose the correct printer driver instance and/or correctly parameterize the print job via driver setup options. In fact, FrameMaker 5,5,6 might even try to generate PDF via calling a PCL driver, FAX driver, or even a non-PostScript inkjet printer!
    DON'T USE PDFWRITER
    The Acrobat PDFWriter is a relic of older versions of Acrobat. In fact, it is no longer installed by default in the "easy install" or the "typical install" of Acrobat 5. It hasn't really be updated since Acrobat 3 and only supports PDF 1.2. It is a GDI (Windows) / QuickDraw (MacOS) driver that directly generates PDF without any intermediary PostScript. Since it is not a PostScript printer driver, applications cannot pass through EPS graphics and/or PDFMark information (used for a wide variety of purposes by FrameMaker). For EPS graphics, most applications will send the low resolution TIFF (or PICT) EPS header in lieu of the PostScript text, if they send anything at all, to the driver. Forget about links, structure, or any other PDF "goodies." Expect that PDFWriter will fully "bite the dust" in the next major version of Acrobat.
    SO HOW DO I GENERATE PDF FILES FROM FRAMEMAKER 6 & EARLIER?
    The ONLY method that is really reliable for producing PDF files with FrameMaker 6 and earlier requires the generation of PostScript via a properly set printer driver instance associated with the Acrobat Distiller PPD and distillation of the resultant PostScript by Acrobat Distiller.
    Case 1: FrameMaker and the Full Acrobat 4.05 or Acrobat 5.0x Products
    PDF file from a "chapter" -- print directly to the Acrobat Distiller printer instance (Windows) or the Create Adobe PDF desktop printer (MacOS) already installed by Acrobat. If you check the "Acrobat data" option, then make sure to UNcheck the "print to file" option that gets set at the same time. As a result, the driver will automatically send the generated PostScript to the Distiller for you and delete the intermediate PostScript when done.
    PDF file from a "book" -- print directly to the Acrobat Distiller printer instance with the "print to file" option checked (Windows) or the Virtual Printer desktop printer (MacOS) associated with the Distiller PPD (see details below under Case 2/MacOS). You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    In both the above sub-cases, the default driver options generally will be OK, but check on paper size and communication protocol (Use pure binary, not ASCII, for optimal performance AND no CTRL-D characters under Windows. Make sure to set Level 3 only and Binary under MacOS. Font inclusion "All" for Acrobat 4.05 and "None" for Acrobat 5 under MacOS.). With Acrobat 4.05, make sure you preset the Distiller to use the joboptions you want. With Acrobat 5, you can set this on a job-by-job basis via the driver printer setup interface (or print dialog on MacOS).
    Case 2: FrameMaker 6 and the Bundled Acrobat 4.05 Distiller
    Windows -- Create a new printer driver instance using the latest version of the Adobe Universal PostScript Driver Installer, downloadable from Adobe's web site AND the Acrobat Distiller PPD file (located in the XTRAS subdirectory of the Distiller directory). This driver instance should be set to print to the local port named "FILE:". Name this driver instance as "Acrobat Distiller". The default driver options generally will be OK, but check on paper size and communication protocol (use pure binary, not ASCII, for optimal performance AND no CTRL-D characters). Make sure you preset the Distiller to use the joboptions you want. Print directly to this Acrobat Distiller printer instance. Make sure that the "print to file" option is checked. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    MacOS -- Install the latest version of AdobePS 8.7.x, downloadable from Adobe's web site. In FrameMaker, go to Page Setup and select the "Virtual Printer" and go to the "Virtual Printer" window pane. Select the Acrobat Distiller PPD file (located in the XTRAS subfolder of the Distiller folder). Print directly to the "Virtual Printer" (Make sure to set Level 3 only, Binary, and font inclusion "All".). Make sure you preset the Distiller to use the joboptions you want. You will need to manually process the resultant PostScript file through the Distiller (or use a "watched folder" arrangement).
    Case 3: Acrobat 3
    Acrobat 3 is not officially supported for the latest OS versions and I personally would no longer recommend its use for generation of PDF files given that Acrobat 5.0.5 is the current version of Acrobat.
    - Dov

    You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

  • Framemaker 8 and Distiller 8.1.4  creating PDF

    Hi
    I use FrameMaker 8. I save it as Frame 7.0 document type. When I create PDF, I get error and cannot successfully convert to pdf.
    My friend told me to uninstall Acrobat Professional, Framemaker 8 and then reinstall frammaker8 so that the PDF add-ons get installed.
    When I try to uninstall Acrobat Pro, uninstallation asks for AcroPro.msi file. When i insert the Acrobat Pro CD, it has the file, but I get the error "package file is not windows package...etc..". This is the same CD from which I had installed Acrobat Pro in the past.
    If I do not uninstall Acrobat Pro, when I install Frame8 and then continue to install PDF addon I get the message, you have a more updated version...installation will exit.....
    Now I am left with no way to convert to PDF.
    Any help, suggestion would be very useful.
    Thanks
    Bhagyashree

    I would start by not listening to your friend...
    Then, I suggest that you:
    * Verify that you have all FrameMaker patches installed.
    * If Acrobat is still on your system, see if you have a Repair Installation option on the Help menu and if so, activate it. Otherwise, I would try to reinstall and select Repair.
    Once you have a working installation again, try setting your system default printer to the Adobe PDF printer, and from Frame, select File > Print and print to the Adobe PDF printer. On the Frame Print dialog box, _do not_ activate the Print to File checkbox.
    If you still get an error, please let us know what the error message is. Also helpful are your operating system, amount of RAM installed, and other system information.

  • Very slow page curls in a PDF

    I am creating an interactive pdf. I created the swf file, imported it into indesign (CS6) and exporting as an interactive pdf. My pdf is simple, it only contains page curls but they are very slow! No where near as fast as the swf file when viewed in a web browser. Why? And what is the solution?

    You're using a hack by running SWF inside PDF. There is no solution unless you just use the SWF file by itself.
    And what's the value of the page curl anyway. It's a way overused effect.

  • PDF-Rendering is very slow

    Hi,
    on our local test-environment with CF 8.01 we have no problem to create a pdf with cfdocument-tag.
    <cfdocument format="pdf"
                    encryption = "128-bit"
                    permissions="AllowCopy,AllowPrinting"
                    unit="cm"
                    scale="100"
                    backgroundVisible="yes"
                    marginleft="1"
                    marginright="1"
                    filename="#url.pk_id#.pdf"
                    pageType="A4">
              <cfdocumentitem type="header">
              ... content of the pdf
    </cfdocument>
    but our productive-server (the same CF-version as the local testserver) is working very slow, and when I say slow I mean minutes not a view seconds more.
    I have no idea where this discrepance is comming from, especially as we could observe the pdf-rendering on fusion-reactor witch makes it rather improbable that - as we first thought - our firewall is slowing down the process.
    does anyone out there has an idea where the problem could be located or had someone in this forum experienced a simular pdf-pitfall?
    thanks for yout efforts.

    Hi Guys I work with a lot of pdf files with being a student at uni and not sure these tips might help. 
    Try an app called skim which is free it handles pdfs nicely and looks similar to the preview app. 
    Also if a pdf is slow to scroll try selecting all the pages goto file print.  Then on the bottom left hand side of the print window select pdf and then save as pdf.  I have found on some pdfs (usually the ones in black and white and look like a photo copy) using the the print save as pdf option has then allowed me to view a pdf fine in the preview app without any issues.  Hope this is useful.
    I suspect its to do with pixels per inch or dots per inch of the document.

  • TPS file is not deleted after FrameMaker creates PDFs via Acrobat 8

    Using FrameMaker 7.2 build 158, and Adobe Acrobat 8, when creating PDF files, the temporary PostScript file (*.tps), which is created before the final PDF, is not deleted after the creation of the PDF is complete.
    This is a big deal for us because we are using a tool which hooks into the PDF-creation of FrameMaker/Distiller, and is reliant on this TPS file being deleted.
    Is this a known bug? Does Adobe know about this? Do any other users have workarounds for this?

    Thomas,
    FWIW, speaking from experience with the Save As route, I've seen
    random "phunnies" in the final PDFs (such as the missing fonts
    issues), a bigger .tps file than the .ps file generated from directly
    printing to file, slower throughput in both the intermediate
    postscript file creation and actual distilling (probably tied in to
    the larger .tps file) and other differences from what the joboptions
    should have been.
    There should not have been any differences in the file sizes being
    created if the same printer instance/configuration was actually being
    used. I also see this on some automated runs with Miramo. It's not
    consistent either - sometimes it works fine and then the next run, the
    process is considerably slower and there are dropouts in the PDFs.
    So far, manually printing to a ps file and distilling always seems to
    work without any issues.
    Your mileage may vary.
    Arnis

Maybe you are looking for