ADOBE FRAMEMAKER 8 INSTALLATION GUIDE FOR UNIX
© 2007 Adobe Systems Incorporated and its licensors. All rights reserved. Installing Adobe® FrameMaker® 8 for UNIX If this guide is distributed with software that includes an end-user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Certain Spelling portions of this product is based on Proximity Linguistic Technology. ©Copyright 1990 Merriam-Webster Inc. ©Copyright 1990 All rights reserved. Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. ©Copyright 2003 Franklin Electronic Publishers Inc.©Copyright 2003 All rights reserved.
Burlington, New Jersey USA. ©Copyright 1989 IDE a.s. ©Copyright 1989 All rights reserved. Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. ©Copyright 1990 Espasa-Calpe ©Copyright 1990 All rights reserved. Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA. ©Copyright 1989 C.A. Stromberg AB. ©Copyright 1989 All rights reserved. Proximity Technology A Division of Franklin Electronic Publishers, Inc.
v Contents Chapter 1: Getting started About multiple-platform networks System requirements ........................................................ 1 ...................................................................... 2 Chapter 2: Installing files Preparing to install FrameMaker ........................................................... 5 Setting up the FrameMaker directory Selecting the files to install ...................................................... 6 ...................................
vi CONTENTS Specifying an XKeysymDB file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Chapter 4: Setting up licenses Licensing basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting up shared licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii Using fonts Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii CONTENTS
1 Chapter 1: Getting started This guide describes how a UNIX® system administrator can install and license Adobe® FrameMaker®. A software developer installing the Frame® Developer’s Kit™ can use the commands provided in “Installing files” on page 5 Note: If you currently use an earlier version of FrameMaker, see the Appendix. About multiple-platform networks You can install UNIX versions of FrameMaker on a single network of workstations that use the same UNIX file server.
2 CHAPTER 1 Getting started System requirements To use FrameMaker for UNIX, you need the following hardware and software. Platform and software requirements The following table shows the supported system configuration. See also “Memory requirements” on page 3. Platform Workstation model Sun™ Sun™ SPARCstation® Operating system Window environment Window manager Solaris 2.8, 2.9, and 2.
ADOBE FRAMEMAKER 8 3 Installation Guide Memory requirements The following table shows requirements for RAM, disk space, and swap space. Disk space requirements are 25 MB larger for Japanese functionality.
4 CHAPTER 1 Getting started
5 Chapter 2: Installing files This chapter describes how to install Adobe® FrameMaker® 8 files from a CD-ROM onto a workstation or server. After installing the files, you will set up user environments and licenses. Note: If you have an earlier version of FrameMaker installed, you must install version 8 of the product in a different directory (see “Upgrading from an earlier version” on page 61).
6 CHAPTER 2 Installing files Setting up the FrameMaker directory If you are installing for more than one user, you must put the files in a directory for which all users have read and execute permissions. The directory must also be mounted on all users’ systems. To install the files, you must have write permission for the directory. Adobe recommends that you install FrameMaker files in a directory named frame in the directory where you normally store applications (for example, /usr/frame or /var/frame).
ADOBE FRAMEMAKER 8 7 Installation Guide To set up the FrameMaker installation directory: 1 Use the mkdir command to create the directory. For example, enter mkdir /usr/frame 2 Use the chmod command to ensure that users can run the products from this directory. For example, enter chmod 755 /usr/frame Note: The remaining installation instructions refer to the directory you just created as install_dir. Type the full name of the new directory when you see install_dir in a command.
8 CHAPTER 2 Installing files • Executable files for the platform from which you are installing • An English-language user interface, or a Japanese-language interface if the LANG environment variable is set to ja • Type 1 fonts • Multibyte fonts. For more information, see Working with Multiple Platforms, on the Adobe website: www.adobe.com/support/documentation/. • All filters (for information, see Using Filters, on the Adobe website: www.adobe.
ADOBE FRAMEMAKER 8 9 Installation Guide • Select individual international dictionary and Thesaurus file sets to install, instead of installing all files. (This saves disk space, but may affect the formatting of text in the languages for which you have not installed dictionaries.) Installing fonts If your previous version of FrameMaker installed Linotype fonts (Times, Helvetica, Helvetica Narrow, NewCenturySchlbk, and Palatino), the fonts can be copied into FrameMaker 8 installation.
10 CHAPTER 2 Installing files Choosing the user-interface language for international products A custom installation also lets you choose which user-interface languages to install. The installation script installs the user-interface, dictionary, thesaurus, and demonstration files in the languages you choose, and optionally installs online manuals in those languages (some online manuals are only available in English). For information about changing the default user-interface language after installation.
ADOBE FRAMEMAKER 8 11 Installation Guide • Mount the CD-ROM drive, if necessary • Run the CD-ROM installation script to install FrameMaker files • Troubleshoot the installation You can install from a CD-ROM drive on your local system or from a remote system. If the CD-ROM drive isn’t mounted, you must log in as the root user to mount it. If you need to log in as root to mount the drive, log out after mounting it and log in under a different name before installing the files.
12 CHAPTER 2 Installing files To determine if the CD-ROM drive has already been mounted: Enter the following command: /sbin/mount You should see a list of mounted file systems.
ADOBE FRAMEMAKER 8 13 Installation Guide To mount the drive on a local system: 1 Log in as the root user and insert the FrameMaker CD into the CD drive. Otherwise, the mount command may not work. 2 Create the CD-ROM directory by entering 3 Mount the drive by entering the following command: The CD drive may be automatically mounted for you when you insert the CD. If it is not, type /sbin/mount -F hsfs –r /dev/sr0 /cdrom The value of device_name depends on your system.
14 CHAPTER 2 Installing files Mounting the CD-ROM drive from a remote system If the CD-ROM drive is attached to a remote system, check whether it is listed in the exports file on the remote system, and add it if necessary. The exports file specifies directories that can be exported to local systems. Its pathname and filename depend on your platform. After checking, correcting, and loading the exports file, you can mount the CD-ROM drive.
ADOBE FRAMEMAKER 8 15 Installation Guide If you see this line, skip to the procedure, “To mount the CD-ROM drive from a remote system:” on page 15. If you do not see this line, you need to add it to the file as described in the following procedure. To edit the exports file: 1 If the file does not exist, use a text editor to create it. 2 Using a text editor, add the following line as the last line of the exports file: share -F nfs -o ro /cdrom After editing the exports file, you must load it.
16 CHAPTER 2 Installing files /sbin/mount -F hsfs -r /dev/sr0 /cdrom The value of device_name depends on your system. The -r option mounts the drive as read-only. Use this option to prevent media error messages from appearing. 2 Exit root on the remote system by entering exit 3 Log in as the root user on your local system.The system will request the root password.
ADOBE FRAMEMAKER 8 17 Installation Guide 2 Enter the following CD-ROM installation command: ./read.cd 3 Read the instructions provided by the CD-ROM installation script and answer the questions. The script asks you to specify the FrameMaker installation directory and which files to install. It then installs the appropriate files into install_dir.
18 CHAPTER 2 Installing files Copying FrameMaker files If you need to copy the FrameMaker directory and its subdirectories from one location to another, use the fmcopy shell script located in install_dir/bin. To see instructions for using this script, change to install_dir/bin and enter ./fmcopy in a UNIX window. Important: Do not use the UNIX cp -r command; only fmcopy will copy the correct file permissions and symbolic links.
19 Chapter 3: Setting up the user environment You should change the PATH environment variable for each user so they can start Adobe® FrameMaker® from any directory. The easiest way to do this is to run the provided fmusersetup script. You also can manually change each user’s path without using fmusersetup. If you choose not to change paths, users must supply full pathnames or change to the installation directory to start FrameMaker.
20 CHAPTER 3 Setting up the user environment Using the fmusersetup script The fmusersetup script alters the user’s startup files to define the environment variable FMHOME (which specifies the directory in which you installed FrameMaker products). It also adds the FrameMaker bin directory to the PATH environment variable, to make it easier to launch FrameMaker, and adds execute permission to the user’s home directory (for printing).
ADOBE FRAMEMAKER 8 21 Installation Guide 5 Test the script by starting FrameMaker from any directory. (For information, see “Starting FrameMaker” on page 57) Running fmusersetup as root If you choose to run fmusersetup as root, make sure the HOME environment variable is set to the root directory of the machine on which FrameMaker is installed.
22 CHAPTER 3 Setting up the user environment If the path assignment statement is defined absolutely, you must edit the file after fmusersetup changes it. (The path is defined absolutely if the path statement doesn’t have the environment variable PATH on the right side of the equal sign. It has pathnames instead.) To correct the file, you must move the lines that fmusersetup added so that they occur before the path assignment statement.
ADOBE FRAMEMAKER 8 23 Installation Guide To set up a user’s environment without running fmusersetup: 1 Define FMHOME by doing one of the following (where install_dir is the name of the directory in which you installed FrameMaker): • If you use the C shell, add this line to the .login file: install_dir • If you use the Bourne or Korn shell, add this line to the .
24 CHAPTER 3 Setting up the user environment Using aliases or scripts to avoid modifying paths If you don’t want to modify paths, you can use aliases or scripts to make it easier for users to start FrameMaker. To do this, create an alias or a shell script that refers to the full pathname for the command to start a product. For information on the commands, see , “Starting FrameMaker.” Important: Do not rename the actual product files.
ADOBE FRAMEMAKER 8 25 Installation Guide • If you use the Bourne shell, define the alias in the .profile file. For example: { install_dir/bin/maker } • If you use the Korn shell, define the alias in the .profile file. For example: alias framemaker='install_dir/bin/maker' Creating a script You could also place a script that starts FrameMaker in a directory that is in the user’s path. Then the user can start the product by entering the name of the script file.
26 CHAPTER 3 Setting up the user environment #!/bin/sh case $# in 0) exec install_dir/bin/maker;; *) exec install_dir/bin/maker "$@" ;; esac Using FMHOME The remaining instructions in this guide assume that you’ve defined FMHOME to represent the FrameMaker installation directory (install_dir). If you haven’t defined this variable, enter the installation directory’s full pathname whenever you see $FMHOME in a command.
ADOBE FRAMEMAKER 8 27 Installation Guide Subject: Warning: translation table syntax error: Unknown keysym name: osfPageLeft You can correct this problem by setting the XKEYSYMDB environment variable to refer to an updated version of the XKeysymDB file, which is provided in $FMHOME/fminit.
28 CHAPTER 3 Setting up the user environment
29 Chapter 4: Setting up licenses This chapter describes how to set up licenses, get reports on license usage, and troubleshoot licensing problems. Note: Please skip this chapter if you are installing a demonstration version of FrameMaker. Licensing basics When you start Adobe® FrameMaker®, the product searches for a license that allows you to run it. Without a license, you can run only a demonstration version.
30 CHAPTER 4 Setting up licenses Personal licenses A personal license allows a single user to use FrameMaker. When you set up licensing, you must assign a user name to each personal license. A licensed user can use FrameMaker from any system on your network, but can only start the product on one system at a time. Shared licenses Shared licenses allow multiple users to use FrameMaker. Each shared license allows a certain number of users simultaneously.
ADOBE FRAMEMAKER 8 31 Installation Guide Note: Make copies of your licensing information and store them in a safe place. If your licensing files become damaged, you must create them again from the original information. Licenses file You set up licenses by using FrameMaker to record license registration numbers in the licenses file. If you are setting up shared licenses, create the licenses file on a system that all users can use, for example, a file server.
32 CHAPTER 4 Setting up licenses Setting up shared licenses If you are installing shared licenses, you must designate a system as the license server host. The program that allows users to share licenses runs on this system. The license server host can be the system on which you installed FrameMaker or any other system on your network.
ADOBE FRAMEMAKER 8 33 Installation Guide Setting up license servers After the installation script installs FrameMaker, it recommends that you install licenses. To do this, you run the fmsetupfls script, which sets up the license server. You can also run fmsetupfls at a later time to set up additional licenses. Important: You must run fmsetupfls on the license server host.
34 CHAPTER 4 Setting up licenses where is the full pathname of the directory where the licensing files will be stored. Specify a directory to which all members of the workgroup have read and execute permission. 2 Provide the information that the script requests. The script creates the scripts that control shared licenses on your network. It stores these scripts in the directory you specified when you started fmsetupfls.
ADOBE FRAMEMAKER 8 35 Installation Guide To set up licensing variables when a user starts FrameMaker: 1 Create an fminit directory in the user’s home directory. 2 Change to that directory. 3 Create a symbolic link to the workgroup’s env.sh file, by entering this command (where workgroup_dir is the workgroup directory you specified when you started fmsetupfls): workgroup_dir/env.sh env.
36 CHAPTER 4 Setting up licenses Setting up personal licenses You set up personal licenses by entering the information from your registration card (or other licensing sheet) into the licenses file. You can enter personal licensing information for multiple users in a central licenses file in $FMHOME, or you can enter each user’s licensing information in a personal licenses file in the user’s home directory.
ADOBE FRAMEMAKER 8 37 Installation Guide 2 Start the fmaddlicense program by entering:| 3 Use fmaddlicense to enter the information on your registration card (or other licensing sheet) into the licenses file. For instructions, see the following section, “Using the fmaddlicense program.” Enter licensing information for one user only. Using the fmaddlicense program The fmaddlicense program is your tool for adding and administering licenses.
38 CHAPTER 4 Setting up licenses where license_path is the path to the licenses file. The default path is $FMHOME/fminit. The fmaddlicense prompt appears: fmaddlicense-> 2 Use fmaddlicense by entering commands at the prompt and pressing Return. The rest of this section explains the fmaddlicense commands. Getting help You can view a list of fmaddlicense commands. Parameters in brackets are optional.
ADOBE FRAMEMAKER 8 39 Installation Guide To add a shared license: Enter registration_number where registration_number is the registration number on your registration card (or other licensing sheet). If the registration number is not a valid shared license registration number, fmaddlicense warns you. Make sure that you entered the registration number correctly.
40 CHAPTER 4 Setting up licenses For each license, fmaddlicense reports product type, license type, and part of the registration number. It also reports the user names assigned to personal licenses. For example: License FrameMaker Personal Adobe 11-1-11111 Assigned to: user_name where user_name is the login ID of the user of the personal license. In FrameMaker 8, Adobe serial numbers are locale-independent, and the product type is generic across locales. For example: Locale Product type in 7.
ADOBE FRAMEMAKER 8 41 Installation Guide Removing and reassigning licenses You must delete a license before moving it to a different licenses file. You cannot use the same license in two licenses files. To remove a personal license from your license file: Enter registration_number To reassign a personal license to a different user: 1 Delete the license (see the preceding instruction). 2 Add the license to the file again, assigning it to the new user. (See “Adding licenses” on page 38.
42 CHAPTER 4 Setting up licenses To have your changes take effect, you must reinitialize the license server process on the license server to load the new licensing information from the licenses file. Before exiting, fmaddlicense asks whether you want to reinitialize the license server process. If you choose not to reinitialize at this time, you can reinitialize the process later. For information, see “Reinitializing the license server” on page 43.
ADOBE FRAMEMAKER 8 43 Installation Guide where host is the name of the license server host and command is an fmflsadm command. You can omit -flshost host to check the host specified by the FM_FLS_HOST environment variable. Checking the license server Use the fmflsadm ping command to check whether the license server process is running on a license server host.
44 CHAPTER 4 Setting up licenses To start the license server process automatically: Add the following line to the license server host’s system startup file: licenses_file > /dev/console 2>&1 where licenses_file is the full pathname of the licenses file you want to use. How licensing works This section gives more detailed information about licensing. Licensing files, scripts, programs, and variables The fmsetupfls script creates the scripts that control shared licenses on your network.
ADOBE FRAMEMAKER 8 45 Installation Guide env.sh and env.csh scripts The fmsetupfls program creates env.sh and env.csh scripts, or updates them if they already exist. These scripts set the values of the FM_FLS_HOST and FM_FLS_AUTO licensing environment variables. FrameMaker uses env.sh to look up the values of these variables. There are sample scripts in the files $FMHOME/fminit/env.sh.ex and $FMHOME/fminit/env.csh.ex.
46 CHAPTER 4 Setting up licenses Note: The fm_flb license broadcaster is designed to transmit information from each machine running FrameMaker to ensure that there are no duplicate licenses being used on the network. All network broadcasts communicate with all I/O ports, which could activate dial-on-demand connections. It is the duty of the network administrator to configure networks and routers responsibly. fm_fls.log file The fm_fls program stores information about license usage in the fm_fls.log file.
ADOBE FRAMEMAKER 8 47 Installation Guide 2 The product searches for a personal license in $HOME/fminit/licenses and then in $FMHOME/fminit/licenses. • If it finds a personal license, the licensed version of the product starts. • If a licenses file exists but the product doesn’t find a personal license, the product continues with step 3. 3 The product checks the licensing environment variable, FM_FLS_HOST, to determine whether shared licensing is installed.
48 CHAPTER 4 Setting up licenses • If fm_fls doesn’t respond, the product runs the fm_fls_auto script (the script named by FM_FLS_AUTO) to start the license server process, and then continues with step 5. (It can’t run fm_fls_auto if FM_FLS_AUTO is not set. In that case, the product displays an alert that the user doesn’t have a license. The user may be able to get a license from a process running on a different host (see the Install_Readme file).
ADOBE FRAMEMAKER 8 49 Installation Guide The log_file option specifies the pathname of the fm_fls.log file from which you will generate the report. This pathname is required.
50 CHAPTER 4 Setting up licenses To display additional messages at startup: Add the -nlverbose command-line option to the command that starts the product. For example: - For a list of commands for starting FrameMaker, see , “Starting FrameMaker.” Specifying personal licenses If both personal and shared licenses are installed on your network, users can specify the type of license they want FrameMaker to use. If FrameMaker cannot obtain that type of license, it starts a demonstration version.
ADOBE FRAMEMAKER 8 51 Installation Guide FrameMaker reports that there are no licenses This problem occurs when the FrameMaker cannot find the licenses file in $HOME/fminit or in $FMHOME/fminit. It asks if you want to run a demonstration version. You might not have set up the licenses file, or it might have been unintentionally removed. Restore the licenses file or use the information from your registration card (or other licensing sheet) and the fmaddlicense program to recreate the file.
52 CHAPTER 4 Setting up licenses To get a license when the product cannot communicate with the license server: 1 Do one of the following: • If your workstation is the license server host, change the name of the license server host in the License dialog box to localhost and try to get a license again. • If the license server host is a remote host, or if the preceding action doesn’t solve the problem, continue with the following steps.
ADOBE FRAMEMAKER 8 53 Installation Guide where host is the name of the license server host. You can omit -flshost host to check the host specified by the FM_FLS_HOST environment variable. The fmflsadm program reports whether or not the license server process is running. 6 If the process isn’t running, restart the license server process by entering: $FMHOME/bin/fmsetupfls workgroup_dir where workgroup_dir is the licensing directory for the workgroup.
54 CHAPTER 4 Setting up licenses • The date on your workstation is different from the date on the license server host. (If the difference is 4 hours or less, you should be able to obtain a license. If the difference is between 4 and 8 hours, you may be able to obtain a license. If the difference is more than 8 hours, you won’t be able to obtain a license.) • The licenses file was updated after the license server process was started. If this is the case, you can instruct the process to reread the file.
ADOBE FRAMEMAKER 8 55 Installation Guide • To start the server and store the licensing log file in the standard location, enter: licenses_file • To start the server and specify a nonstandard location for the licensing log file, enter: licenses_file log_file_path where log_file_path is the full pathname to the directory in which you want to store the log file. For more information on the log file, see “fm_fls.log file” on page 46.
56 CHAPTER 4 Setting up licenses For example: - 4 On any systems that are still running FrameMaker, kill the fm_flb process. For each workstation, use the command shown in step 3 to determine the process number, and use the kill command to kill the process. If you skip this step, users might see an error message and have to provide the name of the new license server in order to continue. 5 Use the fmsetupfls program to set up the new license server.
57 Chapter 5: Starting FrameMaker This chapter describes how to start licensed and demonstration versions of Adobe® FrameMaker® and how to run the product on a remote workstation or server. While running a demonstration version, you can use all features except the Save command. Starting FrameMaker To start FrameMaker, enter in a UNIX window one of the commands in the following table, where language represents a user-interface language (for example, ukenglish, deutsch, francais, or japanese).
58 CHAPTER 5 Starting FrameMaker Note: These commands work only if you have put the FrameMaker directory in your path, as described in , “Setting up the user environment.” If you have not done so, you must enter the full pathname (for example, /usr/frame/bin/maker). There are also many command-line options you can use to customize FrameMaker. For example, you can specify a file to open when the product starts, or change a resource for that session only.
ADOBE FRAMEMAKER 8 59 User Guide Running FrameMaker on a remote system FrameMaker can run locally or remotely. When running locally, FrameMaker runs as a client application on a user’s workstation. When running remotely, FrameMaker runs as a client application on a remote system, and employs the user’s workstation only as a display server, thus conserving workstation resources.
60 CHAPTER 5 Starting FrameMaker 3 Designate a workstation as a display server by doing one of the following (where myhost is the host name of the workstation): • If you are using the C shell, enter setenv DISPLAY myhost:0.0 • If you are using the Bourne shell or Korn shell, enter: DISPLAY=myhost:0;export DISPLAY • If you don’t want to change the DISPLAY variable, instruct users to add the -display hostname:0 option to the command they use to start FrameMaker.
61 Appendix A: Upgrading from an earlier version If you have an earlier version of Adobe® FrameMaker® installed, you might want to retain its setup files and font information. After you install the new FrameMaker files, follow the instructions in this appendix for copying files from the earlier version’s installation directory. For information on new features in version 8 of FrameMaker, see the FrameMaker User Guide.
62 CHAPTER 6 Using existing setup files The resource files and other setup files in $FMHOME/fminit and $FMHOME/fminit/UILanguage directories let you customize FrameMaker for your installation. (UILanguage is a user-interface language directory, for example, usenglish or francais.) For more information about these setup files and about the structure of the fminit directory, see the online manual Customizing FrameMaker on the Adobe website: www.adobe.com/devnet/framemaker/pdfs/Customizing_Frame_Products.pdf.
ADOBE FRAMEMAKER 8 63 Installation Guide To customize the new features of FrameMaker, compare your existing resource files with the standard ones installed with this version. (If you open the files in FrameMaker, you can use the document comparison feature to do this.) Add the new resources to your existing resource files. For more information about resources, see the online manual Customizing FrameMaker on the Adobe website: www.adobe.com/devnet/framemaker/pdfs/Customizing_Frame_Products.pdf.
64 CHAPTER 6 Note: With version 8, you can open documents created with earlier versions of FrameMaker. However, you can open a FrameMaker 8 document in earlier versions only indirectly. First you must open the document in version 8 and save it as a FrameMaker 7.0 or Maker Interchange Format (MIF) 7.0 document. You can then open the FM or MIF file in the earlier version. New features in version 8 are ignored, and messages in a UNIX window will report MIF statements for these features as being “skipped.
ADOBE FRAMEMAKER 8 65 Installation Guide If you added any other Adobe Type 1 fonts to version 7.2 or earlier, follow these steps to add each font to the current version. To add fonts from version 7.2 or earlier to the current version: Copy all custom font files to the current font directory ($FMHOME/fminit/fontdir). For a complete description of the fontlist format, see Working with Fonts in FrameMaker for UNIX, available in this path: $FMHOME/fminit//Documents/Unix_Fonts.pdf.
66 CHAPTER 6
ADOBE FRAMEMAKER 8 67 Installing FrameMaker for UNIX Index A D F add command 27 delete command 28 Adobe Acrobat 7.0, installing 5 desktop environments, integrating with 15 files, setup, using from an older release 41 Adobe Acrobat Reader, installing 5 fm_flb program 30 aliases for starting FrameMaker products 18 directory, FrameMaker product 5 fm_fls program 30 done command 28 fm_fls.log file 31, 32 C E FM_FLS_AUTO environment variable 30 CD-ROM drive env.
68 INDEX fmcopy script 14 H fmflsadm program 29–?? help command 26 using setup files from an older release 41 ping command 29 reinit command 29 FMHOME environment variable 15 I J installing 5–14 Japanese functionality additional platforms later 13 system requirements for 1 fmreport program 32 basic or custom 6 user interface installation 6 fmsetupfls script 23 fmusersetup script 15 creating a FrameMaker product directory 5 L fonts fonts 7 LANG environment variable 6 fonts added in an e
ADOBE FRAMEMAKER 8 69 Installing FrameMaker for UNIX finding, problems in 34 P listing 27 personal licenses 21 network requirements 22 setting up 25 obtaining, problems in 35 ping command 29 personal 21 startup for FrameMaker products 31 setup files, using from an older release 41 shared licenses network requirements 22 process for getting 31 R reassigning 27 registration numbers 22 registration numbers for 22 reinit command 29 removing 27 requirements, system 1 reporting usage 32 settin
70 INDEX V variables, environment FM_FLS_AUTO 30 FM_FLS_HOST 30 FMHOME 15 LANG 6 XKEYSYMDB 19 X XKEYSYMDB environment variable 19 XkeysymDB file, using updated 19
