Frequently Asked Questions

Will Filtrix work across networks?

Yes, on NFS mounted filesystems. Using Filtrix on automounted filesystems may cause unexpected difficulties and errors.

How does Filtrix for Windows run on a network?

Filtrix can be installed on a local machine and/or on a network server. A local machine install will be a single user license version of Filtrix. The default install location is c:\Program Files\Blueberry Software\Filtrix; however, it may be installed on any valid drive/path combination. For Filtrix to function on a network it will need to be installed on a drive that is shared to other (client) computers. The drive must be mounted by these client computers and given a drive letter. For example, you need to be able to see the drive from within MS Explorer.

To install Filtrix for a network, run the installation program from any computer that mounts to network drive (preferably from the computer that has the drive as an internal drive). You will need write permissions in the directory where Filtrix is installed. Once Filtrix is installed, create a shortcut to filtrix.exe on each computer that you want access to Filtrix. Right click on the Desktop->New->Shortcut. Click Browse and navigate through the Explorer window to the install directory. If you don't see the network drive, then you will need to set up networking on the client and mount the drive, giving it a drive letter. Click on filtrix.exe--its name should appear in the filename box--and click Open. The full path and filename should now appear in the command line box of the Create Shortcut window. Click Next, renaming the icon if you wish, and click Finish. A new icon will now be on the desktop. Double clicking it will run Filtrix from the network as long as you are connected to the network.

Filtrix typically comes as a single user license, which is the format we place at our FTP site. It allows a single conversion to occur at a time. If more conversions than licenses are attempted from the GUI, Filtrix will wait for the license to be freed, then begin converting. The typical advantages of installing on a server also apply to Filtrix. Only disk space for one copy is needed, which also means only backup of one copy. Only one copy needs to be upgraded when you upgrade. The disadvantages are also the same: Execution, specifically loading, of the app is slower because of network speeds, and the network needs to be running for Filtrix to run.

Does the Filtrix license ever expire?

How are non-compatible features supported during conversions?

Filtrix does the best it can, but it cannot create new features in target formats.

Here are some examples of how Filtrix deals with non-compatible issues:

• Microdocs in Interleaf are not supported in Word for Windows, but Filtrix will break up the lines and align them as well as possible in WMF graphic frames.
  
• Master pages in FrameMaker are not supported in Word for Windows, but headers and footers are approximated by the location of the data in the Frame master page.

Why did Filtrix delete data from my FrameMaker master page?

If the conversion loses data that were defined on a FrameMaker master page:

A. Any master page data found in the upper 3" of the page is treated as header data and any data found in the bottom 3" of the page is treated as footer data.
B. Under most conditions, any data found between these two header/footer markers will not be converted. EXCEPTION: When a body page identifies a master page and the body page is determined to be empty, Filtrix will translate the entire master page.

Why did Filtrix delete graphic objects from my FrameMaker document?

All body page graphic data that are anchored to a frame will be converted according to our supported graphic features. After analyzing the structure of each body page, Filtrix may not be able to convert individual, unanchored graphic objects unless the entire body page comprises graphic data alone. Otherwise, Filtrix discards the isolated graphic objects in favor of the document text found on the page.

| Top Of Page |