FrameMaker 8 on XP and Softech's ProductCenter

Is anyone using FrameMaker 8 on Windows XP and SofTech's Product Center? We are importing FrameMaker documents into FrameMaker files by reference and then attempting to enter these files into our vault storage. When storing the hierarchy, the process crashes Frame.
Wondering if anyone else is doing this.

Have you triple-checked to be sure that all of the files have been saved in FM before the check-in process is started?
Also, how about things like paths -- are all the component files (e.g. graphics, FM files, whatever is part of the FM document set) in the same directory, all on the same system? Or are some files accessed from non-local directories, network file shares, or something like that?
Does the process work with any FM files at all -- or is it completely broken? e.g. if you make a brand new document without any significant content, no graphics, just a simple doc, does the original check-in work by itself?
Can you identify any correlation between when these crashes started, to pin it down to a date range, and then maybe your IT could see if that syncs with any of the MS security patches.
I guess what I'm trying to suggest is try to break down the steps to the most simple operations, to see if you can identify whether there's some trigger point between when it works vs. not.
There are so many other possibilities with a server app, it's difficult to make troubleshooting suggestions.
I understand trying to do some pre-emptive troubleshooting, but my gut tells me that this might be a significant enough issue that the vendor might have trouble reports from other users.

Similar Messages

In FrameMaker 9.0.3 and 9.0.4, I cannot set tab stops for a style in the Paragraph Designer.

In FrameMaker 9.0.3 and 9.0.4, I cannot set tab stops for a style in the paragraph designer. Here are the steps to dysfunction:
1. In Paragraph Designer, for Tab Stops, click Edit. Edit Tab Stop dialog box opens, and the Paragraph Designer dialog box closes.
2. Type value in New Position box.
3. Click Continue. The Edit Tab Stop box closes.
4. Open Paragraph Designer. No tabs are recorded.
Discussion of a similar problem occured on this forum in June 2010. At that time, the resolution seemed to be to upgrade to 9.0.3. Has anyone else encountered this problem with these versions?
Thanks.

Hi, Arnis,
Brilliant! Thanks so much. I only looked at the later discussions of that thread, which seemed to indicate the problem would be solved by an upgrade to 9.0.3.
-Trish

Unable to print to oversize pages using Adobe FrameMaker 9 \ 7.2 and Distiller 9.0

I am trying to print to PDF a publication that is full of oversize wiring diagrams from Adobe FrameMaker 9 and 7.2 with Distiller 9.0. The pages are all text and images ranging in size from standard A3 and A4 size sheets through to a foldout being 1470 mm W X 297 mm H. We have no problem printing A3, A4 and 630 mm W X 297 H. These are all Portrait images. When we set up our custom print size to accomodate the 1470 mm W X 297 mm H we get the pages without the content, and even some of the oversize pages are not the correct size on print.
The page sizes we are using are:
A4 (This is all good)
A3 (This is all good)
630 x 297 mm (This is all good)
840 x 297 mm (Problems from here on)
1050 x 297 mm
1260 x 297 mm
1470 x 297 mm
The procedures we are using to set up the printing are:
1. Print to PDF (Also tried save to PDF)
Under Print Setup make sure you select PDF Driver and select the Paper size as largest that is in your book. Example: If A4 and A3 pages, print to A3
2. Select Generate Acrobat Data and select
See attached Screen shots for the settings we are using:
Note: Back in FM Print dialogue; make sure Print to File is turned OFF, before you click Print
Any assistance would be greatly appreciated.
Regards
AJ Wilkinson

Create a specific FM file having a custom page size appropriate to each unique "content set".
Create a FM Book file.
Add the FM files.
Work up configuration (Hypertext, Cross-References, autonumbering, variables, etc.) as desired.
In Print Setup -
Set page size to the page size of the largest FM file in the Book.
(you may have to go into the Adobe Printer and add one or more custom page sizes so the page size needed is available)
Set orientation to landscape if any FM files are such.
Idea is, if needed, FM files for the content in the various page size/orientation that is appropriate to the content.
If that means 1FM file of custom size and appropriate orientation then do it.
Book files can deal with it.
Back to Page Setup.
Do the Page Size & Orientation.
Access 'Propertires' - is the Distiller job option selected the one you want/need?
Create one if need be so that it is available.
Go into the Print Book dialog.
Configure as needed (remember Acrobat data links, etc. &, oh yes, back in FM be happy with the configurations under tabs for PDF Setup).
Print the Book.
Use Distiller to take to output *.ps to *.pdf (may want the use a "watched folder")
Output PDF can/will reflect the the different page sizes and page orientations.
n.b., FM-Acobat-Distiller releases have a "sync band".
It is discussed somewhere in some kb articles.
I'm not sure if FM7.2 functions quite right with Distiller 9.
FM 8 will (&, of course FM 9)
I've had no problems with FM7.2 or FM8 and Distiller 8.
Be well...

