36.2 Setting up FrameMaker for unattended operation
Before you can use runfm, you must set up FrameMaker for automatic operation. You must have Windows administrator privileges to do so, because Windows records in the registry the setting required to find the executable to run.
As Administrator, execute the following command, either in a command window or via Start > Run...:
"path\to\FrameMaker" -progid:FrameMaker.M2G -auto
After you set up FrameMaker this way, you can use runfm to run, from a command line, any FrameMaker plug-in that is set up to receive RPC notifications.
Despite its name, the -progid option has nothing to do with which FrameMaker plug-in you want to run. You can provide any string as the value for -progid, as long as you start FrameMaker with that string first, then specify the same value when you execute runfm. If you specify -progid:FrameMaker.M2G when you set up FrameMaker, you can omit this option entirely when you use runfm to run Mif2Go.
These settings become effective after you exit FrameMaker. Once set, they remain set in the Windows Registry (in HKEY_LOCAL_MACHINE/Software/Classes), until/unless you set up FrameMaker again, perhaps with a different value for -progid.
Note: On a 64-bit version of Windows, entries for 32-bit applications such as FrameMaker are buried in a subkey of a subkey: the Wow6432Node key located below the primary Software key. Expand this key to see the 32-bit keys and values.
§36.4 Using runfm for Mif2Go conversions
§36.8 Using runfm for other FrameMaker plug-ins
> 36 Converting via runfm > 36.2 Setting up FrameMaker for unattended operation