DECwrite______________________________________ Installation Guide for VMS Systems Order Number: AA-PHGZA-TE October 1991 This guide describes how to install Version 2.0 of DECwrite on a VMS system. Revision/Update Information: This is a new manual. Software Version: DECwrite Version 2.0 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ October 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1991. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: CDA, DDIF, DECchart, DECdecision, DECfonts, DECnet, DECpage, DECwindows, DECwrite, Digital, DTIF, LiveLink, PATHWORKS, PrintServer 40, ScriptPrinter, ULTRIX, ULTRIX Worksystem Software, VAX, VAXcluster, VAX RMS, VAXstation, VMS, WPS-PLUS, XUI, and the DIGITAL logo Licensed to Digital Equipment Corportation, Maynard, Massachusetts. Copyright © Studio Advertising Art 1988. All rights reserved. The following are third-party trademarks: Arts & Letters is a registered trademark of Computer Support Corporation. Helvetica and Times are registered trademarks of Linotype Company. IBM is a registered trademark of International Business Machines Corporation. ITC Avant Garde Gothic, ITC Souvenir, and ITC Lubalin Graph are registered trademarks of International Typeface Corporation. Lotus and 1-2-3 are registered trademarks of Lotus Development Corporation. Microsoft, MS, and MS-DOS are registered trademarks and Windows is a trademark of Microsoft Corporation. Motif and OSF/Motif are trademarks of Open Software Foundation, Inc. PostScript is a registered trademark and Display PostScript, ATM, and Type Manager are trademarks of Adobe Systems, Inc. Sun and SPARC are registered trademarks and SPARCstation is a trademark of Sun Microsystems, Inc. TeX is a trademark of American Mathematical Society. 20/20 is a trademark of Access Technology, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc. Usage Alert, Electronic Thesaurus, International Hyphenators, and International CorrectSpell licensed from Houghton Mifflin Company. Copyright© 1985, 1987, 1988 by Houghton Mifflin. German© 1985, 1987 by Langenscheidt K.G. French in cooperation with Librairie Larousse. Italian© 1988 by Nicola Zanichelli. All rights reserved. U.S. Pat. Nos. 4,580,241, 4,724,523 and 4,771,401. Canadian Pat. No. 1,203,916. Thesaurus U.S. Pat. No. 4,724,523. English based upon THE AMERICAN HERITAGE DICTIONARY. Thesaurus based upon ROGET'S II THESAURUS. Reproduction or disassembly of embodied computer programs or algorithms prohibited. WordPerfect is a registered trademark of WordPerfect Corporation. ZK5648 This document is available on CDROM. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing for DECwrite Installation on a VMS System 1.1 DECwrite Distribution Kit....................... 1-1 1.2 Prerequisite Software........................... 1-2 1.3 Prerequisite Hardware........................... 1-3 1.4 Privileged Account.............................. 1-4 1.5 License Registration............................ 1-4 1.6 Startup Procedures.............................. 1-5 1.7 VAXcluster Considerations....................... 1-5 1.8 System Quotas................................... 1-6 1.8.1 Disk Space Requirements ...................... 1-6 1.8.2 System Parameter Values ...................... 1-7 1.8.2.1 Checking Parameter Values.................. 1-8 1.8.2.2 Calculating GBLPAGES and GBLSECTIONS Parameter Values........................... 1-8 1.8.2.3 Changing Parameter Values with AUTOGEN..... 1-9 1.9 System Disk Backup.............................. 1-9 2 Installing DECwrite 2.1 VMSINSTAL Requirements.......................... 2-2 2.2 VMSINSTAL Procedure............................. 2-3 iii 3 DECwrite Postinstallation Procedures 3.1 Editing Startup Files........................... 3-1 3.1.1 Editing SYSTARTUP_V5.COM ..................... 3-1 3.1.2 Editing WRITE$STARTUP.COM .................... 3-3 3.1.3 WRITE$EXAMPLES ............................... 3-4 3.1.4 Editing SYS$MANAGER:SYLOGIN.COM .............. 3-5 3.2 Installing DECwrite on a Standalone System...... 3-5 3.3 Installing DECwrite on a VAXcluster............. 3-5 3.4 Rebooting the System............................ 3-7 3.5 User Account Requirements....................... 3-7 3.5.1 Privileges ................................... 3-8 3.5.2 User Account Quotas .......................... 3-8 3.5.3 FileView Account Quotas ...................... 3-9 3.5.4 Modifying User Account Quotas ................ 3-10 3.6 Tuning Your System.............................. 3-11 3.7 Installation Verification Procedures............ 3-12 3.8 Invoking DECwrite............................... 3-13 3.8.1 Running DECwrite from the Session Manager .... 3-15 3.8.2 Running DECwrite from FileView ............... 3-17 3.8.3 Running DECwrite from DCL .................... 3-17 3.9 DECwrite Sample Documents....................... 3-18 3.10 Compiling Fonts on Remote Workstations.......... 3-18 3.10.1 Compiling and Installing Fonts on VMS Systems....................................... 3-19 3.10.2 Compiling and Installing Fonts on ULTRIX Systems....................................... 3-20 3.10.3 Compiling and Installing Fonts on a Sun SPARCstation System........................... 3-21 3.10.4 Compiling and Installing Fonts on a PC DECwindows System............................. 3-21 3.11 Determining and Reporting Problems.............. 3-22 4 Using the DECwrite Font Utility 4.1 Overview of Adding Fonts........................ 4-1 4.2 Copying and Configuring Font Files.............. 4-2 4.3 Adding New Fonts to DECwrite.................... 4-3 4.3.1 Adding Fonts All at Once, Without Customization................................. 4-5 iv 4.3.2 Adding Fonts Individually .................... 4-6 4.3.2.1 Adding Fonts Individually, Using Defaults................................... 4-6 4.3.2.2 Adding Fonts Individually, and Customizing................................ 4-7 4.4 Font Utility Commands and Descriptions.......... 4-10 4.4.1 Changing Characteristics of Added Fonts ...... 4-15 4.5 Revealing a Hidden Font......................... 4-16 4.6 Troubleshooting Font Problems................... 4-17 4.6.1 Setting the Display Variable ................. 4-19 4.6.2 Checking Security Access ..................... 4-19 4.6.3 Checking Session Login ....................... 4-20 4.6.4 Restarting Your Session or DECwindows Display Server........................................ 4-20 4.6.5 Checking the Location of Screen Font, AFM, and PostScript Files.............................. 4-20 4.6.6 Comparing Screen Font, AFM, and PostScript Outline Files................................. 4-21 4.6.6.1 Displaying Screen Font Attributes.......... 4-21 4.6.6.2 Editing AFM and PostScript Outline Files... 4-23 A Printouts from Sample DECwrite Installations A.1 Full DECwrite Installation...................... A-1 A.2 Font Only DECwrite Installation................. A-8 Index Figures 2-1 Successful Installation Display .............. 2-19 Tables 1-1 Free Disk Blocks Required to Install DECwrite, Including Clip Art............................ 1-7 1-2 Minimum Required Global Pages and Sections ... 1-8 2-1 DECwrite Kit Names ........................... 2-3 3-1 Language Variant Parameters .................. 3-2 3-2 International Spell Lexicons ................. 3-7 3-3 User Account Quotas .......................... 3-8 v 3-4 Lexicons supplied by DECwrite Kits ........... 3-13 4-1 DECwrite Font Utility Commands ............... 4-11 4-2 Troubleshooting Summary ...................... 4-18 4-3 Font File Locations .......................... 4-21 4-4 AFM, PostScript, and Screen Font Comparisons................................... 4-23 vi ________________________________________________________________ Preface DECwrite is an integrated document processing application that is available on a variety of hardware, operating, and windowing systems, referred to as platforms. Since DECwrite is supported by Digital's[TM] Network Application Services (NAS), which allow application software to work in a heterogeneous computer environment, you can transfer documents and use DECwrite in a similar fashion on all its platforms. Purpose of This Guide This guide describes how to install DECwrite on the VMS operating system. You should review the entire guide before you start the installation. Who Should Use This Guide This guide is for VMS system managers or others responsi- ble for installing system software. To install DECwrite software, you must have access to a privileged account such as the SYSTEM account, and you must be familiar with the VMS installation procedure (VMSINSTAL). Structure of This Guide This guide has four chapters and one appendix. o Chapter 1 describes installation prerequisites and suggestions. o Chapter 2 is the installation procedure. o Chapter 3 describes postinstallation procedures and general usage information. vii o Chapter 4 describes the DECwrite Font Utility that allows you to add, manage, and delete new fonts. o Appendix A shows two sample installation procedures for reference purposes. Files DECwrite installs or modifies on your system are listed in the DECwrite release notes. Section 2.2 describes how to locate and print the release notes for your kit. Documentation Use the documentation for your DECwrite kit in the order shown in Figure 1. DECwrite also supplies several online files that contain samples and additional information, including information about CDA converter[1] options and error messages. Consult the DECwrite Supplement for information about the location of these files. Additionally, if you are an advanced user of the DECwrite CDA converters, you may be interested in the document Using the CDA Converters, which you can purchase separately from Digital. ________________________Note ________________________ Refer to your VMS system documentation for guide- lines about how to manage files and for information about how to maintain backup copies of documents, how to protect documents, and how to create directories where you can store related documents. That information is not covered in this guide. _____________________________________________________ For more information about the VMSINSTAL command procedure, see one of the following books: o VMS System Manager's Manual (VMS base documentation set) ___________________ [1]The CDA converters provide features for transforming files to and from DECwrite's standard format for documents. viii o Guide to Setting Up a VMS System (VMS full documenta- tion set) For more information about DECwindows, see the following: o VMS DECwindows User's Guide o VMS DECwindows Desktop Applications Guide Conventions The following conventions are used in this guide: A key name is shown enclosed to indicate that you press a key on the keyboard. blue-green ink Blue-green ink indicates information that you must enter from the keyboard. In the Bookreader, information you must enter from the keyboard is indicated by boldface text. UPPERCASE TEXT Uppercase letters indicate that you must enter a command (for example, enter OPEN/READ) or indicate the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. DECchart The term DECchart refers to the DECchart[TM] software. DECdecision The term DECdecision refers to the DECdecision[TM] software. DECpage The term DECpage refers to the DECpage[TM] software. DECwrite The term DECwrite refers to the DECwrite[TM] software. WPS-PLUS The term WPS-PLUS refers to the WPS-PLUS[TM] software. ix A double right arrow is used to show the choosing of a submenu or a dialog box. The following example means choose Left Double Quote from the Insert Character submenu of the Insert menu: Choose Insert Insert Character Left Double Quote. x 1 ________________________________________________________________ Preparing for DECwrite Installation on a VMS System This chapter describes tasks that you must perform when installing DECwrite, and suggests the best methods for preparing for installation. Installing DECwrite is similar to installing other VMS layered products. You should: 1. Take an inventory of the software distribution kit. 2. Make sure that your system has the prerequisite software and hardware. 3. Register your DECwrite license according to the VMS License Registration section in this chapter. 4. Prepare your system and its users for installation. 5. Print and read the Release Notes. 6. Perform the installation procedure and any necessary postinstallation procedures. 7. Resume normal operations after you complete the installation. You should allow between 30 minutes and 2 hours and 15 minutes for the installation, depending on the speed of the system on which you are installing and the options you select. It takes 5 minutes to run the IVP. 1.1 DECwrite Distribution Kit Each DECwrite distribution kit contains: o A bill of materials (BOM) and indented bills report (BIL) o The distribution media for the DECwrite software o Documentation for the product Preparing for DECwrite Installation on a VMS System 1-1 1.1 DECwrite Distribution Kit Media Only kits include the installation guide only. o The Product Authorization Key (PAK) To ensure that you have a complete kit, check the kit contents against the bill of materials and the indented bills report. Check also that you received the correct distribution media, labeled as DECwrite V2.0. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. 1.2 Prerequisite Software DECwrite Version 2.0 includes both XUI and Motif graphical user interfaces (GUI). You choose which DECwrite GUI to use at installation time. Note that only one DECwrite GUI can be installed on a single system; that is, you cannot install DECwrite/XUI and DECwrite/Motif on the same system. For DECwrite/XUI you need to be running VMS Version 5.3-1 or later. For DECwrite/Motif you need to be running VMS Version 5.4 or later and DECwindows Motif for VMS Version 1.0. To install DECwrite you must have: o A valid VMS operating system configuration running the minimum required version of VMS as specified above, having the VMS required saveset o DECwindows installed To execute the IVP during the installation, DECwindows should also be running. Since DECwrite is a DECwindows application, it can run in either of the following ways: o Standalone execution - running the DECwindows X11 display server and the client application (DECwrite) on the same machine o Remote execution - running the DECwindows X11 display server and the client application (DECwrite) on different machines 1-2 Preparing for DECwrite Installation on a VMS System 1.2 Prerequisite Software This requires that a valid DECwindows transport mechanism also be installed. For example, these include DECnet, TCP/IP, and LAT. For standalone execution, the following DECwindows components must be installed on the machine: o VMS DECwindows Compute Server (base kit, which includes runtime support) o VMS DECwindows Device Support For remote execution in a noncluster VAX environment, the following DECwindows components must be installed: On the workstation: o VMS DECwindows Compute Server (base kit, which includes runtime support) o VMS DECwindows Device Support On the remote machine: o VMS DECwindows Compute Server (base kit, which includes runtime support) o VMS DECwindows Device Support (optional) Refer to the VMS Installation Guide for details. 1.3 Prerequisite Hardware DECwrite/XUI supports all hardware configurations sup- ported by a VMS Version 5.3-1 system running DECwindows, with a minimum of 8 MB of memory. DECwrite/Motif supports all hardware configurations supported by a VMS Version 5.4 system running DECwindows Motif for VMS Version 1.0, with a minimum of 12 MB of memory. See the DECwrite Software Product Description (SPD) for details about supported hardware configurations. Preparing for DECwrite Installation on a VMS System 1-3 1.4 Privileged Account 1.4 Privileged Account To install DECwrite, you must be logged into the system manager's account (SYSTEM), an account that has SETPRV, or an account with at least the following privileges: o CMKRNL o WORLD o SYSPRV Note that the VMSINSTAL procedure turns off BYPASS privilege at the start of the installation. 1.5 License Registration The DECwrite license should be registered and loaded before you install or use DECwrite. The information you need is in the Product Authorization Key (PAK) shipped with DECwrite. The PAK is a paper certificate that contains data about your license. ________________________Note ________________________ If you do not register and load the license before installing DECwrite, the installation will complete but DECwrite will run only in demonstration mode. In demonstration mode you will not be able to save documents. You will have to reinstall DECwrite after you have properly registered and loaded the PAK, to be able to use DECwrite's full capabilities. _____________________________________________________ There are multiple license types for DECwrite Version 2.0. While it is necessary to have only one license type active for DECwrite, it will check for the existence of the other license types until a valid one is found. License failures for some of these other license types may be displayed to the operator's console and can be disregarded. These messages can be controlled system-wide for all products by defining the lmf$display_opcom_message logical name. See the VMS License Management Utility manual for details. 1-4 Preparing for DECwrite Installation on a VMS System 1.5 License Registration To register the license, first log in to a privileged account, such as the system manager's account, SYSTEM. Then choose one of the following procedures to perform the registration. The second method is faster for experienced users. o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When prompted for information, respond with data from your Product Authorization Key (PAK). OR o Issue the DCL commands LICENSE REGISTER and LICENSE LOAD with the appropriate qualifiers that correspond to information on the PAK. For additional information, see the License Management Facility section in your VMS documentation set. 1.6 Startup Procedures If you have previously installed DECwrite, make sure you execute SYS$STARTUP:WRITE$STARTUP.COM before starting the new installation. If you have previously installed any of the International Lexicon kits or are reinstalling DECwrite, make sure you execute the SYS$STARTUP:LCI$STARTUP.COM procedure before starting the installation. This startup procedure defines the logical LCI$LEXICONS. The installation procedure then uses LCI$LEXICONS to place the lexicon, or the spell check dictionary, files in their proper directories. 1.7 VAXcluster Considerations You can install DECwrite on a VAXcluster. In a VAXcluster with a common system disk, you can perform the installation on a single member of the cluster. After the installation is completed, each VAX processor can share the same DECwrite software. You must check the number of global sections and global pages on each node in the VAXcluster where you plan to install DECwrite. Instructions are in the next section. Preparing for DECwrite Installation on a VMS System 1-5 1.7 VAXcluster Considerations See Chapter 3 for details about VAXcluster postinstalla- tion instructions. 1.8 System Quotas You use the VMSINSTAL command procedure to install DECwrite. For VMSINSTAL to run properly, there must be sufficient disk storage space and proper system parameter settings to accommodate the installation. This section describes the recommended disk space and system parameters. 1.8.1 Disk Space Requirements Installing DECwrite requires a certain amount of disk storage space. Once the installation is complete, less storage space is required. Table 1-1 summarizes the storage requirements. The VMSINSTAL command has an Alternate Working Directory (AWD) option. This allows you to designate a di- rectory other than the default working directory (SYS$SYSROOT:[SYSUPD.product-name]) used by VMSINSTAL during the installation. This option is useful if there is little free space on the system disk. ________________________Note ________________________ The values in Table 1-1 apply only to the American English language variant. See the cover letter of the SSA in your kit for the values appropriate to your product variant. _____________________________________________________ 1-6 Preparing for DECwrite Installation on a VMS System 1.8 System Quotas Table 1-1 Free Disk Blocks Required to Install DECwrite, __________Including_Clip_Art______________________________ Installation At Installation For Permanent Type _______Time[1]________ Use[1]___________ System _________________Disk________AWD_Device__System_Disk______ Complete 60,000 60,000 45,000 Font Only 2,200 2,200 1,000 [1]These_values_are_approximate,_but_are_the_maximum_that_ the installation will require. The installation procedure reports the actual number of blocks required, which will be slightly less than these values, and may differ from the sample installation in Chapter 2. __________________________________________________________ Use the DCL command SHOW DEVICE to determine the number of free blocks that are presently available on the system disk: $ SHOW DEVICE SYS$SYSDEVICE If the system disk does not have enough free blocks for permanent use, delete unnecessary files to provide space. If the system disk has enough disk space for permanent use, but does not have enough free blocks at installation time, use any alternate working directory (AWD) on the device having the required AWD disk space. See Table 1-1 for AWD disk space requirements. 1.8.2 System Parameter Values Digital recommends that the system parameter WSMAX be set to at least 4,100. On a single-user workstation, it should be set higher, depending on the amount of workstation memory. The DECwrite executable images and the shared libraries can be optionally installed at DECwrite startup time using the INSTALL utility. Table 1-2 lists the minimum system parameter values required to successfully install all these images and libraries. Preparing for DECwrite Installation on a VMS System 1-7 1.8 System Quotas Table_1-2_Minimum_Required_Global_Pages_and_Sections______ System_Parameter____Minimum_Value_________________________ GBLPAGES 3,116 GBLSECTIONS_________9_____________________________________ If GBLPAGES or GBLSECTIONS are below the recommended values, VMSINSTAL displays a message. Installing the DECwrite images will result in better performance. Make sure to adjust these system parameters before modifying and executing the DECwrite startup procedure WRITE$STARTUP.COM. See Chapter 3 for details. Since installing the DECwrite images and shared libraries is optional, you can safely continue the installation. 1.8.2.1 Checking Parameter Values To check the value of one or more parameters, enter the following command at the DCL prompt: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, use the SHOW command to display the value of each system parameter. After you finish checking parameter values, use the EXIT command to return to DCL level. 1.8.2.2 Calculating GBLPAGES and GBLSECTIONS Parameter Values The values for GBLPAGES and GBLSECTIONS in Table 1-2 indicate that you must have at least 3,116 unused global pages and 9 unused global sections available for the installation. To calculate the number of unused global pages and global sections in your system: 1. Use the DCL F$GETSYI lexical function to determine the number of free global pages and global sections: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 1-8 Preparing for DECwrite Installation on a VMS System 1.8 System Quotas 2. If the number of unused global pages is less than the number specified in Table 1-2, you must increase the value using the AUTOGEN command procedure (instructions follow). The next section describes the procedures for changing these values. For more information, refer to the VMS system management documentation. 1.8.2.3 Changing Parameter Values with AUTOGEN You use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that need to be changed. To change system parameters with AUTOGEN: 1. Edit the SYS$SYSTEM:MODPARAMS.DAT file. For example, to increase the setting for the GBLPAGES system parameter by 2,000, add this line to the file: ADD_GBLPAGES = 2000 2. Enter the following command to recalculate your system parameters: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. For more information about using AUTOGEN, see the instructions on modifying system parameters in the VMS system management documentation. 1.9 System Disk Backup Make a backup copy of your system disk before you install DECwrite. For more information about backing up your system disk, refer to the VMS system management documentation. Preparing for DECwrite Installation on a VMS System 1-9 2 ________________________________________________________________ Installing DECwrite This chapter describes how to run the DECwrite installa- tion procedure. You should allow between 35 minutes and 2 hours and 20 minutes to complete the entire installation, depending on the speed of the system on which you are installing. Allow approximately 10 minutes for a font-only installation. Before you start installing DECwrite, make sure that your system meets the requirements outlined in Chapter 1. DECwrite supports language switching. You can install multiple translated versions of DECwrite on a single system. These translated versions are called language variants. This kit includes two DECwrite language variants: American English and British English. A language variant determines the defaults for attributes such as: o The language used for menus and dialog boxes o The Primary Language and Paper Size for new documents DECwrite performs spell checking, hyphenation, and sorting operations according to the primary language. o The style files to use If you perform the installation of a DECwrite language variant from a workstation running Motif, select the appropriate language from the Language Options dialog box on the Session Manager Options menu before you start the installation. OR If you perform the installation from a workstation running XUI, select the appropriate language from the Customize Language dialog box on the Session Manager Customize menu. Installing DECwrite 2-1 See the DECwrite Software Product Description (SPD) for a complete listing of the optional spell check dictionaries. DECwrite installs the language-specific files in the appropriate language-specific subdirectories. See the DECwrite Release Notes for a complete listing of these files and directories, plus a listing of all the files a DECwrite installation installs or modifies. Section 2.2 describes how to locate and print the release notes for your DECwrite kit. Appendix A contains a printout of a typical installation procedure for your reference. You can install the entire DECwrite kit, with or without clip art, or just the screen fonts supplied by DECwrite. If you are installing DECwrite: o In a VAXcluster that includes workstations, install the entire kit. o On a standalone workstation that runs DECwrite locally, install the entire kit. o On a standalone workstations that always run DECwrite from a remote system, you need install only the screen fonts. This allows the standalone workstation to run DECwrite only from the remote system, and access the full set of supported fonts. Similarly, if a standalone workstation user not running DECwrite wants to use either DECwindows Mail or the DDIF viewer to view documents containing equations, then you need to install DECwrite screen fonts on that workstation. 2.1 VMSINSTAL Requirements When you invoke the DCL command VMSINSTAL, it checks: o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether DECnet is up and running o Whether any users are logged in to the system 2-2 Installing DECwrite 2.1 VMSINSTAL Requirements If VMSINSTAL detects a problem during the installation procedure, it notifies you and asks if you want to continue. To stop the installation and correct the problem, enter NO or press the Return key. After you have made the correction, you can restart the installation. To cancel the installation procedure at any time, press Ctrl/Y. The installation procedure deletes all files it has created up to that point and exits. You can then restart the installation. Digital recommends that you refer to the section on the VMSINSTAL command procedure in your VMS documentation set. In the VMS base documentation set, see the VMS System Manager's Manual. In the VMS full documentation set, see the Guide to Setting Up a VMS System. 2.2 VMSINSTAL Procedure You must use the VMSINSTAL command procedure to install DECwrite. Follow these steps to begin the installation: 1. Log in to a privileged account, such as the VMS system manager's account, SYSTEM. 2. Ensure that there are no active users on the system. 3. Enter a command in the following format to run VMSINSTAL: $ @SYS$UPDATE:VMSINSTAL kit-name device-name OPTIONS N where kit-name is the language variant DECwrite kit, and where device-name is the device specification for the distribution media, for example, MUA0:. See Table 2-1 for a list of the languages and their DECwrite kit names. Table_2-1_DECwrite_Kit_Names______________________________ Language_________Kit_Name_________________________________ English (continued on next page) Installing DECwrite 2-3 2.2 VMSINSTAL Procedure Table_2-1_(Cont.)_DECwrite_Kit_Names______________________ Language_________Kit_Name_________________________________ American DECWRITE020 English British DECWRITE020 English Danish DECWRITEDA020 Dutch DECWRITENE020 Finnish DECWRITESU020 French French DECWRITEFR020 Belgian DECWRITEFR020 French Canadian DECWRITEFR020 French Swiss French DECWRITEFR020 (continued on next page) 2-4 Installing DECwrite 2.2 VMSINSTAL Procedure Table 2-1 (Cont.) DECwrite Kit Names __________________________________________________________ Language_________Kit_Name_________________________________ German German DECWRITEDE020 Swiss German DECWRITEDE020 Italian Italian DECWRITEIT020 Swiss Italian DECWRITEIT020 Norwegian DECWRITENO020 Spanish DECWRITEES020 Swedish__________DECWRITESE020____________________________ Specifying OPTIONS N indicates that you want to be prompted to display or print the release notes. Specifying OPTIONS AWD=device: where device: is other than SYS$SYSDEVICE, allows you to re-direct the creation of a temporary working directory used by VMSINSTAL, from SYS$COMMON:[SYSUPD.kit-name] to device:[000000.kit- name]. You can also include the name of the root directory where VMSINSTAL creates its working directory by specifying the directory using the format: OPTIONS AWD=device:[dir1.dir2.dir3]. Using this specification VMSINSTAL's working directory is device:[dir1.dir2.dir3]. ________________________Note ________________________ If the device root directory [000000], or the specified root directory [dir1.dir2.dir3], already contains the subdirectory [.kit-name], VMSINSTAL will delete the subdirectory and subdirectory contents before it restores the first saveset from the media. _____________________________________________________ Installing DECwrite 2-5 2.2 VMSINSTAL Procedure If you do not specify the AWD option, the installation creates the temporary working directory on the system disk by default. VMSINSTAL has several other options, described in the VMS software installation documentation. A message similar to the following appears on your screen: VAX/VMS Software Product Installation Procedure V5.4-2 It is 26-AUG-1991 at 15:07. Enter a question mark (?) at any time for help. Your DECnet network is up and running. The following processes are still active: L M N O P * Do you want to continue anyway [NO]? DECwindows requires that DECnet be up and running. 4. Enter YES and press < Return > to continue the installation. You are asked whether you need to back up your system disk: * Are you satisfied with the backup of your system disk [YES]? Generally, you should back up your system disk before any major software installation, as you were instructed in Chapter 1. YES is the default answer. 5. If you backed up your system disk recently, press the Return key to continue. Next, you receive instructions to mount the distribu- tion media you specified when you invoked VMSINSTAL (in this example, MUA0:). If you did not specify where you would mount the distribution volumes, DECwrite prompts you to identify where you have mounted them. Please mount the first volume of the set on MUA0:. * Are you ready? 2-6 Installing DECwrite 2.2 VMSINSTAL Procedure 6. Mount the media, then enter YES and press < Return > to indicate that you are ready to continue. The following messages appear on your screen: The following products will be processed: DECWRITE V2.0 Beginning installation of DECWRITE V2.0 at 15:07 %VMSINSTAL-I-RESTORE, Restoring product save set A ... 7. If you selected OPTIONS N when you first invoked the VMSINSTAL procedure, a menu asks you how you want to handle the release notes: Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: You should review the release notes in case they con- tain any information about changes in the installation procedures. Choosing option 3 displays the release notes and prints a copy. If you do choose an option that prints the release notes, you are prompted for a print queue: * Queue name [SYS$PRINT]: 8. Press < Return > to print the release notes on SYS$PRINT, or type a different active queue name and press < Return >. The screen displays a message similar to the following: Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT You are asked whether you want to continue with the installation: * Do you want to continue the installation? 9. Enter YES to continue, otherwise press < Return >. Installing DECwrite 2-7 2.2 VMSINSTAL Procedure In either case, the release notes are copied to a file in the SYS$HELP directory and you receive a message similar to the following: %VMSINSTAL-I-RELMOVED, The product's release notes have been moved to SYS$HELP. The text format of the release notes are contained in SYS$HELP: and have the name kit-name.RELEASE_NOTES, where kit-name is the DECwrite kit name from Table 2-1. ________________________Note ________________________ Do not delete release notes for earlier DECwrite versions. _____________________________________________________ Note that the name of the release notes file includes the product name and version number. The screen displays the following messages: DECwrite V2.0 Installation Procedure Programs and databases for the Usage Alert, Electronic Thesaurus licensed from Houghton Mifflin. Copyright (c) 1985, 1987 by Houghton Mifflin Company. International CorrectSpell (c) 1987, 1988 by Houghton Mifflin. All rights reserved. US Pat. Nos. 4,508,241, 4,730,269, and 4,771,041. Canadian Pat. No. 1,203,916. Thesaurus U.S. Pat. No. 4,724,523. Portions licensed to Digital Equipment Corporation, Maynard, Massachusetts Copyright (c) Frame Technology Corporation 1989. All rights reserved. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... You can install the DECwrite kit completely or just the video fonts required to use the DECwrite Equation Editor. If you are installing this kit for use on a workstation, or on a VAXcluster that includes workstations, then you should install the entire kit. This requires 60000 blocks. If you are installing this kit on a workstation that will only run DECwrite from a remote system, then only the video font files are needed. This requires 2200 blocks. 2-8 Installing DECwrite 2.2 VMSINSTAL Procedure You can install the entire DECwrite kit or just the screen fonts supplied by DECwrite. If you are installing DECwrite: o In a VAXcluster that includes workstations, install the entire kit. o On a standalone workstation that runs DECwrite locally, install the entire kit. o On a standalone workstation that always runs DECwrite from a remote system, you need install only the screen fonts. This allows the standalone workstation to run DECwrite only from the remote system, and access the full set of supported fonts. For a listing of the fonts supplied by DECwrite, see the DECwrite Release Notes. You receive information about the number of blocks required to install the entire kit, or to install only the screen font files. You are then asked if you want to install the entire kit: * Do you want to install the entire kit [YES]? This kit contains the user interface for both DECwrite/American English and DECwrite/British English. You should install the appropriate user interface according the type of DECwrite license you have purchased. Installing DECwrite 2-9 2.2 VMSINSTAL Procedure Choose one of the following: 1) DECwrite/American English user interface 2) DECwrite/British English user interface * Enter choice [1]: ? DECwrite is translated into many languages. These translated version are called language variants. This kit includes two DECwrite language variants: American English and British English. A language variant determines the defaults for attributes such as: - the language in which the menus and dialog boxes are presented. - the Primary Language and Paper Size for new documents. DECwrite performs spell checking, hyphenation, and sorting operations according to the primary language. - the style files to use. 10.Press < Return > if you are installing American English. Enter 2 if you are installing British English. Installing DECwrite/American English... If you have DECwindows Motif, you have a choice of either the Motif or XUI graphical user interface (GUI). The screen displays: You have DECwindows Motif installed on your system. You can choose to install DECwrite with a Motif or XUI graphic user interface (GUI). Note: You cannot install both DECwrite/Motif and DECwrite/XUI on a single system. Choose one of the following GUIs: 1) DECwrite/Motif 2) DECwrite/XUI * Enter choice [1]: DECwrite Version 2.0 may be installed with one of two graphical user interfaces (GUIs), OSF/Motif or X User Interface (XUI). 2-10 Installing DECwrite 2.2 VMSINSTAL Procedure The XUI interface is the same as that used with earlier versions of DECwrite. The Motif GUI is new for DECwrite Version 2.0. The Motif GUI requires that DECwindows Motif for VMS Version 1.0 (or later) be installed on your system. Enter the number of the GUI you want to install, and press < Return >. The screen displays: Installing DECwrite/Motif... This kit contains an optional clipart library composed of Encapsulated PostScript pictures, DDIF pictures, and DDIF images. Its total size is 9915 blocks. * Do you want to install the clip art library [YES]? 11.Press < Return > if you want to install the clip art library. You can install the clip art library in sys$sysdevice:[clipart] by default, or you can install it in another location. DECwrite asks you to identify a directory other than the default directory where you want to place the clip art files. Specify a device and directory on which to install the clip art library * Device and directory [sys$sysdevice:[clipart]]: 12.Enter the name of another directory where you want to place the files, OR Press < Return > to accept the default directory. For example: You have chosen the device and directory USER:[PUBLISH.CLIPART] * Is this correct [YES]? 13.Press < Return > to confirm your choice of the directory. The installation also reinstalls the DECwrite style files. The installation prompts you to make backup copies if you have modified the original style files in cda$library:. Installing DECwrite 2-11 2.2 VMSINSTAL Procedure ************************************************************* Note: This installation will replace the DECwrite supplied style files in CDA$LIBRARY. If you have made modifications to these files, make backup copies before continuing. For example: $ backup/log cda$library:wr_*.doc_style style_files.bck/sav ************************************************************* * Do you want to continue [YES]? If you are installing a language variant of DECwrite that already existed on your system, and if you have made modifications in language-specific style files located on CDA$LIBRARY_XX_YY, you should make an additional backup copy of these files before continuing. This applies, for example, if you have modified the DECwrite/French-supplied style files: $ backup/log cda$library_fr_fr:wr_*.doc_style style_files_fr_fr.bck/sav 14.Create the backup files if necessary. Press < Return > once you have made the backup files, or if you do not need to preserve them. This kit requires DECchart V1.5-5 or later. If your system does not have the required version of DECchart installed, the screen displays a message similar to the following: ************************************************************* DECchart V1.5-5 will be installed since it does not exist on your system. ************************************************************* If your system does have a version of DECchart Version installed, the screen displays a message similar to the following: ************************************************************* DECchart V1.n already exists on your system. You may choose to reinstall DECchart V1.n or use the currently installed version. ************************************************************* 2-12 Installing DECwrite 2.2 VMSINSTAL Procedure * Do you want to reinstall DECchart [NO]? Reinstall DECchart if you are installing this kit on a system running multiple language versions of DECwrite. For example, if the French version of DECwrite is currently installed and you are installing the German version, then reinstall DECchart. You should also reinstall DECchart if you want to change the Graphical User Interface of DECchart. For example, if you are installing DECwrite Motif and you have the correct version and language of DECchart already installed, but in XUI Graphical User Interface, you can reinstall DECchart to get the Motif Graphical User Interface. 15.Enter YES and press < Return >. The screen displays: This kit requires the DECwrite Equation Editor V1.1-2 or later. If your system does not have the DECwrite Equation Editor V1.1-2 or later installed, the screen displays the following message: The DECwrite Equation Editor V1.1-2 will be installed since it does not exist on your system. If your system does have the DECwrite Equation Editor V1.1-2 or later installed, the screen displays the following message: ************************************************************* The DECwrite Equation Editor V1.1-2 already exists on your system. You may choose to reinstall the Equation Editor or use the currently installed version. ************************************************************* * Do you want to reinstall the Equation Editor [NO]? You should reinstall the DECwrite Equation Editor if you are installing this kit on a system running multiple language versions of DECwrite. For example, if the French version of DECwrite is currently installed and you are installing the German version, then reinstall the Equation Editor. Installing DECwrite 2-13 2.2 VMSINSTAL Procedure You should also reinstall the DECwrite Equation Editor if you want to change its Graphical User Interface. For example, if you are installing DECwrite Motif and you have the correct version and language of the Equation Editor already installed, but in XUI Graphical User Interface, you can reinstall the Equation Editor to get the Motif Graphical User Interface. 16.Enter YES and press < Return >. If there are no spell check dictionaries already installed on the system (by previous versions of DECwrite, or by another product) the screen displays: The DECwrite spell check lexicons will be installed in the directory SYS$SYSDEVICE:[LCI.LEXICONS] by default. You may optionally install the files on a device other than the system disk. * Specify a device on which to install the spell check lexicons [SYS$SYSDEVICE:]: 17.Enter the name of the device where you want the spell check dictionaries installed, or enter nothing to use the default device (SYS$SYSDEVICE:), and press < Return >. The screen displays: You have chosen the device SYS$SYSDEVICE: * Is this correct [YES]? 18.Press < Return > to confirm the device. The screen then displays: Checking/registering INTL-LEXICON-AMERICAN Product Authorization Key... ________________________Note ________________________ The Session Manager's language setting should match the language of the DECwrite language variant you are installing. _____________________________________________________ To set the language on a Motif system, choose Language from the Session Manager Options menu and choose the appropriate language from the Language Options dialog box. OR 2-14 Installing DECwrite 2.2 VMSINSTAL Procedure To set the language on an XUI system, choose Language from the Session Manager Customize menu and choose the appropriate language from the Customize Language dialog box. Note that other language variants have different PAKs. The screen then displays: * Do you want to run the IVP after the installation [YES]? 19.If you are NOT installing DECwrite from a workstation, then do not run the IVP. Instead, use a workstation to run the IVP after the installation is completed. If you are installing DECwrite from a workstation, but one that is NOT running DECnet, then do not run the IVP during the installation. Instead, execute the IVP from DCL after the installation is completed, making sure that a display device is defined using the local transport (see the SET DISPLAY DCL command). Otherwise, answer Yes. If your workstation display is not defined, the installation procedure tells you and prompts you for the workstation name. The screen displays: Enter the node name of the workstation on which to display the IVP or press Return to continue and not run the IVP * Node name: 20.Enter the node name of the workstation on which you want to display the IVP. This node name is used to issue a SET DISPLAY command to the appropriate workstation. Note that this requires that the Session Manager's security database be set up properly and that nodes be defined properly in the network databases. For example, if you are installing DECwrite on your own workstation and you have SET HOST 0 from your own account to use the SYSTEM account, then you must add 0::SYSTEM to the security database. See the DECwindows User's Guide for details on the Session Manager's security database. Installing DECwrite 2-15 2.2 VMSINSTAL Procedure The screen then displays: The language in the Language dialog box on the Session Manager's Customize/Option menu must be set to American English in order to run the IVP. Ensure the language is set accordingly before continuing. * Press Return when ready to continue: 21.Make sure that the language is set to the language you are installing, then press < Return >. You are asked whether you want to purge (delete) old versions of files replaced by this installation: * Do you want to purge files replaced by this installation [YES]? Purging is recommended. 22.To purge old versions of the files, press < Return >. The screen displays the following messages: To complete the installation on a standalone VAX 11/780 will take approximately: 135 minutes to install 5 minutes to run the IVP All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? 23.Press < Return > to continue the installation or enter no to stop the installation. The screen displays the following messages: %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... %VMSINSTAL-I-RESTORE, Restoring product save set J ... %VMSINSTAL-I-RESTORE, Restoring product save set L ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE]. The on-line demonstration document, tutorial.doc and the documents used in the Getting Started exercises are in: VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE] 2-16 Installing DECwrite 2.2 VMSINSTAL Procedure %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE.FONTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECWRITE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory GERUND$DKB0:[CLIPART]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[EPS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[ARROWS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[BUILDING]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[COMMUNIC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[ENERGY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[SPORTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[FIGURES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[FINANCE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[GOVERNMT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[SCIENCE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BLDG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BORDR]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BUSNS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_COMM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_DOM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_FIN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_FLAGS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_MISC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_NATUR]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_PEOPL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SCI]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SPORT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SYMBL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_TOONS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_TRANS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_USMAP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_WDMAP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[LCI.LEXICONS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CHART$IVP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECCHART]. The following commands must be added to the system startup command file SYS$MANAGER:SYSTARTUP_V5.COM for all nodes that will be running DECwrite: @sys$startup:write$startup @sys$manager:decw$starti18n @sys$startup:lci$startup.com ! American-English lexicon Installing DECwrite 2-17 2.2 VMSINSTAL Procedure 24.Add the listed commands to the system startup command file for all nodes that will run DECwrite. The screen also displays: If you are installing this kit on a workstation, you should restart DECwindows after the installation has completed: @sys$startup:decw$startup restart 25.Make sure you restart DECwindows after the installation is complete. The installation continues. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %VMSINSTAL-I-FONTS, Updating font directories 153 fonts loaded Creating sys$common:[sysfont.decw.user_75dpi]DECW$FONT_DIRECTORY.DAT 9 fonts loaded Creating sys$common:[sysfont.decw.user_100dpi]DECW$FONT_DIRECTORY.DAT %VMSINSTAL-I-RUNIVP, Executing installation verification procedure(s) Executing IVP for: DECwrite V2.0 The IVP edits a sample document. If the document looks the same as the illustration in the installation guide, then the installation has been successful. After the document window appears, click the mouse in the window to assign input focus, and type Alt/Q (hold down the Compose Character or "Alt" key and press Q) to exit DECwrite and complete the DECwrite portion of the IVP. Note that when executing this IVP for a particular DECwrite language variant, make sure to set the appropriate language in the Language dialog box on the Session Manager's Customize/Options menu. See the installation guide for details. Set your language now before continuing with the IVP. Press return when ready: To set the language on a Motif system, choose Language from the Session Manager Options menu and choose the appropriate language from the Language Options dialog box. OR 2-18 Installing DECwrite 2.2 VMSINSTAL Procedure To set the language on an XUI system, choose Language from the Session Manager Customize menu and choose the appropriate language from the Customize Language dialog box. 26.Return input focus to the terminal window and press < Return >. The screen displays: Starting DECwrite.... 27.The document displayed on the screen should look like Figure 2-1. 28.Complete the instructions in the IVP document, including updating the chart, which serves as an installation verification procedure for DECchart. After you have updated the chart, follow the instructions to close the IVP document. As DECwrite displays the document, the screen displays the following messages: ************************************* DECwrite V2.0 IVP COMPLETED SUCCESSFULLY ************************************* IVP completed for: DECwrite V2.0 Executing IVP for: International Lexicon/American for VMS V1.0 ******************************************** International Lexicon/American for VMS V1.0 IVP COMPLETED SUCCESSFULLY ********************************************* IVP completed for: International Lexicon/American for VMS V1.0 Installation of DECWRITE V2.0 completed at 16:33 Installing DECwrite 2-19 2.2 VMSINSTAL Procedure VMSINSTAL procedure done at 16:34 $Enter the products to be processed from the next distribution volume set. * Products: ^Z VMSINSTAL procedure done at 15:48 ________________________Note ________________________ VMSINSTAL will execute all of the DECwrite compo- nent IVP procedures (DECwrite itself, DECchart, International Lexicon/ American English) and exit successfully. Any errors will be reported by the individual IVP. _____________________________________________________ The installation is complete. Refer to the postinstalla- tion procedures in Chapter 3. 2-20 Installing DECwrite 3 ________________________________________________________________ DECwrite Postinstallation Procedures This chapter describes tasks you must complete after you install DECwrite. 3.1 Editing Startup Files You must edit the system startup file SYSTARTUP_V5.COM and, optionally, WRITE$STARTUP.COM before using DECwrite. 3.1.1 Editing SYSTARTUP_V5.COM Add the following lines to SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:WRITE$STARTUP.COM ! DECwrite $ @SYS$STARTUP:LCI$STARTUP.COM ! International Lexicons ________________________Note ________________________ If an international spell checking dictionary has previously been installed, LCI$STARTUP.COM should be in SYS$MANAGER:SYSTARTUP_V5.COM. _____________________________________________________ If you install a non-American English DECwrite language variant, you should also add DECW$STARTI18N.COM to SYS$MANAGER:SYS$STARTUP_V5.COM. In this case, both WRITE$STARTUP and DECW$STARTI18N require a language parameter specific to the language variant installed on the system. See Table 3-1 for a list of the language parameters. DECwrite Postinstallation Procedures 3-1 3.1 Editing Startup Files Table_3-1_Language_Variant_Parameters_____________________ Language________Parameter_________________________________ American None required English Belgian French FR_BE British EN_GB English Danish DA_DK Dutch NL_NL Finnish FI_FI French FR_FR French FR_CA Canadian German DE_DE Italian IT_IT Norwegian NO_NO Spanish ES_ES Swedish SV_SE Swiss French FR_CH Swiss German DE_CH Swiss_Italian___IT_CH_____________________________________ For example, after the installation of the Swiss- French language variant, you should edit the line in SYS$STARTUP:SYSTARTUP_V5.COM that starts WRITE$STARTUP to add "FR_CH", and add @SYS$STARTUP:DECW$STARTI18N "FR_CH". The two lines would then be: $ @SYS$STARTUP:WRITE$STARTUP "FR_CH" $ @SYS$STARTUP:DECW$STARTI18N "FR_CH" If only American-English is installed WRITE$STARTUP.COM will not have any parameters. If you already have one or more language variants installed, SYSTARTUP_V5.COM should already contain these two lines. Each line contains the parameter P1, represented by the language code or list of language codes, separated by commas, for all language variants present on the system. 3-2 DECwrite Postinstallation Procedures 3.1 Editing Startup Files After installing a new language variant, edit SYSTARTUP_ V5.COM and add the parameter for the newly installed language variant to both lines. For example, if you install the Swiss French language variant on a system where the American English variant has been already installed, change the existing one-line command from: $ @SYS$STARTUP:WRITE$STARTUP to: $ @SYS$STARTUP:WRITE$STARTUP "FR_CH" $ @SYS$STARTUP:DECW$STARTI18N "FR_CH" As another example, if you install the Swiss French language variant on a system where German and British language variants have been already installed, change the following two lines from: $ @SYS$STARTUP:WRITE$STARTUP "DE_DE,EN_GB" $ @SYS$STARTUP:DECW$STARTI18N "DE_DE,EN_GB" to: $ @SYS$STARTUP:WRITE$STARTUP "DE_DE,EN_GB,FR_CH" $ @SYS$STARTUP:DECW$STARTI18N "DE_DE,EN_GB,FR_CH" ________________________Note ________________________ In SYSTARTUP_V5.COM, the command that starts DECW$STARTI18N.COM must be placed after the command that starts the network. _____________________________________________________ See Table 3-1 for a list of the language parameters. 3.1.2 Editing WRITE$STARTUP.COM WRITE$STARTUP defines the logical WRITE$CLIPART to point to the DECwrite clip art directory. See the DECwrite User's Guide for information about the clip art files. The default at installation time is SYS$SYSDEVICE:[CLIPART]. If you installed the clip art during the installation, or if you had the logical name WRITE$CLIPART previously defined, the installation automatically appends the DECwrite Postinstallation Procedures 3-3 3.1 Editing Startup Files correct WRITE$CLIPART logical name definition to WRITE$STARTUP.COM. By default, all the INSTALL commands in WRITE$STARTUP.COM are commented out. You can optionally remove the comments for the images and shared libraries you want to install. This improves system performance on systems where multiple users are running DECwrite concurrently. Make sure you have completed the steps in Section 1.8 before executing WRITE$STARTUP.COM on a standalone system or on other nodes in a VAXcluster. 3.1.3 WRITE$EXAMPLES DECwrite provides an examples directory with demonstration documents, sample clip art, and other documents useful during DECwrite editing. For a complete list of all the examples files, read the file readme.txt in the write$examples directory. For DECwrite systems with language variants, the installation defines the WRITE$EXAMPLES_XX_YY logicals to point to each language-specific subdirectory. The installation places common, nontranslated example files in the top-level WRITE$EXAMPLES directory, and language specific example files in WRITE$EXAMPLES_XX_YY. After you install one or more language variants, you can specify an optional second language parameter to the command that executes WRITE$STARTUP in SYSTARTUP_V5.COM. This allows you to redefine WRITE$EXAMPLES as a search list that will include the top-level examples directory and a language-specific examples directory. For example, assume that you have the British English and German language variants installed on the same system. If you want the German-specific examples directory to be a default directory for demonstration documents, include the following line in the system startup file SYS$STARTUP:SYSTARTUP_V5.COM: $ @SYS$STARTUP:WRITE$STARTUP "DE_DE",EN_GB" "DE_DE" 3-4 DECwrite Postinstallation Procedures 3.1 Editing Startup Files In this example, WRITE$EXAMPLES would be defined using the following command: $ DEFINE/SYS/EXEC WRITE$EXAMPLES WRITE$EXAMPLES_DE_DE, - SYS$COMMON:[SYSHLP.EXAMPLES.DECWRITE] 3.1.4 Editing SYS$MANAGER:SYLOGIN.COM LiveLink [TM] applications started from DECwrite create detached processes. When these applications create detached, or child, processes, the user's LOGIN.COM file is not executed for performance reasons. In some cases, the logicals you normally expect to see are not defined, causing the child process to fail. If you want a logical name to be accessible from a LiveLink application, define the logical name with the qualifier "/job". Note that LiveLink applications do execute SYLOGIN.COM. Care should be taken when constructing SYLOGIN.COM to not assume interactive use only. For example, you should use the lexical function F$MODE(): $ IF F$MODE() .EQS. "INTERACTIVE" THEN EXIT 3.2 Installing DECwrite on a Standalone System If you have installed DECwrite on a standalone worksta- tion, you must restart the DECwindows server in order to use the new screen fonts. Enter @SYS$STARTUP:DECW$STARTUP RESTART to restart the server. ________________________Note ________________________ This will log you out of your workstation session. _____________________________________________________ 3.3 Installing DECwrite on a VAXcluster To install DECwrite on a cluster with a common system disk, make sure you load the DECwrite license and the lexicon license appropriate to the language variant being installed on all nodes in the cluster. DECwrite Postinstallation Procedures 3-5 3.3 Installing DECwrite on a VAXcluster To load the licenses, enter commands in the following format: $mc sysman SYSMAN> set environment/cluster/user=system Remote Password: SYSMAN> do license load LICENSE-NAME Where LICENSE-NAME is the language variant kit name. SYSMAN> do license load intl-lexicon Where intl-lexicon is the name of the spell lexicon. Table 3-2 lists the lexicons. SYSMAN> do @sys$startup:lci$startup SYSMAN> do @sys$startup:write$startup P1 [P2] SYSMAN> do @sys$manager:decw$starti18n P1 !DECwrite language variants SYSMAN> do @sys$startup:decw$startup restart ! Only required for workstations 3-6 DECwrite Postinstallation Procedures 3.3 Installing DECwrite on a VAXcluster Where P1 is the name of the language parameter from Table 3-1, and P2 is the default language used when defining write$examples, as described in Section 3.1.3. SYSMAN> exit Table_3-2_International_Spell_Lexicons____________________ Name__________________Description_________________________ INTL-LEXICON- American English AMERICAN INTL-LEXICON- British English BRITISH-ENG INTL-LEXICON-DEUTSCH German INTL-LEXICON-ESPAŃOL Spanish INTL-LEXICON- French FRANCAIS INTL-LEXICON- Dutch NEDERLANDS INTL-LEXICON-SVENSKA Swedish INTL-LEXICON-ITALIAN__Italian_____________________________ 3.4 Rebooting the System You can reboot your system after you have installed DECwrite and reset the system parameters (if necessary). A system reboot verifies that DECwrite is ready for use, and establishes any new parameter settings. Note, however, that rebooting is optional. 3.5 User Account Requirements To use DECwrite, user accounts on your system must have certain privileges and quotas. The next two sections contain information about these requirements. DECwrite Postinstallation Procedures 3-7 3.5 User Account Requirements 3.5.1 Privileges To use DECwrite, each account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine whether users have the privileges they require. 3.5.2 User Account Quotas You must make sure that the appropriate user accounts have sufficient quotas to be able to use DECwrite. Table 3-3 summarizes minimum recommended process quotas. Table_3-3_User_Account_Quotas_____________________________ Account_Quota____Value____________________________________ ASTLM 10 BIOLM 10 BYTLM 35,000 DIOLM 10 ENQLM 110 FILLM 10 MAXDETACH 0[1] PGFLQUO 40,000 PRCLM 2 TQELM 10 WSDEF 256 WSQUOTA 512 WSEXTENT 4,100[2] [1]LiveLink_applications_run_as_detached_processes._The___ MAXDETACH quota controls how many LiveLink processes a user can run at one time. [2]On a single-user workstation, the value of the system parameter WSEXTENT can be set equal to the value of WSMAX, for better performance. __________________________________________________________ 3-8 DECwrite Postinstallation Procedures 3.5 User Account Requirements 3.5.3 FileView Account Quotas If you want to run DECwrite from FileView, special tuning is required. FileView runs your task as a subprocess; therefore, your process quotas that are depleted by subprocess creation dictate how many FileView tasks you can run simultaneously. Before creating a new process, FileView checks these quotas and displays a warning in a dialog box if any are too low. The quota name is included in the message and can be one of the following: - ASTLM - BIOLM - BYTLM - FILLM - PGFLQUOTA - PRCLM - TQELM The most likely quotas to be consumed are your process limit (PRCLM) and buffered I/O byte count (BYTLM). To run a single task from FileView, your BYTLM quota should be a minimum of 10000, and an additional 5000 for each task you want to be able to run simultaneously. To be able to run five simultaneous tasks, your PRCLM quota must be at least 5, and your BYLTM quota must be at least 30000. Process creation can reduce remaining ASTCNT and BIOCNT by 3, and FILCNT by 2. PGFLQUOTA usage is highly dependent on the task. FileView checks these quotas when creating its subpro- cesses; however, some quotas, such as PGFLQUOTA, are not consumed until the application is running. Therefore, if several applications are invoked at once, it is possible that PGFLQUOTA will be exhausted once the applications start up, without the error being detected by FileView. In this case, the applications can crash when the quota is exceeded. DECwrite Postinstallation Procedures 3-9 3.5 User Account Requirements When process creation fails due to quota exhaustion, FileView marks the task as Pending in the Work in Progress box until one of the running tasks has completed. The Pending task then becomes Active. If you try to start an additional task after the quota message has been displayed, the task is marked Pending, and the Work in Progress box is displayed without a further warning message. 3.5.4 Modifying User Account Quotas User account quotas are stored in the file SYSUAF.DAT. Use the Authorize Utility to verify and change user account quotas. First, set your directory to SYS$SYSTEM, and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the AUTHORIZE prompt (UAF>), use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=10 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once you have finished making the changes, the users must log out and log in again for the new quotas to take effect. Note that to run DECwrite from FileView, you must have the PRCLM quota set to at least 1. For additional information about setting process quotas when running FileView, see the VMS Version 5.3-1 Release Notes. 3-10 DECwrite Postinstallation Procedures 3.5 User Account Requirements For more information about modifying account quotas, see the description of the Authorize Utility in the VMS system management and operations documentation. 3.6 Tuning Your System After you install DECwrite, you might want to adjust your system to enhance performance or lower the use of some system resources. Information about tuning your system is included in the VMS System Management, Volume 4, Performance manual. DECwrite performance, particularly with large documents is dependent on the amount of memory available, so workstations running DECwrite should be tuned with this in mind. The critical SYSGEN parameters and AUTHORIZE quotas that control how much memory is available to user processes are: - WSDEF - WSQUOTA - WSEXTENT - WSMAX Setting these quotas/parameters too low causes unnecessary paging/swapping. It is recommended that WSDEF and WSQUOTA be small, approximately 256 and 512, respectively. Since other DECwindows processes, such as the window manager, run using a user's quotas, it is usually best to start users with this small amount of memory and have them get more as they need it. WSEXTENT can be set equal to the SYSGEN parameter WSMAX. On a workstation, WSMAX can be set to a very large value. For example, on a 24 MB workstation, there are 49K pages of memory available. Approximately 6K of those pages are permanently allocated by the VMS system. The remaining 42K are available user processes. WSMAX can be set to 42K and AUTOGEN will recommend a slightly lower value (approximately 34K). With WSMAX and WSEXTENT set to 34K, a single userprocess, such as DECwrite, can get very large amounts of physical memory. This sort of tuning would be unrealistic on most timesharing/server machines, but it is not unrealistic for a single-user workstation. This tuning DECwrite Postinstallation Procedures 3-11 3.6 Tuning Your System will allow processes that need large amounts of memory to use the available memory with a minimum of paging. Note that these recommendations are dependent on DECwrite document size and document content. In addition, the available physical memory can vary widely, depending on the other applications running concurrently (the Session Manager, FileView, Calendar, Clock, and so forth). Finally, when working on very large documents (serveral hundred pages), make sure the system parameter VIRTUALPAGECNT and the user quota PGFLQUOTA are large enough. When opening a large document, use SHOW PROCESS to monitor a process's VIRTUALPAGECNT and use this number to estimate the required PGFLQUOTA for a given WSEXTENT. 3.7 Installation Verification Procedures The DECwrite Installation Verification Procedure (IVP) runs automatically at the end of the DECwrite installation procedure if you enter YES to that option during the installation. ________________________Note ________________________ Before you run the IVP for any language, ensure that you correctly set the language you will use. _____________________________________________________ If you did not enter YES, you may want to run the IVP later. If run later, the IVP needs two separate command procedures: $ @SYS$TEST:WRITE$IVP.COM ! DECwrite $ @SYS$TEST:Lxx$IVP.COM ! Bundled spell checking dictionary where xx is the two letter code for the lexicon included in your DECwrite kit. Table 3-4 lists language codes used for bundled lexicons: 3-12 DECwrite Postinstallation Procedures 3.7 Installation Verification Procedures Table_3-4_Lexicons_supplied_by_DECwrite_Kits______________ Language Bundled IVP Language DECwrite_Kit____Variant_______Lexicon_______Code__________ DECWRITE020 American American AE English English DECWRITE020 British British BE English English DECWRITEDA020 Danish American AE English DECWRITENE020 Dutch Dutch DU DECWRITESU020 Finnish None DECWRITEFR020 All French French FR LVs DECWRITEDE020 All German German GE LVs DECWRITEIT020 All Italian Italian IT LVs DECWRITENO020 Norwegian American AE English DECWRITEES020 Spanish Spanish SP DECWRITESE020___Swedish_______Swedish_______SW____________ You receive a message indicating whether the IVP succeeded or failed. 3.8 Invoking DECwrite You can run DECwrite from the Session Manager, from FileView, or from the command line (DCL). To run DECwrite, you must use the appropriate display device. See your SSA for the list of supported display devices. To invoke a DECwrite language variant: 1. On a Motif system, select the language corresponding to the DECwrite language variant you want to use, by choosing Language from the Session Manager Options menu and choosing the appropriate language from the Language Options dialog box. OR DECwrite Postinstallation Procedures 3-13 3.8 Invoking DECwrite On an XUI system, select the language by choosing Language from the Session Manager Customize menu and choosing the appropriate language from the Customize Language dialog box. 3-14 DECwrite Postinstallation Procedures 3.8 Invoking DECwrite 2. Run DECwrite using one of the methods described below. ________________________Note ________________________ If you use the Session Manager to switch languages, and you switch to a language for which there is no DECwrite language variant, DECwrite will not run. If the DECwrite American English product variant is installed, that will be run instead. _____________________________________________________ 3.8.1 Running DECwrite from the Session Manager For systems with DECwindows Motif for VMS Version 1.0, the installation automatically adds DECwrite as an item on the Session Manager Applications menu. If you install DECwrite on an XUI system, before you can invoke DECwrite from the Session Manager you must first customize your Session Manager's Applications menu to include a menu item for DECwrite. To add DECwrite to the Session Manager Applications menu: 1. From the Session Manager window, choose Customize Application Definitions. DECwrite displays the Customize Application Definitions dialog box. 2. Enter DECwrite in the Menu Item field. 3. Enter RUN SYS$SYSTEM:DECWRITE in the Menu Command field. 4. Click on the Add button, then click on OK. 5. Choose Customize Applications Menu. DECwrite displays the Customize Applications Menu dialog box. 6. Click on DECwrite in the Add list box. 7. Click on OK. 8. Choose Customize Save Current Settings. To invoke DECwrite using a particular language: 1. From the Session Manager, choose Customize Language. DECwrite Postinstallation Procedures 3-15 3.8 Invoking DECwrite 2. Choose the appropriate language from the Session Language list box. 3. Choose DECwrite from the Session Manager's Applications menu. 3-16 DECwrite Postinstallation Procedures 3.8 Invoking DECwrite ________________________Note ________________________ If you use a graphics terminal (VT1200, for example), you must first establish X-session on the node where DECwrite is installed; then, repeat the actions described in this section. _____________________________________________________ 3.8.2 Running DECwrite from FileView The installation adds DECwrite as an item on the FileView Applications menu. You should inform all users after the installation that DECwrite is available as an option on their FileView Applications menu. In FileView, if you doubleclick on a file with the extension .doc or .doc_style, DECwrite is automatically invoked to edit that document. For information about adjusting quotas to run DECwrite in FileView, see Section 3.5.2. 3.8.3 Running DECwrite from DCL To run DECwrite from the DCL command line, enter at the $ prompt: run sys$system:decwrite If you want to run DECwrite from your workstation in a language other than English, choose the appropriate language from the Session Language list on the Customize Language dialog box. You can also add a line to your login.com file to define a symbol to run DECwrite. For example: decwrite :== $ sys$system:decwrite A user could, after logging out and then logging back in or running login.com, enter at the DCL $ prompt: decwrite filename This would invoke DECwrite and open the named document if it already exists, or display the New Document Attributes dialog box if you have specified a new document. DECwrite Postinstallation Procedures 3-17 3.9 DECwrite Sample Documents 3.9 DECwrite Sample Documents During installation, DECwrite places sample files for each of its components in the following directories: o WRITE$EXAMPLES o WRITE$EXAMPLES_XX_YY, if a language variant has been installed. XX_YY refers to any non-American English language parameter codes shown in Table 3-1. o CHART$EXAMPLES The DECWRITE directory contains: o The documents used for the Getting Started exercises o Several demonstration documents o A sample equation for use with the DECwrite Equation Editor o Several sample Encapsulated PostScript files for use with the DECwrite Link to Picture option For a complete list of all the examples files, read the file readme.txt in the write$examples directory. For instructions on using the DECwrite Getting Started exercises and the online tutorial, refer to the DECwrite User's Guide. The CHART$EXAMPLES directory contains a sample chart file used in the DECchart Getting Started exercises. For instructions on the DECchart exercises, refer to the DECwrite User's Guide. 3.10 Compiling Fonts on Remote Workstations Your DECwrite software kit includes bitmap definition font files. If you want to display DECwrite on a system not specifically supported by your software kit, you will need to compile and install the fonts on the remote system. For example, if you have purchased DECwrite for ULTRIX and want to display DECwrite on a VMS workstation, follow the procedure in Section 3.10.1. 3-18 DECwrite Postinstallation Procedures 3.10 Compiling Fonts on Remote Workstations On the other hand, if you have purchased DECwrite for VMS and want to display DECwrite to a VMS system where DECwrite is not installed, simply perform a font only installation, as described in the installation procedure in Section 2.2 and illustrated by the example installation in Section A.2. After installing the DECwrite kit, the bitmap distribution format (.bdf) files can be found in the following directories: o On VMS systems: SYS$SYSROOT:[SYSHLP.EXAMPLES.DECWRITE.FONTS] o On ULTRIX systems: /var/X11/fonts/private/75dpi /var/X11/fonts/private/100dpi o On Sun SPARCstations: /usr/lib/DECpublishing/font/DECpublishing/75dpi /usr/lib/DECpublishing/font/DECpublishing/100dpi The following sections describe how to compile and install the DECwrite fonts on VMS, ULTRIX, and Sun SPARCstation displays, and on PCs using DECwindows. 3.10.1 Compiling and Installing Fonts on VMS Systems To compile and install the fonts on a VMS system: 1. From a system account, copy the files with a .bdf extension to a temporary working directory on the VMS workstation that will display DECwrite. 2. Compile each of the files using command in the following format: $ FONT fontfilename.BDF The FONT command creates a file with a .DECW$FONT file extension. 3. Copy all the 75 dpi font files into the 75 dpi font area using the following command: $ COPY/LOG *_75.DECW$FONT SYS$COMMON:[SYSFONT.DECW.USER_75DPI] DECwrite Postinstallation Procedures 3-19 3.10 Compiling Fonts on Remote Workstations 4. Copy all the 100 dpi font files into the 100 dpi font area using the following command: $ COPY/LOG *_100.DECW$FONT SYS$COMMON:[SYSFONT.DECW.USER_100DPI] 5. For systems running DECwindows Motif or VMS Version 5.4 or later, update the Server's font directory file using the following command: $ @SYS$UPDATE:DECW$MKFONTDIR 6. For all systems, restart the DECwindows server using the following command: $ @SYS$MANAGER:DECW$STARTUP RESTART 3.10.2 Compiling and Installing Fonts on ULTRIX Systems To compile and install the fonts on an ULTRIX workstation: 1. From a privileged account, copy the files with a .bdf extension to a temporary working directory on the RISC /ULTRIX or VAX/ULTRIX workstation that will display DECwrite. 2. Compile each font file using a command in the following format: /usr/bin/dxfc fontfilename.bdf >fontfilename.pcf 3. Copy all the 75 dpi font files into the 75 dpi font area using the following command: cp file.pcf /var/X11/fonts/private/75dpi/ 4. Copy all the 100 dpi font files into the 100 dpi font area using this command: cp file.pcf /var/X11/fonts/private/100dpi/ 5. Enter the following commands: mkfontdir /var/X11/fonts/private/75dpi mkfontdir /var/X11/fonts/private/100dpi 6. Restart the DECwindows server. 3-20 DECwrite Postinstallation Procedures 3.10 Compiling Fonts on Remote Workstations 3.10.3 Compiling and Installing Fonts on a Sun SPARCstation System To compile and install the fonts on a Sun SPARCstation workstation: 1. From a privileged account, copy the files with a .bdf extension to a temporary working directory on the SPARCstation workstation that will display DECwrite. For example, you might copy the files to the directories /home/myfonts/75dpi and /home/myfonts /100dpi. You should be running OpenWindows Version 2 before attempting to compile the fonts. 2. Process all the 75 dpi font files in the 75 dpi font area using a command in the following format: cd /home/myfonts/75dpi $OPENWINHOME/bin/convertfont -f 24 *.bdf -d . $OPENWINHOME/bin/bldfamily -f 24 3. Process all the 100 dpi font files in the 100 dpi font area using a command in the following format: cd /home/myfonts/100dpi $OPENWINHOME/bin/convertfont -f 24 *.bdf -d . $OPENWINHOME/bin/bldfamily -f 24 4. If you want the 75dpi fonts used, make the new directory known to the X server by adding commands in the following format to your ~/.xinitrc file: xset +fp /home/myfonts/75dpi xset fp rehash 5. Restart the X server by exiting from OpenWindows Version 2 and then rerunning the openwin shell script. 3.10.4 Compiling and Installing Fonts on a PC DECwindows System To compile and install the fonts on a PC DECwindows system: 1. Copy the .bdf files from the system where DECwrite is installed to a directory on your PC. The PC file names must be no more than eight characters followed by a three-character extension. For example, PRESENT_ BULLETS24_75.BDF could be named PB2475.BDF. Make sure DECwrite Postinstallation Procedures 3-21 3.10 Compiling Fonts on Remote Workstations the file names are unique so that existing files are not overwritten. 2. Compile the fonts. For a description of the compilation procedure, refer to the PATHWORKS - PC DECwindows User's Guide. 3.11 Determining and Reporting Problems If you encounter a problem while using DECwrite, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form, if the problem has to do with the DECwrite documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for warranty information. If you encounter a problem during the warranty period, report the problem as indicated above, or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. 3-22 DECwrite Postinstallation Procedures 4 ________________________________________________________________ Using the DECwrite Font Utility The DECwrite Font Utility allows you to add new fonts or delete existing fonts from the DECwrite font family menu. This chapter describes the following: o Procedures for copying and configuring font files prior to running the Font Utility o Procedures for adding fonts to DECwrite - All at once, without customization - Individually, without customization - Individually, customizing font weight and/or slant o Font Utility commands and descriptions o Troubleshooting procedures To use the Font Utility, you must be logged in as SYSTEM, or you must have privileges to copy files into protected areas and be able to restart the DECwindows Server. 4.1 Overview of Adding Fonts To install new fonts into DECwrite, you must: 1. Configure and place in the appropriate directories the screen font files, Adobe Font Metrics files (AFM files), and PostScript font outline program files (PostScript outline files) for each font. If you have installed a DECfonts Font kit on your system, the installation procedure completes this step. Proceed to Section 4.3. If you are installing third-party fonts, follow the directions given in Section 4.2 to copy and configure these files. Using the DECwrite Font Utility 4-1 4.1 Overview of Adding Fonts 2. Add the newly installed fonts to DECwrite by running the DECwrite Font Utility. Section 4.3 describes how to use the Font Utility to add new fonts. 4.2 Copying and Configuring Font Files Complete this section if you are installing third-party fonts into DECwrite. To copy and configure your new font files, complete the following procedure. 1. At the command line, enter font, followed by the name of each .bdf and .decw$bdf screen font file, to compile the files with the VMS Font Compiler. Use a separate command for each screen font file, in a format similar to the following: $ font filename-1 $ font filename-2 . . . $ font filename-n 2. Copy the resulting .decw$font files to the following target areas: .decw$font Target Area files 75dpi sys$common:[sysfont.decw.user_75dpi] 100dpi sys$common:[sysfont.decw.user_100dpi] 3. If you are running a version of DECwindows earlier than DECwindows Motif Version 1.0 or DECwindows Version 3.0, continue to step 4. If you are running DECwindows Motif Version 1.0 or later, or DECwindows Version 3.0 or later, update the font lookup file to point to both the 75 dpi and 100 dpi font areas by entering the following command: $ @sys$update:decw$mkfontdir 4-2 Using the DECwrite Font Utility 4.2 Copying and Configuring Font Files 4. Copy the new AFM files (extension .afm) and PostScript outline files (extension .ps) to the target directory, using the following logical: sys$ps_font_metrics: The files are placed in the directory sys$common:[sysfont.ps_font_metrics.user]. 5. Log out of your current windows session and log in again. If you are running XUI windows, you must restart your DECwindows Display Server with the following command: $ @sys$startup:decw$startup "restart" 4.3 Adding New Fonts to DECwrite The following sections describe several ways to use the Font Utility to add fonts to DECwrite. This summary discusses factors that can help you determine which method to use. Every font has a weight and a slant. The weight indicates the relative thickness of each character in the font. Slant indicates whether the font is upright or is italic. Each font used with DECwrite can have up to two weights and two slants. The Font Utility provides the following ways to add new fonts to DECwrite: o All at once, without any customization The Font Utility adds all fonts and determines their weight and slant. This method is appropriate for fonts with only one or two weights and one or two slants, or when the weight and slant choices are simple and the Font Utility can make the proper assignments by default. o Individually, using defaults The Font Utility provides default font weights and slants, on a font-by-font basis. This method is useful if you have installed many fonts, but want to add only a few to DECwrite. o Individually, with customization Using the DECwrite Font Utility 4-3 4.3 Adding New Fonts to DECwrite You choose weights and slants based on the choices available with the font, and the weights and slants the Font Utility recognizes. Use this method to add either DECfonts or third-party fonts with many choices of weight and slant. Because of the variety of font suppliers, there are a wide range of font characteristics. The Font Utility recognizes the following slants and weights: __________________________________________________________ Slants and Weights Recognized _____________by_the_Font_Utility__________________________ Slants____________________________________________________ Roman Italic Oblique Cursive Slanted Reverse Reverse Kursive Italic oblique __________________________________________________________ Weights___________________________________________________ Thin Light Demi bold Ultra bold Thinline Medium Semi bold Heavy Fineline Regular Bold Heavyface Ultra Book Bold 2 Black light Extra Nord Extra bold Ultra light Semilight___Demi__________________________________________ Examples in the following sections use DECfonts Version 1.0 as the installed fonts. To add these fonts, you must first install them on your system, then restart your DECwindows display server before performing any of these procedures. 4-4 Using the DECwrite Font Utility 4.3 Adding New Fonts to DECwrite 4.3.1 Adding Fonts All at Once, Without Customization Adding all fonts at once is the simplest and fastest way to add new fonts to DECwrite. The Font Utility adds all the fonts you have installed on your system and, where applicable, chooses two defaults each, for weight and slant. This allows you to complete the process from the command line level without entering any further commands through the Font Utility. ________________________Note ________________________ This procedure creates a backup copy of your existing write_fonts.ini, called write$fonts.ini_ backup. _____________________________________________________ To add new fonts to DECwrite all at once, without any customization, run the Font Utility by entering commands in the following format: $ set def sys$common:[syslib] $ set display/create/node=nodename $ wfont :== $write$fontutil $ wfont -n write$fonts.ini For nodename, enter the node name of your workstation. The Font Utility displays messages on your screen in the following format, then returns you to the command line: Font Utility V2.0 Gathering screen and printer font information from system - please wait... Adding all the following fonts: Helvetica narrow ITC Bookman ITC Zapf Chancery ITC Zapf Dingbats Palatino All fonts successfully added Saving to file write$fonts.ini $ Using the DECwrite Font Utility 4-5 4.3 Adding New Fonts to DECwrite 4.3.2 Adding Fonts Individually The procedures in the next two sections describe the simplest ways to add fonts individually. Both allow you to run the Font Utility interactively. While running the Font Utility, you have access to all the Font Utility commands described in Section 4.4. These commands give you additional flexibilty in working with fonts. For example: o Before adding fonts, you can use the show command to confirm that font families have been installed and are available to be added to the DECwrite font menu. o Without leaving the Font Utility, you can use both the add command (described in Section 4.3.2.1) to add fonts with default weight and slant, and the add confirm command (described in Section 4.3.2.2) to customize weight and slant. o You can experiment with new fonts without overwriting the default file write$fonts.ini by saving changes to a new output file name when you exit from the Font Utility, or by specifying an output file name other than write$fonts.ini when you start the Font Utility. o You can also hide fonts (so that they are usable but do not appear on the DECwrite font menu), reveal hidden fonts, and rename fonts. 4.3.2.1 Adding Fonts Individually, Using Defaults To add fonts one at a time using the defaults supplied with the font: 1. Enter the following commands to start the Font Utility: $ set def sys$common:[syslib] $ set display/create/node=nodename $ wfont :== $write$fontutil $ wfont write$fonts.ini For nodename, enter the node name of your workstation. The Font Utility starts up, then prompts you to enter a command. 2. Enter add, followed by the name of the font you are adding, in quotation marks (" "). 4-6 Using the DECwrite Font Utility 4.3 Adding New Fonts to DECwrite For example: Enter command> add "Palatino" The Font Utility reports that the font has been added, then prompts you again. 3. Enter exit. The Font Utility asks if you want to write out the input file write$fonts.ini. 4. Enter y. The Font Utility confirms the creation of a new version of the file write$fonts.ini, then returns you to the command line. 4.3.2.2 Adding Fonts Individually, and Customizing You may want to customize how font weight and slant are determined if: o The font has more than two choices available for weight and slant o You want a bold or italic font to be the normal font when using DECwrite To add a font and customize it using the Font Utility: 1. Enter: $ set def sys$common:[syslib] $ set display/create/node=nodename $ wfont :== $write$fontutil $ wfont write$fonts.ini For nodename, enter the node name of your workstation. The Font Utililty starts up, then prompts you to enter a command. 2. Enter add confirm, followed by the name of the font you want to add, in quotation marks (" "). For example: Enter command> add confirm "Palatino" Using the DECwrite Font Utility 4-7 4.3 Adding New Fonts to DECwrite The Font Utility displays the choices that are available for the font weight, and the defaults it has chosen, followed by a prompt asking if the choices are correct. 3. Do one of the following: o Enter y to accept the defaults, and then proceed to step 5. o Enter n to choose new defaults, and then continue at step 4. o Enter a to leave the Font Utility without adding the font. 4. To specify new font weight settings: a. Enter the number corresponding to the desired Normal font weight, or enter no number to refrain from choosing a font for the normal setting. b. Enter the number corresponding to the desired Bold font weight, or enter no number. c. Answer y at the prompt when you are sure your choices are correct. 5. Based on the choices displayed for the font slant, do one of the following: o Enter y to accept the defaults. o Enter n to choose new defaults, and then choose the desired slants. o Enter a to leave the Font Utility without adding the font. After you accept the defaults or choose a new slant, the Font Utility confirms that the font has been added. 6. Enter exit to leave the Font Utility. 7. Enter y to confirm that you want to overwrite the file write$fonts.ini. A new version of write$fonts.ini is written and you are returned to the command line. 4-8 Using the DECwrite Font Utility 4.3 Adding New Fonts to DECwrite The following example shows how the confirm option is used to customize font weights for a hypothetical font "Martian Miter": $ wfont write$fonts.ini Font Utility V2.0 Gathering screen and printer font information from system - please wait... Enter command> add confirm "Martian Miter" Verifying attributes for Font "Martian Miter" FONT "WEIGHT" SELECTION The following font "weight" choices are available: (0) none (1) light (2) medium (3) bold (4) extra bold (5) ultra bold For the font family ITC Bookman, the font utility chose: - "light" as Normal font weight - "medium" as Bold font weight Are the above choices for font weight correct [yes/no/abandon]: n You may pick any two of the available font "weight" choices: (0) none (1) light (2) medium (3) bold (4) extra bold (5) ultra bold Enter font "Normal" weight number from list above [0 to 5]: 1 Enter font "Bold" weight number from list above [0 to 5]: 4 For the font family Martian Miter, you chose: - "light" as Normal font weight - "extra bold" as Bold font weight Are the above choices for font weight correct [yes/no/abandon]: y Using the DECwrite Font Utility 4-9 4.3 Adding New Fonts to DECwrite FONT "SLANT" SELECTION The following font "slant" choices are available: (0) none (1) roman (2) italic (3) reverse italic For the font family Martian Miter, the font utility chose: - "roman" as Upright font slant - "italic" as Italic font slant Are the above choices for font slant correct [yes/no/abandon]: y Font "Martian Miter" added. Enter command> exit Do you really want to overwrite write$fonts.ini (y or n) [n]? y Saving to file write$fonts.ini $ 4.4 Font Utility Commands and Descriptions The DECwrite Font Utility allows you to add and manage fonts not shipped with DECwrite. Table 4-1 lists all of the Font Utility's commands and describes how you can use them to perform font management tasks. Font Utility commands use two font lists. The New list contains font families that can be added to the DECwrite menu. These are fonts you have installed on your system, but have not yet added to DECwrite. Fonts you add to DECwrite using the Font Utility are removed from this list. Fonts you delete using the Font Utility are returned to the New list and can be added again later. When a font is removed from the New list, it is placed on the Menu list. This list contains font families that have already been added to the DECwrite menu. The Font Utility commands are not case sensitive. 4-10 Using the DECwrite Font Utility 4.4 Font Utility Commands and Descriptions Table_4-1_DECwrite_Font_Utility_Commands__________________ Command___Format,_Effects,_and_Descriptions_______________ add add [confirm] "fontname" If you specify a fontname, the add command places the fontname on the Menu list, and removes it from the New list. If you specify the confirm option, the Font Utility displays all the weight and slant choices for the font and lets you confirm default assignments, or pick new defaults. If you do not specify the fontname, the add command prompts you for it with the prompt Family name:. If you press the Return key without specifying a fontname, the add command changes nothing. add new add new [confirm] Adds all the new fonts in the New list to the Menu list. If you specify the confirm option, the Font Utility confirms the weight and slant assignments as they are being added. If you have many fonts and do not need to customize their font and weight assignments, omit the confirm option to reduce the time required to add fonts. (continued on next page) Using the DECwrite Font Utility 4-11 4.4 Font Utility Commands and Descriptions Table_4-1_(Cont.)_DECwrite_Font_Utility_Commands__________ Command___Format,_Effects,_and_Descriptions_______________ hide hide "fontname" Hides the fontname from the Menu list. Hidden or invisible fonts are available to existing DECwrite files read in, but are not visible on the DECwrite Font Family Menu. This feature is useful for hiding the DECmath fonts from the menu, or for permitting a user to exclude a standard DECwrite font without deleting it. If you do not specify the fontname, the hide command prompts for it with Family name:. If you press the Return key, the hide command changes nothing. You can reverse the effects of the hide command by using the reveal command to make a hidden font visible on the DECwrite font menu. delete delete "fontname" Deletes the indicated fontname from the Menu list, adding it to the New list. If you do not specify the fontname, the delete command prompts you for it with Family name:. If you press the Return key, the delete command changes nothing. (continued on next page) 4-12 Using the DECwrite Font Utility 4.4 Font Utility Commands and Descriptions Table_4-1_(Cont.)_DECwrite_Font_Utility_Commands__________ Command___Format,_Effects,_and_Descriptions_______________ exit exit [outfilename] Exits the Font Utility and saves the changes you have made. Use the exit command with the outfilename option to specify a file name where changes should be saved, regardless of how you entered the startup command. If you specified an outfilename when you started the Font Utility, the exit command saves your changes to that file name. In the following startup command example, changes would be saved to the file newfonts.ini: $ wfont write$fonts.ini newfonts.ini If you do not specify an outfilename when you start the Font Utility, the exit command saves your changes to the infilename you specify in the startup command. In the following example, changes would be saved to the file write$fonts.ini: $ wfont write$fonts.ini In all cases, the Font Utility verifies that you want to write to the indicated file. If you respond with yes, you exit the Font Utility and your changes are saved. If you respond with no, no action is taken and you can continue to use the Font Utility. If you respond yes to save changes and the file name in the startup command is write$fonts.ini, the Font Utility saves the previous version of write$fonts.ini to write$fonts.ini_backup. (continued on next page) Using the DECwrite Font Utility 4-13 4.4 Font Utility Commands and Descriptions Table_4-1_(Cont.)_DECwrite_Font_Utility_Commands__________ Command___Format,_Effects,_and_Descriptions_______________ quit quit Terminates the session without saving changes. If you made changes to the infilename, the font utility prompts you to confirm that you want to quit without saving your changes. If you answer yes, the font utility's session terminates without saving any changes. If you answer no, the utility saves no changes and the font utility continues running. If you have made no changes to the infilename, the font utility session ends without confirma- tion. rename rename "oldfontname" "newfontname" Renames the indicated font family to a new font name. The names you change with the rename command are those displayed on the DECwrite Font Family Menu. Renaming a font does not change file names or affect the internal pointers that DECwrite uses to identify fonts. If you do not specify oldfontname, the Font Utility prompts From:. If you do not specify newfontname, the Font Utility prompts To:. If you press the Return key at either prompt without entering a font name, no change is made, and you can continue to use the Font Utility. reveal reveal "fontname" Makes the indicated hidden fontname visible on the DECwrite font menu. See the hide command for details about hidden fonts. If you do not specify the fontname, the reveal command prompts you for it with Family name:. If you press the Return key without specifying a fontname, the utility displays nothing. (continued on next page) 4-14 Using the DECwrite Font Utility 4.4 Font Utility Commands and Descriptions Table_4-1_(Cont.)_DECwrite_Font_Utility_Commands__________ Command___Format,_Effects,_and_Descriptions_______________ show show [full] [new|menu] "fontname" Displays the indicated font and optionally its corresponding screen font name, PostScript outline file name, and AFM file name. If you do not specify a fontname or an option, the show command defaults to show new, showing all entries in the New list. o full Displays additional information for each entry, consisting of screen font name, PostScript outline file name, and AFM file name o new Displays all entries in the New list, or displays a specific entry if you specify a fontname o menu Displays all entries in the Menu list, or displays a specific entry if you specify a fontname o "fontname" Displays the indicated font family in either the New or Menu list __________________________________________________________ 4.4.1 Changing Characteristics of Added Fonts After you add a font to DECwrite, you may want to change some of its characteristics, such as weights, slants, or point sizes. Revisions of point sizes involve adding new screen font files, while changing weight or slant requires changing the Font Utility pointers to AFM and PostScript outline files. Using the DECwrite Font Utility 4-15 4.4 Font Utility Commands and Descriptions To make either change, you must delete the font from the DECwrite font menu using the Font Utility, make the changes to the files, and then add the font back to the menu. To revise fonts you have added to the DECwrite font menu: 1. Run the Font Utility, as described in Section 4.3.2.1. 2. Enter delete, followed by the font name in quotation marks (" "). 3. Enter exit to exit from the Font Utility. 4. Install the files providing the new weights, slants, or point sizes, as described in Section 4.2. 5. Run the Font Utility again. 6. To add the font back to the DECwrite font menu, do one of the following: o If you have added only new point sizes, enter add, followed by the font name in quotation marks. The font, including the new point sizes, is added to the DECwrite menu, with the same slants and weights it had previously. o If you have added new slants and weights, enter add confirm, followed by the font name in quotation marks. The Font Utility allows you to specify new fonts and weights, as described in Section 4.3.2.2. 7. Enter exit to exit from the Font Utility. 4.5 Revealing a Hidden Font Some fonts on your system may be hidden. Hidden fonts are available to existing DECwrite files read in, but are not visible on the DECwrite Font Family Menu. To make a hidden font visible on the DECwrite Font Family menu, use the reveal command. The following examples show how to reveal the hidden font Present Bullets. 4-16 Using the DECwrite Font Utility 4.5 Revealing a Hidden Font 1. Enter the following commands to start the Font Utility: $ set def sys$common:[syslib] $ set display/create/node=nodename $ wfont :== $write$fontutil $ wfont write$fonts.ini For nodename, enter the node name of your workstation. The Font Utility starts up, then prompts you to enter a command. 2. Enter reveal, followed by the name of the font you are revealing, in quotation marks (" "). For example: Enter command> reveal "Present Bullets" The Font Utility reports that the font has been revealed, then prompts you again. 3. Enter exit. The Font Utility asks if you want to write out the input file write$fonts.ini. 4. Enter y. The Font Utility confirms the creation of a new version of the file write$fonts.ini, then returns you to the command line. 4.6 Troubleshooting Font Problems This section describes problems you may encounter after adding fonts, or when using the Font Utility to manage your fonts. Table 4-2 lists possible problems and summarizes steps you can take to address them. The sections following the table provide detailed descriptions of problem recovery procedures. Using the DECwrite Font Utility 4-17 4.6 Troubleshooting Font Problems Table_4-2_Troubleshooting_Summary_________________________ Problem Third-Party or Description______DECfonts_Fonts______User-Defined_Fonts___ Cannot connect Set the display Same solution. to DECwindows variable. server Check security access. Check that a session is logged in on your workstation. __________________________________________________________ Font Utility Log out of your Check system screen show new or windows session font directories. show menu and log in again. Check AFM and commands do If you are running PostScript outline not list all XUI windows, you file directories. installed fonts must restart the Compare screen font DECwindows Display and AFM files. Server. __________________________________________________________ Wrong slant or Run Font Utility. Same solution. weight chosen Delete font, then exit. Run Font Utility again. Add font using confirm option. __________________________________________________________ (continued on next page) 4-18 Using the DECwrite Font Utility 4.6 Troubleshooting Font Problems Table_4-2_(Cont.)_Troubleshooting_Summary_________________ Problem Third-Party or Description______DECfonts_Fonts______User-Defined_Fonts___ Cannot see Check that Same solution. added fonts all fonts are when running installed on DECwrite workstation to which you are displaying. Restart worksta- tion's Display Server. __________________________________________________________ Cannot print Check that Same solution. document PostScript In addition, compare containing outline files AFM file data and new font from are in required PostScript outline DECwrite_________directory.__________file_data.___________ 4.6.1 Setting the Display Variable Because the Font Utility uses DECwindows to perform screen font lookups on your workstation, it must connect to your workstation as DECwrite does. To set the display variable to connect to your worksta- tion, issue a command in the following format: $ set display/create/node=nodename For nodename, enter the node name of your workstation. 4.6.2 Checking Security Access If you are running the Font Utility on a cluster and pointing back to a workstation with your display variable, then you should ensure that your workstation gives you access. To check your security access: 1. From the DECwindows Session Manager, choose Options (or Customize on XUI Windows) Security. Using the DECwrite Font Utility 4-19 4.6 Troubleshooting Font Problems 2. If the node and account you are using on the cluster are not in the Security list on your workstation, add them, and click on OK. 3. Choose Options (or Customize) Save Current Settings. 4.6.3 Checking Session Login If you are running the Font Utility on a cluster or a diskless server and your display is pointing back to a workstation, you must also be logged in to that workstation from the display window on that workstation. 4.6.4 Restarting Your Session or DECwindows Display Server If you are running under the MOTIF window manager, after you install fonts on your workstation, you must log out of your window session and then log in again. If you are running under the XUI window manager, after you install fonts on your workstation, you must restart your DECwindows display server to allow DECwindows to see your new fonts. Restart your display server by issuing the following command: $ @sys$startup:decw$startup "RESTART" 4.6.5 Checking the Location of Screen Font, AFM, and PostScript Files If fonts you have installed and added using the Font Utility are not listed when you use the Font Utility show new or show menu commands, they may have been installed in the wrong directories. Table 4-3 gives the correct directory locations for these files. 4-20 Using the DECwrite Font Utility 4.6 Troubleshooting Font Problems Table_4-3_Font_File_Locations_____________________________ Font_Files_________________Directory_Location_____________ Screen font files sys$common:[sysfont.decw.user_ 75dpi] sys$common:[sysfont.decw.user_ 100dpi] AFM and PostScript sys$common:[sysfont.ps_font_ outline_files______________metrics.user]__________________ For instructions on copying the files to the proper directories, see Section 4.2. Section 4.2 also describes the procedure you must follow to update the font lookup file if you are using DECwindows Version 3.0 or higher. 4.6.6 Comparing Screen Font, AFM, and PostScript Outline Files When you install third-party or user-defined fonts, data in the AFM files may be omitted or may not agree with corresponding data in the Screen Font and PostScript files. If this data does not match, the Font Utility cannot see your newly installed fonts. To determine whether the data matches, you need to do the following: 1. Display the screen font data. 2. Edit the relevant AFM files to see, and possibly correct, data fields. 3. Edit the relevant PostScript files to see, and possibly correct, data fields. 4.6.6.1 Displaying Screen Font Attributes To display the screen font attributes: 1. Run the DECwindows Notepad application. 2. Choose Fonts from the Customize menu. The Font Attributes dialog box is displayed. 3. In the Family list box, click on the name of your new font. Using the DECwrite Font Utility 4-21 4.6 Troubleshooting Font Problems The available sizes for that font are displayed in the Size list box. 4-22 Using the DECwrite Font Utility 4.6 Troubleshooting Font Problems 4. Click on any size. The screen font attributes weight, slant, width, spacing, and character set are displayed. These, and the Font Family name, are the attributes you need to compare. 4.6.6.2 Editing AFM and PostScript Outline Files For new fonts to appear in the Font Utility's New list, certain strings within the AFM and PostScript outline files, and corresponding attributes of the screen fonts, must match. If you cannot list the added fonts when you use the Font Utility show new or show menu commands, or if you cannot print a document containing a new font, you must check the data in the AFM and PostScript outline files that correspond to the weight and slant you have chosen. Note that although installing a font copies AFM and PostScript Outline files for each possible combination of weights and slants, you need check only those files required to produce the weights and slants assigned when the font is added to DECwrite (a maximum of four files). Table 4-4 shows the AFM, PostScript, and screen font attributes that must match. An example is given after each set. Except where noted, the match must be content specific, but not case sensitive. ________________________Note ________________________ If you are installing the Bookman font shipped with the DECfonts Version 1.0 kit, you should only read and not modify these files. _____________________________________________________ Table_4-4_AFM,_PostScript,_and_Screen_Font_Comparisons____ AFM_File_String_____________Screen_Font_Attributes________ FullName Family Weight Slant (continued on next page) Using the DECwrite Font Utility 4-23 4.6 Troubleshooting Font Problems Table 4-4 (Cont.) AFM, PostScript, and Screen Font __________________Comparisons_____________________________ AFM_File_String_____________Screen_Font_Attributes________ FullName ITC Bookman ITC Light Italic Light Italic Bookman FamilyName Family FamilyName ITC Bookman ITC Bookman Weight Weight Weight Light Light IsFixedPitch Spacing IsFixedPitch false Proportional IsFixedPitch true Monospaced EncodingScheme Char Set EncodingScheme AdobeStandardAdobe-ng FontSpecific EncodingScheme FontSpecific DEC- FONTSPECIFIC __________________________________________________________ PostScript Outline File AFM_File_String_____________Attributes____________________ FontName (case sensitive) FontName (case sensitive) FontName Bookman- FontName Bookman- LightItalic LightItalic FontName PostScript outline file name FontName Bookman- bookman_lightitalic.ps LightItalic_______________________________________________ The screen font attribute Char Set is composed of a registry string and an encoding string. In the second EncodingScheme example in Table 4-4, the registry string is DEC- and the encoding string is FONTSPECIFIC. In some cases, the registry string for the screen font is not present in the AFM EncodingScheme string, as illustrated by the example. 4-24 Using the DECwrite Font Utility 4.6 Troubleshooting Font Problems The following encoding schemes are recognized by the Font Utility: AdobeStandardEncodidec.dtscs.1990-jisx0208.1983-1 2 AppleSpecific fontspecific jisx0208- kanji11 decisolatin1 gb2312.1980-1 jisx0201- romankana dec.cns11643.1986- isolatinhebrew ksc5601.1987-1 2 iso8859-n, where n is a number 1 through 8, corresponding to ISO Latin 1 through 8. To view and edit the attributes of an AFM or PostScript outline file: 1. Set default to sys$common:[sysfont.ps_font_metrics.user]. 2. Edit the appropriate AFM or PostScript outline file. 3. Locate and compare the strings listed in Table 4-4. Most matches must be between AFM strings and screen font attributes. An additional match is necessary between the FontName strings in the AFM and PostScript outline files, and between the AFM FontName string and the name of the PostScript outline file. 4. Edit the files as follows to ensure that the necessary matches are made. o If AFM strings do not match the corresponding screen font attributes, edit the appropriate AFM strings. o If the AFM FontName string does not match the PostScript outline file FontName string, edit the PostScript outline file. o If the AFM FontName string does not match the name of the PostScript outline file, rename the PostScript file to create the match. Additional information is available on AFM files from Adobe Systems, Inc. in the Adobe Font Metrics Files Specification, Version 3.0. Using the DECwrite Font Utility 4-25 4.6 Troubleshooting Font Problems Additional information on screen fonts is available in X Window System, second edition by Robert W. Scheifler & James Gettys 1990, Digital Press. (See Part IV. X Logical Font Descriptions, pp 558-572.) 4-26 Using the DECwrite Font Utility A ________________________________________________________________ Printouts from Sample DECwrite Installations This appendix contains printouts of typical DECwrite installation procedures. These procedures show: o A full DECwrite installation o A font only installation To perform a successful installation, you must: 1. Prepare your system by completing the procedure in Chapter 1. 2. Install DECwrite by completing the installation procedure described in Chapter 2. 3. Perform any needed postinstallation procedures described in Chapter 3. A.1 Full DECwrite Installation This sample installation printout shows the user responses and system messages on a VMS Version 5.4 system where DECwindows Motif for VMS Version 1.0 and all the appropriate licenses have been installed. $ @sys$update:vmsinstal decwrite USER7:[CDE.KITS.CBL6] VAX/VMS Software Product Installation Procedure V5.4-2 It is 26-AUG-1991 at 15:07. Printouts from Sample DECwrite Installations A-1 A.1 Full DECwrite Installation Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$TE_0104 SMITH DECterm 2-0 gerund Mail DECW$TE_011E DECterm 3-1 DECterm 4-1 Notes1 gerund BR * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? yes The following products will be processed: DECWRITE V2.0 Beginning installation of DECWRITE V2.0 at 15:07 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, The product's release notes have been moved to SYS$HELP. DECwrite V2.0 Installation Procedure Programs and databases for the Usage Alert, Electronic Thesaurus licensed from Houghton Mifflin. Copyright (c) 1985, 1987 by Houghton Mifflin Company. International CorrectSpell (c) 1987, 1988 by Houghton Mifflin. All rights reserved. US Pat. Nos. 4,508,241, 4,730,269, and 4,771,041. Canadian Pat. No. 1,203,916. Thesaurus U.S. Pat. No. 4,724,523. Portions licensed to Digital Equipment Corporation, Maynard, Massachusetts Copyright (c) Frame Technology Corporation 1989. All rights reserved. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... You can install the DECwrite kit completely or just the additional screen fonts used by DECwrite and the: DECwrite Equation Editor. If you are installing this kit for use on a workstation, or on a VAXcluster that includes workstations, then you should install the entire kit. This requires 60000 blocks. A-2 Printouts from Sample DECwrite Installations A.1 Full DECwrite Installation If you are installing this kit on a workstation that will only run DECwrite from a remote system, then only the screen font files are needed. This requires 2200 blocks. * Do you want to install the entire kit [YES]? This kit contains the user interface for both DECwrite/American English and DECwrite/British English. You should install the appropriate user interface according the type of DECwrite license you have purchased. Choose one of the following: 1) DECwrite/American English user interface 2) DECwrite/British English user interface * Enter choice [1]: ? DECwrite is translated into many languages. These translated version are called language variants. This kit includes two DECwrite language variants: American English and British English. A language variant determines the defaults for attributes such as: - the language in which the menus and dialog boxes are presented. - the Primary Language and Paper Size for new documents. DECwrite performs spell checking, hyphenation, and sorting operations according to the primary language. - the style files to use. * Enter choice [1]: Installing DECwrite/American English... You have DECwindows Motif installed on your system. You can choose to install DECwrite with a Motif or XUI graphic user interface (GUI). Note: You cannot install both DECwrite/Motif and DECwrite/XUI on a single system. Choose one of the following GUIs: 1) DECwrite/Motif 2) DECwrite/XUI * Enter choice [1]: ? DECwrite V2.0 may be installed with one of two graphic user interfaces (GUI): - OSF/Motif - X User Interface (XUI) Printouts from Sample DECwrite Installations A-3 A.1 Full DECwrite Installation The XUI interface is the same as that used with earlier versions of DECwrite. The Motif GUI is new for DECwrite V2.0 The Motif GUI requires that DECwindows Motif for VMS V1.0 (or later) be installed on your system. * Enter choice [1]: Installing DECwrite/Motif... This kit contains an optional clipart library composed of Encapsulated PostScript pictures, DDIF pictures, and DDIF images. It's total size is 9915 blocks. * Do you want to install the clip art library [YES]? Specify a device and directory on which to install the clip art library * Device and directory [sys$sysdevice:[clipart]]: You have chosen the device and directory SYS$SYSDEVICE:[CLIPART] * Is this correct [YES]? ************************************************************* Note: This installation will replace the DECwrite supplied style files in CDA$LIBRARY. If you have made modifications to these files, make backup copies before continuing. For example: $ backup/log cda$library:wr_*.doc_style style_files.bck/sav ************************************************************* * Do you want to continue [YES]? This kit requires DECchart V1.5-5 or later. ************************************************************* DECchart V1.5-5 will be installed since it does not exist on your system. ************************************************************* This kit requires the DECwrite Equation Editor V1.1-2 or later. The DECwrite Equation Editor V1.1-2 will be installed since it does not exist on your system. The DECwrite spell check lexicons will be installed in the directory SYS$SYSDEVICE:[LCI.LEXICONS] by default. You may optionally install the files on a device other than the system disk. A-4 Printouts from Sample DECwrite Installations A.1 Full DECwrite Installation * Specify a device on which to install the spell check lexicons [SYS$SYSDEVICE:]: You have chosen the device SYS$SYSDEVICE: * Is this correct [YES]? Checking/registering INTL-LEXICON-AMERICAN Product Authorization Key... * Do you want to run the IVP after the installation [YES]? %VMSINSTAL-W-NODISPLAY, Workstation display not defined Enter the node name of the workstation on which to display the IVP or press Return to continue and not run the IVP * Node name: gerund The language in the Language dialog box on the Session Manager's Customize/Options menu must be set to American English in order to run the IVP. Ensure the language is set accordingly before continuing. * Press Return when ready to continue: * Do you want to purge files replaced by this installation [YES]? To complete the installation on a standalone VAX 11/780 will take approximately: 135 minutes to install 5 minutes to run the IVP All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %VMSINSTAL-I-RESTORE, Restoring product save set G ... %VMSINSTAL-I-RESTORE, Restoring product save set H ... %VMSINSTAL-I-RESTORE, Restoring product save set J ... %VMSINSTAL-I-RESTORE, Restoring product save set L ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE]. The on-line demonstration document, tutorial.doc and the documents used in the Getting Started exercises are in: VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE] Printouts from Sample DECwrite Installations A-5 A.1 Full DECwrite Installation %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECWRITE.FONTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.DECWRITE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory GERUND$DKB0:[CLIPART]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[EPS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[ARROWS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[BUILDING]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[COMMUNIC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[ENERGY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[SPORTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[FIGURES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[FINANCE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[GOVERNMT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[SCIENCE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BLDG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BORDR]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_BUSNS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_COMM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_DOM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_FIN]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_FLAGS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_MISC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_NATUR]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_PEOPL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SCI]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SPORT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_SYMBL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_TOONS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_TRANS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_USMAP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory WRITE$CLIPART:[PR_WDMAP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[LCI.LEXICONS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.CHART$IVP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECCHART]. The following commands must be added to the system startup command file SYS$MANAGER:SYSTARTUP_V5.COM for all nodes that will be running DECwrite: @sys$startup:write$startup @sys$manager:decw$starti18n @sys$startup:lci$startup.com ! American-English lexicon A-6 Printouts from Sample DECwrite Installations A.1 Full DECwrite Installation If you are installing this kit on a workstation, you should restart DECwindows after the installation has completed: @sys$startup:decw$startup restart %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %VMSINSTAL-I-FONTS, Updating font directories 153 fonts loaded Creating sys$common:[sysfont.decw.user_75dpi]DECW$FONT_DIRECTORY.DAT 9 fonts loaded Creating sys$common:[sysfont.decw.user_100dpi]DECW$FONT_DIRECTORY.DAT %VMSINSTAL-I-RUNIVP, Executing installation verification procedure(s) Executing IVP for: DECwrite V2.0 The IVP edits a sample document. If the document looks the same as the illustration in the installation guide, then the installation has been successful. After the document window appears, click the mouse in the window to assign input focus, and type Alt/Q (hold down the Compose Character or "Alt" key and press Q) to exit DECwrite and complete the DECwrite portion of the IVP. Note that when executing this IVP for a particular DECwrite language variant, make sure to set the appropriate language in the Language dialog box on the Session Manager's Customize/Options menu. See the installation guide for details. Set your language now before continuing with the IVP. Press return when ready: Starting DECwrite.... ************************************* DECwrite V2.0 IVP COMPLETED SUCCESSFULLY ************************************* IVP completed for: DECwrite V2.0 Executing IVP for: International Lexicon/American for VMS V1.0 ******************************************** International Lexicon/American for VMS V1.0 Printouts from Sample DECwrite Installations A-7 A.1 Full DECwrite Installation IVP COMPLETED SUCCESSFULLY ********************************************* IVP completed for: International Lexicon/American for VMS V1.0 Installation of DECWRITE V2.0 completed at 16:33 VMSINSTAL procedure done at 16:34 $ log SMITH logged out at 26-AUG-1991 16:39:01.33 A.2 Font Only DECwrite Installation This sample installation printout shows the user responses and system messages when all the appropriate licenses have been installed, and the user chooses a font only installation. $ @vmsinstal decwrite020 mua0: options s VAX/VMS Software Product Installation Procedure V5.3 It is 19-JUL-1991 at 16:20. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: SMITH JONES DECterm 2 Mail DECterm 3 Notes * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DECWRITE V2.0 Beginning installation of DECWRITE V2.0 at 16:20 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. A-8 Printouts from Sample DECwrite Installations A.2 Font Only DECwrite Installation DECwrite V2.0 Installation Procedure Programs and databases for the Usage Alert, Electronic Thesaurus licensed from Houghton Mifflin. Copyright (c) 1985, 1987 by Houghton Mifflin Company. International CorrectSpell (c) 1987, 1988 by Houghton Mifflin. All rights reserved. US Pat. Nos. 4,508,241, 4,730,269, and 4,771,041. Canadian Pat. No. 1,203,916. Thesaurus U.S. Pat. No. 4,724,523. Portions licensed to Digital Equipment Corporation, Maynard, Massachusetts Copyright (c) Frame Technology Corporation 1989. All rights reserved. %VMSINSTAL-I-RESTORE, Restoring product save set B ... You can install the DECwrite kit completely or just the video fonts required to use the DECwrite Equation Editor. If you are installing this kit for use on a workstation, or on a VAXcluster that includes workstations, then you should install the entire kit. This requires 60000 blocks. If you are installing this kit on a workstation that will only run DECwrite from a remote system, then only the video font files are needed. This requires 2200 blocks. * Do you want to install the entire kit [YES]? no * Do you want to install only the video fonts [YES]? Installing only the DECwrite Equation Editor fonts... * Do you want to purge files replaced by this installation [YES]? To complete the installation on a standalone VAX 11/780 will take approximately: 10 minutes to install All required questions have been asked. You can terminate the installation procedure at this time. * Do you want to continue the installation [YES]? %VMSINSTAL-I-RESTORE, Restoring product save set I ... %VMSINSTAL-I-RESTORE, Restoring product save set J ... If you are installing this kit on a workstation, you should restart DECwindows after the installation has completed: @sys$startup:decw$startup restart Printouts from Sample DECwrite Installations A-9 A.2 Font Only DECwrite Installation %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of DECWRITE V2.0 completed at 16:33 VMSINSTAL procedure done at 16:43 $ A-10 Printouts from Sample DECwrite Installations ________________________________________________________________ Index A Compiling ___________________________ font files, 4-2 Add command Confirm option of Font Utility, 4-6, of Font Utility, 4-6, 4-11 4-11 example, 4-6 example, 4-7 Add new command Copying of Font Utility, 4-11 font files, 4-2 Adobe Font Metric files see also AFM files D__________________________ AFM files DECwrite comparing to screen font documentation, viii files, 4-21 running from DCL, 3-17 copying, 4-3 running from FileView, editing, 4-23 3-17 used with Font Utility, DECwrite startup file 4-1 editing, 3-4 WRITE$STARTUP.COM, 3-4 B__________________________ Delete command Backing up the system disk, of Font Utility, 4-12 1-9 Disk blocks Beginning the installation, displaying number of free 2-3 disk blocks, 1-7 Display Server C restarting, 4-3, 4-20 ___________________________ Display variable Checking the distribution setting for Font Utility, kit, 1-1 4-19 Clip art, 3-3 Distribution kit Cluster contents of, 1-1 installing DECwrite, 1-5 Documentation set, viii Commands Font Utility, 4-10 Index-1 Font Utility (cont'd) E__________________________ customizing font slant, Encoding scheme 4-8 used with font files, example, 4-9 4-24 customizing font weight, Examples 4-8 WRITE$CLIPART directory, example, 4-9 3-3 delete command, 4-12 WRITE$EXAMPLES directory, descriptions, 4-10 3-3 exit command, 4-13 Examples directory, 3-4 full option, 4-15 Exit command hide command, 4-12 of Font Utility, 4-13 menu list definition, 4-10 F__________________________ menu option, 4-15 F$MODE(), 3-5 new list File locations definition, 4-10 checking for Font Utility new option, 4-15 problems , 4-20 resolving, 4-17 Font files quit command, 4-14 compiling, 4-2 rename command, 4-14 copying, 4-2 restarting display server Font lookup file , 4-20 updating, 4-2 reveal command, 4-14, Font Utility, 4-1 to 4-26 4-16 about, 4-1 example, 4-17 add command, 4-6, 4-11 setting display variable, example, 4-6 4-19 add new command, 4-11 show command, 4-6, 4-15 changing point size, 4-15 system management changing weight and slant privileges required, , 4-15 4-1 checking file location, Fonts 4-20 adding to DECwrite, 4-1 checking security access, all at once, 4-5 4-19 individually with checking session login, customization, 4-7 4-20 individually with commands, 4-10 defaults, 4-6 comparing font files, compiling and installing 4-21 on remote workstations, confirm option, 4-6, 4-11 3-18 example, 4-7 revealing, 4-16 Index-2 Fonts (cont'd) Installation Verification slant Procedure customizing, 4-8 running after example, 4-9 installation, 3-12 definition, 4-3 recognized by Font L__________________________ Utility, 4-4 Labels third-party on distribution media, configuring, 4-2 1-2 copying, 4-2 Language weight parameter, 3-3 customizing, 4-8 variant, 2-1, 3-3 example, 4-9 Libraries, shared, 3-4 definition, 4-3 License registration, 1-4 recognized by Font Utility, 4-4 M Free disk blocks ___________________________ displaying number of, 1-7 Media labels, 1-2 Full option Menu option of Font Utility, 4-15 of Font Utility, 4-15 ___________________________ N__________________________ Global pages, 1-5 New option Global sections, 1-5 of Font Utility, 4-15 ___________________________ P__________________________ Hide command Parameter of Font Utility, 4-12 language, 3-3 PostScript font outline I__________________________ program files Images, shared, 3-4 see also PostScript Installation outline files sample printout, A-1 PostScript outline files Installation notes comparing to AFM files, compiling and installing 4-21 fonts on a remote copying, 4-3 display, 3-18 editing, 4-23 Installation on a used with Font Utility, standalone system, 3-5 4-1 Installation on a Preparing for installation, VAXcluster, 3-5 1-1 Index-3 Prerequisite software for Session login DECwrite installation, checking (cont'd) 1-2 for Font Utility, 4-20 Privileges Session Manager required to run Font running DECwrite from, Utility, 4-1 3-15 Show command Q__________________________ of Font Utility, 4-6, Quit command 4-15 of Font Utility, 4-14 SHOW DEVICE command Quotas displaying number of free for running DECwrite from disk blocks, 1-7 FileView, 3-9 Slant modifying for user of fonts accounts, 3-10 changing, 4-15 user account, 3-8 customizing, 4-9 definition, 4-3 R Software ___________________________ required before Rename command installing DECwrite, of Font Utility, 4-14 1-2 Restart command, 4-3, 4-20 Standalone system Reveal command installation on, 3-5 of Font Utility, 4-14, Starting the installation, 4-16 2-3 example, 4-17 System disk Running DECwrite, 3-17 backing up, 1-9 from the Session Manager, System startup file 3-15 editing, 3-1 System tuning S__________________________ after installation, 3-11 Sample document, 3-18 Sample installation T__________________________ printout, A-1 Tuning Screen font attributes after installation, 3-11 displaying, 4-21 Screen font files V__________________________ comparing to AFM files, VAXcluster 4-21 installation on, 3-5 Security access installing DECwrite, 1-5 checking VMSINSTAL for Font Utility, 4-19 command line, 2-3 Session login checking Index-4 VMSINSTAL (cont'd) of fonts starting the installation changing, 4-15 , 2-3 customizing, 4-9 definition, 4-3 W WRITE$EXAMPLES, 3-4 ___________________________ write$fonts.ini Weight backup, 4-5 WRITE$STARTUP.COM, 3-3 Index-5