FrameMaker 10: Manage used and unused styles

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/framemaker/pdf/FRAM EMAKER11_UPGRADE_GUIDE.PDF says FM 10 introduced the ability to "Manage used and unused styles: paragraph, character, table" but I am unable to find that information in the (exceedingly unhelpful) help system. Can anyone point me to a discussion of this featue? We are moving to new templates and would like to make the transition as painless as possible.

Hi, Beverly:
Extendscript was introduced in FrameMaker 10. Perhaps someone's already created a script for this. I'm not sure if Extendscripts can be assigned to a keyboard shortcut. Perhaps soneone on the forum can point to an existing script, and also confirm whether a script can be assigned to a KBSC.
[EDIT]
I forgot to mention: Search Google for terms like "framemaker 10 extendscript" without quotes for info about Extendscript. Even if you don't want to add scripting to your resume, you might get some useful ideas from this link:
http://www.rickquatro.com/resources/BeginningFrameMakerScripting.pdf
[/EDIT]
And, in some future lifetime, your feature request will be incorporated in FM, if you post a formal request here:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices
Beverly Robinson wrote:
I'm a keyboard person--I apply styles using the F8 and F9 key--so I don't have the paragraph catalog display at all. I would have put the "Delete all unused formats" option with the delete functionality available through the Commands button on the Paragraph Designer. But that's just me.
Message was edited by: peter at knowhowpro

FrameMaker FDK Developement - hints and tips needed

Hi.
I have looked around after information about how to develope with FrameMaker FDK, but I can't find any good examples for a FDK newbee.
Anyone that knows about some useful links where I can find information about how to get started?
I have tried google, but I couldn't find anything good.
Thanks,
Per

If you need to create quick fixes to speed up production, then definitely investigate Framescript first. It's a complete IDE environment that lets you try things out iteratively. It has virtually all of the capabilities of the FDK and lets you access system resources as well. The documentation is extensive and there is a third-party tutorial book available from Rick Quatro at http://www.frameexpert.com
There is an active group on Yahoo for this as well at http://groups.yahoo.com/group/framescript-users/
Depending upon where you reside there also are some training classes available for this via Front-Runner Training in Toronto,
see: http://www.front-runner.com/TrainingCategoryDetail.php?cid=76&catid=4&compid=1&pageNum_Cat egoryCourses=00

Acrobat 7, needed with FrameMaker 7: How do I get and install an "Adobe PDF printer instance?"

In FrameMaker, when I try to save a FrameMaker file as a PDF file, I get the following message: "FrameMaker could not find Adobe PDF printer instance, which must be installed to execute "Save as PDF" command". I have a sinking feeling that I deleted that printer instance from my list of printers, thinking I did not need such a printer. I have tried uninstalling and reinstalling FrameMaker 7, Acrobat 7 and Reader 9. All reinstalled successfully, EXCEPT still no Adobe PDF printer instance. Thus my question: how do I get and install that Adobe PDF printer instance?
.( I am using a new computer. I still have my old computer available, with the Adobe PDF printer instance on it. If I could find where in the old machine (Windows XP) the files are for it, I could copy them to the new machine).
Thanks in advance for any advice.

Just curious,
What is the new machine's OS (& is it 32-bit or 64-bit)?
Be well...

FrameMaker hangs and can't print to Adobe PDF

