Hi Dan, None of the plugins that were originally made for 32-bit FrameMaker will work with 64-bit FrameMaker 2019. They have to be recompiled by the developer.
If you don't need all of the features of IXgen, you may want to consider an ExtendScript solution. ExtendScript is built into FrameMaker 10 and higher and the scripts should survive from version-to-version, including 64-bit FrameMaker 2019. I have rewritten most of my plugins as scripts and all of them work with FrameMaker 2019 and all versions down to 10. Rick Rick Quatro Carmen Publishing Inc. [email protected] 585-729-6746 www.frameexpert.com/store/ -----Original Message----- From: Framers <[email protected]> On Behalf Of Harding, Dan Sent: Thursday, April 11, 2019 8:58 AM To: An email list for people using Adobe FrameMaker software. <[email protected]> Subject: [Framers] FM2019 and ixgen? Good morning all, I have an email in to Frank Stearns (creator of ixgen) about this, but in the interim I want to get some other data points: Has anyone been able to get ixgen to work with FrameMaker 2019? When I run the ixgen installer, it does not see the installation of 64-bit FrameMaker, presumably because ixgen is a 32-bit application, so installing it under 64-bit FM is likely out. When I run the installer and select 32-bit FrameMaker 2019, it installs successfully, however when I launch 32-bit Frame 2019, I get the following error in the FM console: ---------------------------------------------------------------------------- ---------------------------------------------------------- Cannot initialize API client C:\Program Files (x86)\Adobe\Adobe FrameMaker 2019 (32 Bit)\ixgen\bin\ixgen.dll. Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client. ---------------------------------------------------------------------------- ---------------------------------------------------------- I checked the maker.ini file and didn't see anything untoward. It may be that FM has changed enough "under the hood" that ixgen is no longer compatible... which puts a real crimp in my production workflow. I'd prefer not to go back to FM2017 at this point. Thanks, -Dan _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected] _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected]