FrameMaker has been hanging and blowing up on me. Specifically, it hangs when I try to save all the chapters in a book. Some of these books are very small, maybe 20 or 30 pages. After I stop Frame thru Task Manager and reboot, I can reopen the book and my changes appear to be there. I looked through the forum and saw something that said it might be because the PC doesn't have enough memory. It has 3.5 GB RAM. Isn't that enough?
Also, when I print (to my default printer = Adobe PDF), if I unselect "print to file," nothing happens - no Distiller window opens - I don't see any new files generated. I can "save as PDF" just fine. I can "print to Adobe PDF" from other apps, just not from Frame. I can "print to file" and then open the resulting .ps; then Distiller opens and creates the PDF file. This is annoying - it used to automatically launch Distiller and create the PDF in one step instead of two.
I'm putting both this issues in a single topic because they both started at about the same time.
I tried re-installing Frame and Acrobat, but I didn't uninstall first.
I'm using Windows XP Pro and Frame 8.0p277.
So where do I go from here?
Thanks

Yes, the location for the Adope PDF printer had garbage in it. I fixed that. That has now fixed the problem.
However, Art's reply gave me an idea. I am using FrameMaker 8.0p277 (the version that came with Tech Comm Suite). Also, Acrobat 8 3D came with it.
Since then, however, I have installed Acrobat 9 Pro (which also provided Distiller 9).
Could it be that FrameMaker is trying to call Distiller 8, which no longer exists on my computer)?
Answering prev questions:
"So if you uncheck Print To File so the distiller generates the PS file and distills it automatically, nothing happens, right? It just sits there?
and
Have you tried selecting a different Job Option, like Standard, or High Quality?"
Yes, if I uncheck Print to File, nothing happens and no .ps or .pdf is created.
On the properties of my Adobe PDF printer
There are actually four entries. It does not seem to matter which one I choose.
I'm working now on seeing if I can get Acrobat re-installed.

FrameMaker 8.0p277 and printing to Acrobat Pro 8 & 9

All this year (2009) I've been working on several contract documents using FrameMaker's conditional text facility.
FrameMaker is 8.0p277 and the OS is Windows XP Pro SP3.
In May the old workstation became cantankerous so I updated to a new HP xw4600 with a Quad Core, 4GB ram, and 2 x 250GB SATA disks. Cool!
I applied all the MS updates and then treated myself to a clean install of Adobe Design Premium CS4, then installed and updated FrameMaker 8.0 (without the PDF Maker). The Adobe Acrobat Professional 9.0 in CS4 was patched to 9.1.2.
If I open a document in InDesign CS4 and print it to the 'Adobe PDF' printer everything works just fine. Same for Illustrator CS4.
But FrameMaker fails with this message:
... followed by:
I have also attached the most recent FrameLog fiole...
Howsomever, if I print the same document to my HP laserjet 4300dtn (or the laserjet 5200 or the FujiXerox DocuPrint 2100) it works just fine. So I assume the document itself is OK.
If I select the printer to be one of the 3 above and then print to file (and create a .PS file), and then open it in Distiller 9.1.2 it produces a perfect .PDF file (shades of Acrobat 3 and the watched folders here!). But, if I select AdobePDF printer as my output device before generating the .PS file, Distiller reports parsing errors and does not produce output.
With a doffed hat to Arnis and Dov I refrained from trying 'save to PDF'
This looks like a corrupt printer driver...
After talking to Adobe Support (ID 121 702 309) I have tried each of the following (and then re-run my testing cycle as outlined above):
Running the 'Repair Acrobat Installation' process from Acrobat Pro 9.1.2.
Setting Acrobat PDF as my default printer (strong whiff of "eyes of a bat and wings of a newt" about THAT suggestion).
Un-installed and then reinstalled Acrobat Pro 9.1.2.
Un-installed and reinstalled FrameMaker 8.0p277.
Un-installed and then reinstalled Acrobat Pro 8.1.4.
Un-installed and reinstalled FrameMaker 8.0p277.
Sworn loudly.
Anyone have some ideas / fixes / incantations???

Hi Laurence,
If you can produce PDFs from the AdoebPDF via ID and AI by printing, then I'd suspect that the driver is probably ok. (Note: from ID and AI, it is better to SaveAs PDF, since these have their own internal PDF generation capabilities.)
Also, with FM8, if you're making interactive PDFs (i.e. not for press), then it is ok to do the SaveAsPDF route, since FM has some post-processing modules that kick in to clean-up the .tps file prior to handing it over to Distiller. So, the process is no longer is identical to printing to file and distilling.
On the FM side, make sure that the tagged PDF setting is turned off in your PDF setup and have the setting for generating named destinations for all paragraphs enabled.
You also might want to download Sundorne's SetPrint ( http://www.sundorne.com/FrameMaker/Freeware/setPrint.htm ) utility to ensure that you always have the same printer instance (AdobePDF) enabled when you start FM.
Have you also applied the MS hotfix for the PDF font issues? Details are available here: http://blogs.adobe.com/techcomm/2008/07/hotfix_for_framemaker_1.html
Last desperation move would be to create a new custom PDF printer instance using the Distller PPD and a copy of the AdobePS installer.

Framemaker and floating license ?

Hi,
In my company , we want to move to another strategy than we have now.
At the moment , we have 10-15 users who use from time to time framemakers, never at the same moment.
We dedicated 4 computers in one room for these users, so we use 4 licenses.
We would like now that all the users use framemaker from their computer, and a perfect solution would be a floating license.
Navigating on the site, I could not find a way to buy a floating license.
Are we forced to buy 15 licences ?
Thanks for answer!

AFAIK, the floating licenses have only been available for the unix platforms.
You might want to contact Adobe's evangelist for tech comm products, RJ Jacquez on this. He should definitely know. The easiset & fastest way to reach him is via Twitter. See: http://twitter.com/rjacquez

Problems with Bridge and FrameMaker

We are using FrameMaker 9.0.3 and Creative Suite CS4 on Windows XP, with 3 GB of RAM and 150 GB hard drive space. One of us typically runs FrameMaker and Bridge CS4 simultaneously, usually with Illustrator and maybe also Photoshop open at the same time. A few weeks ago, he began having problems. Typically he (1) opens FrameMaker, (2) opens a .fm file located on a network drive, (3) opens Adobe Bridge, then (4) selects a folder located on the network drive in Bridge. At some point, he gets an error (apparently a Windows error) that there are insufficient resources. Sometimes he is able to save his work and sometimes not, but he always has to reboot to be able to work again. He typically reboots 4 or 5 times a day.
Any suggestions as to why this might happen?
Thanks in advance,
Van

Read thruogh this rather lengthy post about "low on resources". Perhaps something in here will help faster than starting from scratch on a new post.
http://forums.adobe.com/thread/310498?tstart=30

Internal Error 10014, 7686666, 10069197, FrameMaker has detected a serious problem and must quit.

When opening FrameMaker 10, program stops and relays Intrnal Error 10014, etc. I tried uninstalling FrameMaker and reloading, same error. FrameMaker had been working to this point.Any Ideas.\?

At what point in the start-up screen (the module names flash below the "Adobe FrameMaker 10" as shown below) does the crash happen?
If this happens during "Localization", it usually means that one of your dictionary libraries (Linguistics) is hosed. If you rename the "Linguistics" folder at c:\users\username\AppData\Roaming\Adobe for Win7 or c:\Document Settings\username\Application Data\Adobe for XP to something else (e.g. Linguistics_bad), then FM will re-create a new one when it starts up next time. You can then delete the bad folder after FM has succesfully started.
If the problem is in another module, then please specify which module, which FM point release, what operating system your running, etc. so guesses about your environment are minimal.

FrameMaker 7 vs Windows 7 and Windows Vista

We have several computers with either Windows 7 or Windows Vista. On these we have Frame version 7 (latest patch). I have heard that Frame 7 is not compatible with these 2 operating systems. Is that true?
We all have the same problem:
If we, with our mice, try to mark text in a flow or cells in a table, and have the left button pressed too long (more than a couple of seconds), FM freezes. The only way to get out of this is to crash it and loose everything since the last save.
Will this problem go away if we upgrade to version 9? Has anybody else experienced the same, upgraded and now FM behaves properly?
Lena, Sweden

Lena,
we are currently running FrameMaker 7.2 on Windows 7, and we too are experiencing 'Not Responing' hanging issues that we have to then end FrameMaker and lose the unsaved information.
I initially thought it was network related but eliminated this when i looked at files on a local hard disk.
I can now produce the error by selecting a large section of a framemaker document and trying to copy it (we have a lot of referenced illustrations which are EPS files stored on the network and these seem to assist in causing the program to hang.)
I found reference on a site about the Desktop Windows Manager, and decided to do a test. I have forced my computer in to a Hang situation and then looked at ending the dwm.exe process in task manager. As soon as i do this, the screen flashes, and i now have a responding framemaker program. I have done it a few times and it seems to correct it each time.
DWM is linked into the Aero interface. see http://en.wikipedia.org/wiki/Desktop_Window_Manager, so it looks like the way to get framemaker 7 working is to turn off/disable the DWM service,
Under Control Panel -> System and Security -> Administrative Tools -> Services -> Desktop Window Manager Session Manager -> Disabled
I would recommend testing this by causing Framemaker to stop responding and then use Task Manager to end DWM.exe. If this works the long term solution would be to disable the DWM Service. I am going to do this and see how i get on.
Hope this information is of some use.

How Can I install Framemaker 10 silently with serial key and license updater?

How Can I install Framemaker 10 silently with serial key and license updater? Is there any tool to create MSI for this?
I tried with using http://download.macromedia.com/pub/developer/creativesuite/AAMEE/win32/ApplicationManagerE nterprise_1_all.exe and its not supporting.
I am looking for any customization tool for Framemaker 10 from Adobe or else silent install with serial and license updater

After creating "application.xml.override" from above link
First after installing manually Adobe Framemaker 10,Copy "pcd.db" to your source folder from "%ProgramFiles(x86)%\Common Files\Adobe\Adobe PCD\" once you run "LicenseUpdater.exe"
1) For install create batch file "install.bat" and copy below command
@echo off
REM =====Install script=====
set Current=%~dp0
"%Current%Set-up.exe" --mode=silent --deploymentFile="%Current%\deploy\AdobeFrameMaker10_en_US.install.xml" --overrideFile="%Current%\deploy\application.xml.override" --acton=install
COPY /Y "%Current%pcd.db" "%ProgramFiles(x86)%\Common Files\Adobe\Adobe PCD\pcd.db"
Exit 0
2) For Uninstall
* download Adobeairinstaller from Adobe - Adobe AIR to uninstall adobe AIR silently and copy this exe in source folder
Create batch file to uninstall Framemaker 10 "Uninstall.bat" and copy below command to Uninstall
@echo off
REM =====Uninstall script=====
set Current=%~dp0
REM Uninstalling "Adobe Framemaker 10"
"%Current%Set-up.exe" --mode=silent --deploymentFile="%Current%\deploy\AdobeFrameMaker10_en_US.remove.xml" --overrideFile="%Current%\deploy\application.xml.override" --acton=uninstall
DEL /F /Q "%ProgramFiles(x86)%\Common Files\Adobe\Adobe PCD\pcd.db"
REM Uninstalling Adobe community help
msiexec /x {E2B04924-29F3-F49D-71E9-B90EFEDE282C} /qn
REM Uninstalling Adobe PDF creation Add-On 9
msiexec /x {AC76D478-1033-0000-3478-000000000004} /qn
REM Uninstalling Adobe AIR
"%Current%AdobeAIRInstaller.exe" -uninstall
Exit 0
I think this will help....

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...

Problem with FrameMaker 9 on Windows 7

A member of my unit is running FrameMaker 9 on Windows 7 with a 64bit machine and has come across a strange problem.
Whenever he has a file open for too long his FramMaker will crash once he tries to work with the file again. This usually takes a few hours before this problem arises. In trying to figure out what was going on we took a look at Windows Task Manager. We noticed that once we opened a FrameMaker file the GDI Objects for FrameMaker continued to grow steadily even when we weren’t touching the file or doing any work in FrameMaker. The value under FrameMaker GDI Objects continued to grow until it reached some point around 10 000 then FrameMaker would either crash (if the GDI Objects passed 10 000) or it would crash once one tried to open another FrameMaker file (because that would make the GDI Objects increase to over 10 000).
Has anyone else encountered this problem? Does anyone know of a way to fix this problem?

I actually have a similar problem with my machine. I am running FrameMaker 9 with Windows XP on a 32bit machine.
The problem is slightly different because on my machine the GDI Objects doesn't continue to increase over time it increases with the number of files I open and close. Every time I open a file the number of FrameMaker GDI Objects increase and when I close the file the number of GDI Objects decreases a little but not down to the original value, so when I open and close a lots of FrameMaker files the number continues to increase until it reaches 10 000 then my FrameMaker crashes.

FrameMaker 8 on XP and Softech's ProductCenter

Similar Messages

Maybe you are looking for