Lotus SmartSuite for OS/2 Warp 4 Release 1.5 README.TXT (c) Copyright 1999 Lotus Development Corporation. All rights reserved. This file contains important information about installing, launching, and using the SmartSuite for OS/2 Warp 4 products. The SmartSuite for OS/2 area of the Lotus Web site, located at http://www.lotus.com/smartsuiteos2, contains up-to-date information on SmartSuite for OS/2 products. The latest editions of Release Notes (README files) and other valuable information can be found by clicking the "Downloads" link at the bottom of the SmartSuite for OS/2 home page. To get the latest support information on all Lotus products, see the Lotus Customer Support Web home page at http://www.support.lotus.com. SmartSuite for OS/2 Warp 4 Release 1.5 is an update to Release 1.1 of SmartSuite for OS/2 Warp 4. The following enhancements are included in Release 1.5: * New release of Lotus 1-2-3 includes most of the features in 1-2-3 Millennium for Windows (Release 9) * Enhanced HTML and Internet support in 1-2-3 and Word Pro * Updated 1-2-3 and Word Pro import/export filters for Microsoft Word 97 and Excel 97 * Enhanced support for installing SmartSuite in the WorkSpace On-Demand 2.0 environment * Year 2000 sliding window support in LotusScript This file contains four sections: I. Installing SmartSuite for OS/2 Warp 4 Release 1.5 II. Installing SmartSuite Release 1.5 in WorkSpace On-Demand 2.0 III. Information about SmartSuite Release 1.5 IV. Information about Prior SmartSuite Releases that Still Applies to Release 1.5 If you installed a prior release of SmartSuite for OS/2 Warp 4 and are updating to Release 1.5, read sections I, II, and III. If you are installing SmartSuite for OS/2 Warp 4 for the first time, read all four sections. The Lotus Software License Agreement displays during the installation process. To view the License Agreement later, double-click the Lotus Software License Directory folder, which is located in the Lotus Accessories folder inside the Lotus SmartSuite for OS/2 Warp 4 folder. NOTE: You must be using code page 850 for all international characters to appear correctly in the language license files. ==================================================== I. INSTALLING SMARTSUITE FOR OS/2 WARP 4 RELEASE 1.5 ==================================================== 1. System Requirements 2. Release 1.5 Installation 3. The Default Internet Browser 4. The SmartSuite Registration Program 5. The Default Directory Structure 6. Uninstalling SmartSuite Products A. Uninstalling a Standalone or Node Installation B. Uninstalling a Server or Network Distribution Installation ---------------------- 1. System Requirements ---------------------- In order to successfully install and run SmartSuite Release 1.5, you must make sure your computer meets the system requirements: * OS/2 Warp 4 (or higher) running on a Pentium 90 MHz processor (or equivalent) with 32 MB RAM (or more) * OS/2 Warp FixPak 6 (or higher) No FixPak is provided with Release 1.5. Lotus recommends that you install Release 1.5 on a system with the most recent FixPak available for your language version. The minimum requirement is FixPak 6. NOTE: You can obtain the latest FixPak from the IBM Web site at http://ps.software.ibm.com/softupd.html. * OS/2 Warp compatible VGA or higher adapter and monitor * OS/2 Warp compatible CD-ROM drive * OS/2 Warp compatible mouse or other compatible pointing device * 50 MB of disk space for SmartSuite shared components (installed once and shared by all SmartSuite products) * Plus disk space for each of the SmartSuite products you choose to install (see NOTE 2 below): 1-2-3 24 MB Approach 20 MB Organizer 17 MB Word Pro 57 MB Freelance 37 MB NOTE 1: The disk space shown above is for a Default install of each of the SmartSuite for OS/2 Warp 4 products. A Custom install option allows for the selection of optional product features that require additional disk space or the deselection of Default install features to reduce the amount of disk space required. NOTE 2: You will also need approximately 3 MB of free disk space for temporary files created during the installation process. These files are automatically deleted when installation is complete. To verify the FixPak version level on OS/2 Warp 4: -------------------------------------------------- 1. Open an OS/2 Window. 2. Type VER /R and press ENTER. 3. The following message displays: "The Operating System/2 Version is 4.00 Revision 9.0xx" (where "9.0xx" is the revision number). The revision number for FixPak 6 is 9.030. If the Revision number 9.030 (or higher) displays, you can successfully install SmartSuite Release 1.5. --------------------------- 2. Release 1.5 Installation --------------------------- You can use the Install program on the SmartSuite CD-ROM to update a previous release or to install SmartSuite for the first time. If you are updating a previous release -------------------------------------- SmartSuite Release 1.5 includes updated shared component program files that are used by all of the applications. These Lotus Shared Tools are not compatible with previous releases. The install procedure for updating a previous release is different for standalone and network installations. If you are updating Release 1.0 or 1.1 of SmartSuite for OS/2 Warp 4: * On a STANDALONE COMPUTER: You should install Release 1.5 to the same location you installed the previous release. During the installation, you should select and install ALL previously installed applications. This will replace the existing program files with the updated files. You can also select and install any application that was not previously installed. If you do NOT want to install over the previous release, you must UNINSTALL all existing SmartSuite applications using the Uninstall program from the previous release. You will then be able to use the Release 1.5 Install program to install to a new location. NOTE: If you are using CID (Configuration, Installation, and Distribution) to install to a standalone computer, you should ensure that the Response file (.RSP) has the appropriate applications selected. * On a NETWORK FILE SERVER: You should install Release 1.5 to a NEW location. Refer to the READNET.TXT file located in the root directory of the SmartSuite CD-ROM for complete information. For standalone installation instructions, refer to the steps below. If you are installing for the first time ---------------------------------------- You can install SmartSuite Release 1.5 using the installation instructions below. For information about installing to a network file server, refer to the READNET.TXT file located in the root directory of the SmartSuite CD-ROM. Standalone Installation Instructions ------------------------------------ Follow these instructions to begin the installation of SmartSuite for OS/2 Warp 4 Release 1.5: 1. Insert the SmartSuite CD-ROM in your CD-ROM drive. 2. Open an OS/2 command prompt window and type X: (where "X" represents the drive letter of your CD-ROM drive) and then press ENTER. 3. Type: INSTALL to begin the SmartSuite installation process. 4. Press ENTER. After all files have been copied to your hard disk, a message prompts you to restart your system. Click OK in this dialog box to let the installation complete. When the system prompt displays, restart your computer. NOTE: Restarting your computer before the command prompt appears may result in system errors. ------------------------------- 3. The Default Internet Browser ------------------------------- Lotus recommends that you install Netscape Navigator 4.61 for OS/2 Warp (or higher) prior to installing SmartSuite Release 1.5. Netscape Navigator 4.61 is available in Netscape Communicator 4.61 which can be found at: http://www.ibm.com/software/os/warp/netscape/ The SmartSuite Install program automatically defaults to using Netscape Navigator as the Internet browser for all of the SmartSuite applications. You can use the REGRX program to change to another Internet browser: 1. Run the REGRX.EXE utility located in the \LOTUSW4\COMPNENT directory. 2. From the RegRx Services menu, choose Set SmartSuite Web browser. 3. Select the browser you want and click OK. NOTE: Refer to the Freelance Graphics README.TXT file for additional information about changing to another Internet browser in Freelance Graphics. -------------------------------------- 4. The SmartSuite Registration Program -------------------------------------- There is a new product registration program in SmartSuite Release 1.5 that prompts you to register at the end of the SmartSuite installation. NOTE: Old registrations using the ART registration tool that shipped in previous releases of SmartSuite have expired. Please re-register SmartSuite using the registration program included in SmartSuite Release 1.5. To use the registration program after you have installed SmartSuite, follow these instructions: 1. Insert the SmartSuite CD-ROM in your CD-ROM drive. 2. Open an OS/2 command prompt window and type X: (where "X" represents the drive letter of your CD-ROM drive) and then press ENTER. 3. Type: CD IBMTOOLS and press ENTER to change to the directory where the registration program is located. 4. Type: REGISTER and press ENTER to initiate the registration program. NOTE: The SmartSuite registration program provides for registration via the Internet. To successfully register via the Internet, you must be using Netscape Navigator 4.61 (or higher). ---------------------------------- 5. The Default Directory Structure ---------------------------------- The SmartSuite Release 1.5 Install program creates a new directory, \LOTUSW4\LICENSE, on your hard disk. This directory contains the Lotus Software License agreements for all of the language versions of SmartSuite for OS/2 Warp 4. Additional information about the default directory structure is provided in section IV-1-B below. ----------------------------------- 6. Uninstalling SmartSuite Products ----------------------------------- A. Uninstalling a Standalone or Node Installation ------------------------------------------------- The Uninstall program allows you to remove all files associated with a selected SmartSuite product that were copied to your system when the product was installed. It also removes all program folders (except for the main Lotus SmartSuite for OS/2 Warp folder), all program and shadow icons created by the SmartSuite Install program, and SmartSuite for OS/2 Warp 4 registry entries placed in the OS/2 Open32 registry. 1. Close all SmartSuite products. 2. Open the Lotus Accessories folder, found in the Lotus SmartSuite for OS/2 Warp 4 folder. 3. Double-click the Lotus SmartSuite for OS/2 Warp 4 Uninstall program icon. 4. Select the SmartSuite product version(s) and click Next. 5. Select the product(s) you want to remove and click Next. 6. Click Yes. The deletion process begins when you click Yes. If you do not want to remove the selected product(s), click No. Uninstall does not delete files in your \LOTUSW4\WORK or personal directories. It does not delete a directory until all directories and files are removed from that directory. Uninstall deletes all SmartMaster templates and sample files that are installed during the installation process. If you have customized any SmartMaster templates or made changes in the sample files, be sure to rename these files prior to running the Uninstall program. You cannot use Uninstall to remove files added when you installed a second or subsequent language. NOTE: Lotus recommends that you manually remove a Server installation if it was performed from a PC which has another installed configuration. For example, if you installed multiple configuration types from the same PC (like a Server and a Node), then you can use the Uninstall program to remove the Node installation from the PC, but you should remove the Server installation manually. B. Uninstalling a Server or Network Distribution Installation ------------------------------------------------------------- There is no uninstall function provided for a Server or Network Distribution install. For these types of installations, you must manually delete all the program files under the \LOTUSW4 directory on the network file server. For more information about networks, refer to the READNET.TXT file located in the root directory of the SmartSuite CD-ROM. ================================================================ II. Installing SmartSuite Release 1.5 in WorkSpace On-Demand 2.0 ================================================================ SmartSuite Release 1.5 includes an automated program for installing SmartSuite Release 1.5 in the WorkSpace On-Demand 2.0 environment. Complete instructions are available in the READWSOD.TXT file located in the root directory of the SmartSuite CD-ROM. ============================================= III. INFORMATION ABOUT SMARTSUITE RELEASE 1.5 ============================================= 1. Year 2000 Support 2. LotusScript 4.0 3. System Requirements for Using the Euro 4. Using the Euro in SmartSuite 5. Microsoft Excel 97 and Word 97 Filters 6. Contents of the \EXTRA Directory 7. Documentation Updates 8. Customer Support Information 9. Known Issues -------------------- 1. Year 2000 Support -------------------- SmartSuite for OS/2 Warp 4 Release 1.5 is designed to be year 2000-ready. It has been fully tested and meets the Lotus guidelines for Year 2000 readiness, which means that when used in accordance with its associated documentation, SmartSuite Release 1.5 is capable of correctly processing, providing and/or receiving date data within and between the 20th and 21st centuries, provided that all products (for example, hardware, software and firmware) used with the product properly exchange accurate date data with it. NOTE: The information regarding Year 2000 readiness of Lotus Products is for informational purposes only and is not a warranty or an extension or modification of the terms of the applicable warranty. The limited warranty for Lotus products is solely as contained in the software agreement governing your use of Lotus software. For the most complete and current information about year 2000 readiness, please see the Lotus Year 2000 Web site at http://www.lotus.com/year2000. The applications in SmartSuite Release 1.5 use a sliding (rolling) or a fixed window method to determine the year if you enter dates with 2-digit years. For information about the sliding and fixed windows, refer to the online Help in 1-2-3, Approach, Organizer, or Word Pro. Click on Help - Help Topics and open the topic "SmartSuite and the Year 2000." Year 2000 and 1-2-3, Approach, Organizer, and Word Pro ------------------------------------------------------ By default, these applications use a 50/50 rule for the sliding window -- the window begins 50 years before and ends 49 years after the current year. In 1-2-3, you can disable the sliding window in the 1-2-3 User Preferences dialog box. This option is not available in Approach, Organizer, and Word Pro. NOTE: LotusScript 4.0 uses a 50/50 rule for the sliding window when used with 1-2-3, Approach, and Word Pro. Changing the 50/50 default -------------------------- The 50/50 default for the sliding window is set through a single entry in the OS/2 registry and can be changed manually at any time. To change the registry, follow the steps below. 1. Open an OS/2 window. 2. Type REGRX and press ENTER to launch the Lotus OS/2 Registry Utility. 3. Read the Registry Modification Warning screen and click OK. 4. Select Services - Set SmartSuite Year 2000 Pivot Point. 5. Type the new pivot point number in the text box. The number you enter is used to calculate the first year of the sliding window. For example, if you enter the number 20 and the system date is 1/1/1999, Lotus determines that 1999 minus 20 is 1979 (1999-20=1979), so the sliding window would begin in 1979 and end in 2078. 6. Click OK. 7. To end the RegRx program, press F3 or ALT+F4, or select Services - Exit. NOTE: Changing the pivot point in the registry changes it for 1-2-3, Approach, Organizer, Word Pro, and LotusScript. Year 2000 and Freelance Graphics -------------------------------- Freelance Graphics interprets dates with 2-digit years as 20th century (19xx). If you want to enter dates for the 21st century (20xx), you must enter 4 digits for the year. There are no date calculations in Freelance Graphics that are affected by the change in the century. NOTE: When you use LotusScript 3.0 with Freelance Graphics, 2-digit years are interpreted as current century. If the system date is 1/1/2000 or later, a 2-digit year is interpreted as the 21st century. If the system date is 12/31/1999 or earlier, a 2-digit year is interpreted as the 20th century. Lotus recommends that you enter 4 digits for the year when you use LotusScript with Freelance Graphics. ------------------ 2. LotusScript 4.0 ------------------ In SmartSuite Release 1.5, the LotusScript shared component program files have been updated to LotusScript 4.0. This updated version of LotusScript provides support for the year 2000 sliding window and other new functionality. 1-2-3, Approach, and Word Pro now use LotusScript 4.0 instead of LotusScript 3.1. NOTE: Freelance Graphics uses LotusScript 3.0. LotusScript is not available in Organizer. The LotusScript Help files provided with SmartSuite Release 1.5 are the same as those provided in the prior releases. The new information about LotusScript 4.0 is not included in the online Help. You can order a printed book about LotusScript 4.0 on the Web. The book, LotusScript Language Guide, provides an overview of the LotusScript 4.0 programming language and how to use the language's basic building blocks to create applications. To order this book, go to the following Web page: http://merchant.lotus.com/store/products.nsf You can quickly locate the book on the Web site by searching on part number "CT73LNA." NOTE: For additional information, refer to section IV-6, "LotusScript Release Notes" later in this document. LotusScript 4.0 and Year 2000 ----------------------------- The default pivot point for the year 2000 sliding window is 50/50 in the SmartSuite for OS/2 applications. The SmartSuite for Windows applications use an 80/20 pivot point for the sliding window. Sharing files that contain scripts using date values may produce different results in OS/2 and Windows. If you want to share application files using scripts between OS/2 and Windows, you must either enter 4-digit years for the date values or change the sliding window pivot point in OS/2 or Windows so that the pivot points are the same. ----------------------------------------- 3. System Requirements for Using the Euro ----------------------------------------- Support for the Euro is available starting in OS/2 Warp 4 FixPak 6. You must use a code page and font that supports the Euro to display and use the character in SmartSuite applications. In addition, certain International keyboards contain the Euro character. The Euro character is included in the following OS/2 code pages: Code page Description Kind --------- ----------- ---- 850 0xD5 (replaces dotless i) PC Latin 1 base + PM 857 0xD5 PC Turkish base + PM NOTE: The Euro is not available in the 437 (US English) or 863 (Canadian French) code pages and is not available in Win-OS/2. To identify the code page currently being used on your system, go to a system prompt, type CHCP, and press ENTER. A message displays indicating the active code page. If you need to change to a code page that supports the Euro, follow these steps: 1. Open the CONFIG.SYS file in the OS/2 System Editor. 2. Select Edit - Find and type CODEPAGE in the Find edit box. 3. Click Find. The code page statement is displayed as CODEPAGE=xxx,yyy (where xxx and yyy are code page numbers). 4. Enter 850 or 857 as the first code page (in the xxx position). 5. Save the CONFIG.SYS file and exit the System Editor. 6. Restart your computer. The Euro character is added to these fonts: Font Name Kind --------- ---- Courier (bitmap) Courier (ATM) Helv (bitmap) Helvetica (ATM) System Monospace (bitmap) System Proportional (bitmap) System VIO (bitmap) Times New Roman (ATM) Times New Roman MT 30 (TrueType - Java 1.1) Tms Rmn (bitmap) WarpSans (bitmap) NOTE: The best way to obtain these fonts is to install FixPak 6 (or higher). The Euro character is added to these OS/2 keyboards: Country ID Key ------- -- --- Belgium be altgr-e Canada ca altgr-e Denmark dk altgr-5 Finland su (fi) altgr-5 France fr altgr-e Germany gr (de) altgr-e Germany (453) de453 altgr-e Iceland ic (is) altgr-5 Iceland 101 is458 altgr-5 Italy it altgr-5 Italy extended it142 altgr-5 Latin America la altgr-e Netherlands nl altgr-e Norway no altgr-5 Portugal po altgr-5 Spain sp (es) altgr-5 Sweden sv altgr-5 Swiss French sf altgr-e Swiss German sg (sd) altgr-e Turkey tr179 altgr-e Turkey 440 tr440 altgr-e UK uk altgr-4 UK 168 uk168 altgr-e US International ux altgr-e NOTE: The Euro is not on the US keyboard. You can use the US International (ux) keyboard instead or you can access the character by pressing ALT+213. -------------------------------------------- 4. Using the Euro in SmartSuite Applications -------------------------------------------- You can insert the Euro symbol into any SmartSuite application, if you are using: * FixPak 6 or higher * A code page that supports the Euro symbol (see "System Requirements for Using the Euro" above) * A font that contains the Euro symbol (see "System Requirements for Using the Euro" above) To insert the symbol, press ALT+213. The Euro symbol will appear in the document. In SmartSuite for OS/2 Warp 4 Release 1.5, the Euro symbol is defined as a currency format in 1-2-3, Word Pro, and Approach. The following sections provide: * Instructions for using the Euro as a currency format in SmartSuite Release 1.5 applications * Information about sharing 1-2-3 and Word Pro files that use the Euro * Information about printing the Euro * Information about using the Euro in Charts 1-2-3 for OS/2 Warp 4 Release 1.5 --------------------------------- In 1-2-3 Release 1.5, the Euro is available as a currency format in the Number Format tab (#) of the InfoBox. 1. From the 1-2-3 menu with the insertion point in a cell, choose Range - Range Properties to open the InfoBox. 2. Click the Number Format tab (#). 3. Select "Currency" as the Format category. 4. Select "Euro" as the Current format. 5. Click back in the cell. 6. Type a number and press ENTER and the cell will be formatted with the Euro currency format. Word Pro for OS/2 Warp 4 Release 1.5 ------------------------------------ In Release 1.5 of Word Pro, the Euro symbol is available as a currency format in the Number Format tab (#) of the InfoBox. 1. From the Word Pro menu with the insertion point in a table cell, choose Table - Cell Properties to open the InfoBox. 2. Click the Number Format tab (#). 3. Select "Currency" as the Format category. 4. Select "Euro" as the Current format. 5. Click back in the table cell. 6. Type a number and press Tab and the cell will be formatted with the Euro currency format. Approach for OS/2 Warp 4 Release 1.5 ------------------------------------ In Release 1.5 of Approach, the Euro symbol is available as a currency format in the Number Format tab (#) of the InfoBox. 1. In the Design view, double-click the field you want to format to open the InfoBox. 2. Click the Number Format tab (#). 3. Select "Currency" as the Format type. 4. Select "Euro" as the Current format. 5. Click back in the field. Sharing 1-2-3 Release 1.5 files with other applications ------------------------------------------------------- When you save a 1-2-3 Release 1.5 file, the format of any cells formatted as Euro currency will be set to Euro currency. If this file is opened using a version of 1-2-3 for Windows that recognizes the Euro, the Euro currency formatted cells will be retained and will display correctly. When you open a file created in a prior release of 1-2-3 for OS/2 Warp 4 (for example, Release 1.1) that contains the Euro, 1-2-3 Release 1.5 will recognize and display the Euro correctly. When you save a 1-2-3 Release 1.5 file that contains the Euro to a previous version of 1-2-3 or to Excel 97 (or earlier), 1-2-3 for OS/2 Release 1.5 re-sets the format of any cells formatted to "Euro" to "Comma". Saving the format to any other currency would produce in an incorrect result. Sharing Word Pro Release 1.5 files with other applications ---------------------------------------------------------- When you save a Word Pro Release 1.5 file, the format of any table cells formatted as Euro currency will be set to Euro currency. * If this file is opened using a version of Word Pro for Windows that recognizes the Euro, the Euro currency formatted table cells will be retained and will display correctly. * If this file is opened using a version of Word Pro for Windows that does not recognize the Euro, the Euro symbol will not appear and the format of any table cells formatted as Euro currency will be set to Currency - Default. NOTE: Euro currency support was first added to Word Pro for Windows Release 9.1. To access Euro currency in Word Pro for Windows, you must have Windows 98, or Windows 95 and updated fonts that support the Euro symbol (available from a Microsoft Web site). To insert the Euro symbol in Word Pro for Windows, press ALT+0128 and then press ENTER. If you save a Word Pro Release 1.5 file to a pre-97 version of Word Pro, the Euro symbol will be removed, and the format of any table cells formatted as Euro currency will be set to Frequently Used - Default. If you save a Word Pro Release 1.5 file to Ami Pro, the Euro symbol will be removed, and the format of any table cells formatted as Euro currency will be set to General. If you save a Word Pro Release 1.5 file to another word processing file format and then open the file in that product, the Euro symbol will appear if the other product supports Euro currency. If the other product does not support Euro currency, the symbol will be removed. The format of any table cells formatted as Euro currency will vary, depending on whether the other product supports Euro currency. Printing the Euro ----------------- Existing printers do not support the Euro in device fonts. You need to select a font which is not mapped to a device font in order to print the Euro. The Euro will print correctly on printers where the system fonts are used. When there are problems, a dotless-i is normally printed instead of the Euro. For PostScript printers, it is necessary to disable device fonts to print the Euro in one of the base PostScript fonts (Helvetica, Times Roman, Courier). To do this: 1. Open the properties of the Printer object. 2. Select the Print Driver tab. 3. Select Job Properties. 4. Select the Output tab. 5. Deselect "Use printer device fonts." 6. Close the dialog box. Using the Euro in Charts ------------------------ There are two versions of the Chart component shipping with SmartSuite for OS/2 Warp 4. Freelance Graphics uses an earlier version of chart than the other applications. Charts display different behaviors depending on the application. The following are known issues when using the Euro in charts: * To use the Euro in a Freelance Graphics chart, you must enter the Euro symbol (ALT+213) or the text string "E" after the number in the data table. If you enter the symbol before the number or the text string "Euro" after the number, the chart displays incorrectly. * If you create a chart with the Euro symbol in 1-2-3 or Word Pro and then copy/paste the chart into Freelance Graphics, the chart displays as a bitmap and cannot be edited. --------------------------------------------------- 5. Microsoft Excel 97 and Microsoft Word 97 Filters --------------------------------------------------- Microsoft Office 97 filters are available in 1-2-3 and Word Pro. The File - Open and File - Save functions in 1-2-3 and Word Pro maintain as much data and functionality as possible. Note that there is not a 1:1 correspondence for all features in Microsoft Office and Lotus SmartSuite, so 100% functionality cannot be achieved. 1-2-3 ----- 1-2-3 automatically recognizes and opens a Microsoft Excel file if you specify the file name and extension in the File - Open dialog box. To view a list of Excel file names, you need to specify All or Microsoft Excel as the type of file in the 1-2-3 File - Open dialog box. (The default type of file is Lotus 1-2-3 Workbook.) If you open an Excel 97 file in 1-2-3 and use File - Save, 1-2-3 automatically saves to the Excel 97 file format. For more information about the Excel filter, see online Help in 1-2-3. Word Pro -------- Word Pro automatically recognizes and opens a Microsoft Word file if you specify the file name and extension in the Word Pro File - Open dialog box. To view a list of Word 97 file names, you need to specify MS Word 97 (*.doc) as the type of file in the Word Pro File - Open dialog box. The MS Word 97 export filter is new in Release 1.5. To save a Word Pro file in Word 97 format, you need to specify MS Word 97 (*.doc) in "Save file as type" in the Word Pro File - Save As dialog box. ----------------------------------- 6. Contents of the \EXTRA Directory ----------------------------------- The following tools and additional files are available in the \EXTRA directory on the SmartSuite CD-ROM: * The 1-2-3 & Freelance Graphics File Translator (to use older versions of 1-2-3 and Freelance Graphics files with the new releases) * Extra files needed for using TeamMail with cc:Mail * Word Pro batch conversion files * Pre-Reform German language files for spell and grammar checking * Alternative Help files (to view Help at high video resolutions, such as 1024 x 768, 1280 x 1024, and 1600 x 1200) * Installing International proofing tools * Data Validation add-in for 1-2-3 * Sample Scripts for 1-2-3 * Additional map outlines for 1-2-3 Refer to the EXTRA.TXT file in the \EXTRA directory for more information about each of these. NOTE: These tools and files are supplied as a convenience for users but are not supported by Lotus. ------------------------ 7. Documentation Updates ------------------------ Printed and Online Books ------------------------ Some pictures and instructions in the printed and online books are not accurate for SmartSuite for OS/2 Warp 4 Release 1.5. * Lotus no longer ships a FixPak with SmartSuite. You must be using FixPak 6 (or higher) to install and use SmartSuite for OS/2 Warp 4. * The disk space requirements have changed. See section I-1, "System Requirements," for additional information. * There is no tour in 1-2-3 for OS/2 Warp 4 Release 1.5. * 1-2-3 and Word Pro contain enhanced Internet functionality. See the 1-2-3 and Word Pro product updates (README files) available in the Lotus Assistance Center folder for more information. * SmartSuite Release 1.5 ships with LotusScript 4.0 for 1-2-3, Approach, and Word Pro. LotusScript Online Help ----------------------- The help topic "Bracket notation in LotusScript" contains the following inaccuracies. The Help topic: * Refers to a property (Value) which doesn't exist on the Range. * Refers to an object (Cell) which doesn't exist. * Refers to a method (Print) which is not contained by a range. * Has the incorrect syntax for the Bind statement. * Example uses a range name which exceeds the maximum length. Here is the correct content for this Help topic: Bracket notation in LotusScript For applications built in some Lotus products, such as 1-2-3, you can use names in brackets rather than object reference variables to identify Lotus product objects. To determine whether your Lotus product supports this notation, see the product documentation. Syntax [prodObjName] Elements prodObjName The name understood by the product to identify an object (an instance of a product class). Usage In some cases, Lotus products assign names to objects, and in other cases you can use the product user interface to name the objects you create. In a spreadsheet, for example, A1 identifies a particular cell, and you could use the user interface to name a chart SalesTracking. Bracket notation lets you use these names without declaring an object variable and binding it to the object. For example, the product might allow you to use: [A1].contents = Cstr(247000) instead of: Dim myCell as Range Set myCell = Bind("A1") mycell.contents = Cstr(247000) In some cases, the product uses bracket notation when it records transcripts of user actions. This makes the transcripts easier to read and modify. For more information, see the product documentation. The LotusScript compiler does not attempt to determine the class of objects that are identified with bracket notation, so any class syntax errors you make (such as the incorrect use of properties and other methods), will generate run-time errors, not compile-time errors. You can also use empty brackets to identify the currently selected product object. Empty brackets are equivalent to leading dot notation. For example, if the current selection is a range named Sales, then [ ].CopyToClipboard and .CopyToClipboard are equivalent to [Sales].CopyToClipboard All three statements copy the contents of the Sales range to the clipboard. To include square brackets as text within a string, double the brackets. For example, if the current selection is a range named Sales[East], use the following syntax: [Sales[[East]]].CopyToClipboard ------------------------------- 8. Customer Support Information ------------------------------- To locate information about customer support services, click Help - Help Topics in any SmartSuite application, expand the Troubleshooting category, and then expand the Lotus Customer Support category. Customer support services change periodically. You can call 1-800-553-4270 to obtain updated information about support services. For updated phone numbers, call 1-800-343-5414. Please note the following changes to support services: * Effective December 31, 1998, the Fax on Demand and BBS services will be discontinued. * Effective December 1, 1999, support will no longer be available via the 900 number. As an alternative, Lotus recommends that customers who require support on SmartSuite products, but do not have an annual contract, purchase support for a single incident by calling 1-800-553-4270. ------------------------ 9. Known Issues ------------------------ Netscape and the Euro --------------------- If you save a 1-2-3 Release 1.5 file that contains the Euro character in HTML format (File - Internet - Convert to Web Pages), the Euro character may display as a fallback character. This occurs on systems using Code Page 850 and FixPak 6 (or higher) when the HTML file is viewed in Netscape version 4.04. The Euro displays correctly when the HTML file is viewed in Netscape Communicator 4.61 (or higher). LotusScript SendKeys Statement ------------------------------ The LotusScript SendKeys statement is not currently supported in OS/2. SendKeys cannot send keystrokes to a window that is not an OS/2 Presentation Manager program. SendKeys cannot send keystrokes to an OS/2 Presentation Manager window if that window is in the same process as the program calling SendKeys. =============================================== IV. INFORMATION ABOUT PRIOR SMARTSUITE RELEASES THAT STILL APPLIES TO RELEASE 1.5 =============================================== 1. Important Installation Information A. If You Are a Network Administrator B. The Default Directory Structure C. If You Previously Installed an Alpha or Beta Release D. Deleting Obsolete ODBC drivers E. What You Need to Know about Having More than One Version of SmartSuite Installed on Your Machine 2. Installing SmartSuite for OS/2 Warp 4 Products A. SmartSuite Installation B. SmartSuite Install Release Notes C. Multilingual Installation 3. If you Can't Launch a SmartSuite Product A. Troubleshooting SOM B. Matrox Mystique or Matrox Millennium Video Card C. Conflicts with OS/2 Utilities D. DeskMan/2 E. Disabling SmartSuite Products' Splash Screens F. Launching Approach G. Using the RegRx Utility 4. After You Install SmartSuite Products A. Installing the Most Recent Printer Drivers B. Installing the Most Recent Video Drivers C. Reading Individual Product README Files D. Adobe Acrobat Reader and the Online Books E. Installing ODBC Drivers F. Using the Sybase ODBC Driver G. Using the IBM DB2 Drivers H. Using cc:Mail Release 8.1 with TeamMail 5. Uninstalling SmartSuite Products A. Using the Uninstall Program B. Uninstalling a Network Distribution Install C. Uninstalling SmartSuite 96 for OS/2 Products 6. LotusScript Release Notes A. LotusScript in SmartSuite for OS/2 Warp 4 vs. LotusScript in SmartSuite 96 for OS/2 B. LotusScript and REXX C. Troubleshooting and Limitations D. Ordering Printed Documentation about LotusScript E. Sample LotusScript Applications 7. Known Issues A. If You Are Installing Lotus Notes B. Multiple Products in the Startup Folder C. Running a Tour and SmartSuite Product at the Same Time D. Printing Without the HP/GL-2 Option E. Duplex Printing F. IBM 4019 Printer and Forms Mismatch G. Enhancing the Printing Performance H. Printing Tips ------------------------------------- 1. IMPORTANT INSTALLATION INFORMATION ------------------------------------- A. If You Are a Network Administrator ------------------------------------- Lotus recommends that you install the Server and Distribution versions of the SmartSuite products in new or empty directories. See the READNET.TXT file in the root directory of the SmartSuite CD-ROM included in this package for information about supported networks, performing Server and Node installs, running an automated Install, and other network-related topics. B. The Default Directory Structure ---------------------------------- The SmartSuite Install program provides the following default directory structure. This structure makes it easier to maintain and upgrade your products, since your \WORK, \BACKUP, \SMASTERS, \SAMPLES, and other directories on your hard disk are independent of your main product directory. This diagram shows the directory structure: \LOTUSW4 (Main Lotus product directory for all | Lotus SmartSuite for OS/2 Warp 4 products) | |---\123 (Executables and other core files for 1-2-3) | |---\APPROACH (Executables and other core files for Approach) | |---\FLG (Executables and other core files for Freelance) | |---\ORGANIZE (Executables and other core files for Organizer) | |---\WORDPRO (Executables and other core files for Word Pro) | . |---\ACROREAD (Acrobat Reader Installer and online book files) | |---\SMASTERS (SmartMaster templates subdirectory) | |---\123 (SmartMaster templates for 1-2-3) | |---\APPROACH (SmartMaster templates for Approach) | |---\FLG (SmartMaster templates for Freelance) | |---\WORDPRO (SmartMaster templates for Word Pro) | |---\SAMPLES (Samples for all Lotus products) | |---\123 (Samples for 1-2-3) | |---\WORDPRO (Samples for Word Pro) | |---\SCRIPTS (Samples for LotusScript) | |---\WORK (Work directory for all Lotus products) | |---\123 (Work directory for 1-2-3) | |---\APPROACH (Work directory for Approach) | |---\FLG (Work directory for Freelance) | |---\ORGANIZE (Work directory for Organizer) | |---\WORDPRO (Work directory for Word Pro) | |---\BACKUP (Backup directory for all Lotus products) | |---\123 (Backup directory for 1-2-3) | |---\APPROACH (Backup directory for Approach) | |---\FLG (Backup directory for Freelance) | |---\ORGANIZE (Backup directory for Organizer) | |---\WORDPRO (Backup directory for Word Pro) | |---\COMPNENT (Shared components for all Lotus | SmartSuite for OS/2 Warp 4 products) | |---\LICENSE (Language license files) | |---\FONTS (Fonts for all Lotus | SmartSuite for OS/2 Warp 4 products) | |---\TEMP (Temp files) | |---\ETC (*.IR files) C. If You Previously Installed an Alpha or Beta Release ------------------------------------------------------- If you previously installed an Alpha or Beta Release of SmartSuite for OS/2 Warp 4, you should uninstall the Alpha or Beta Release using the Lotus SmartSuite Uninstall program found in the Lotus Accessories folder (located inside the Lotus SmartSuite for OS/2 folder) before installing the SmartSuite products. The Uninstall program is also available in the root directory of the Alpha or Beta CD-ROM. You should also make a backup of your CONFIG.SYS file, then remove any references to the Alpha or Beta software from the following statements: LIBPATH, SET PATH, SET HELP, SET SOMIR, SET TEMP, SET TMP, SET SOMTHREADPEER, SET APOLLO_ENABLE_DLGED, SET LOTUS_CLS, SET DSQCOMMTRACE, SET DSSDIR, and SET DSSPATH. After updating the CONFIG.SYS file, save it and restart your system. After you uninstall the Alpha or Beta Release, modify the CONFIG.SYS file, and restart, you should manually remove the old \LOTUS97 or \LOTUSW4 directories (and their contents) that were not removed by the Uninstall program. Be sure to save any WORK files you created using the Alpha or Beta Release BEFORE you delete the old directories. The Uninstall program does not remove the obsolete ODBC drivers that were installed with the Alpha or Beta release of 1-2-3. Refer to Section 1-D for instructions on removing these ODBC drivers. D. Deleting Obsolete ODBC Drivers --------------------------------- If you previously installed an Alpha or Beta Release of 1-2-3, you should remove the following obsolete ODBC files from your system (if found) *BEFORE* installing 1-2-3 for OS/2 Warp 4 or Approach for OS/2 Warp 4. \OS2\odbc.ini \OS2\odbcinst.ini \OS2\DLL\odbcadm.exe \OS2\DLL\odbcinst.dll \OS2\DLL\odbcinst.hlp \OS2\DLL\odbc.dll \OS2\DLL\odbc.lib E. What You Need to Know about Having More than One Version of SmartSuite Installed on Your Machine --------------------------------------------------- You can install and use the SmartSuite for OS/2 Warp 4 products on a system containing SmartSuite 96 for OS/2 Warp. However, Lotus **recommends** that you uninstall the SmartSuite 96 products BEFORE you install the SmartSuite for OS/2 Warp 4 products. This saves disk space because SmartSuite for OS/2 Warp 4 products are installed to different directories than the previous version. You also avoid potential problems that can arise if you later decide to uninstall either version of SmartSuite. Uninstalling SmartSuite 96 on a system that has SmartSuite for OS/2 Warp 4 ----------------------------------------------- If you run the Uninstall program for SmartSuite 96 on a system that also has SmartSuite for OS/2 Warp 4 products installed, some registry and *.INI file entries will be uninstalled. You may encounter problems when you try to launch or run the SmartSuite for OS/2 Warp 4 products. In this case, you will need to reset these values. There are two ways to do this: * Re-install the SmartSuite for OS/2 Warp 4 product(s). * Use the RegRx. For more information on the RegRx utility, as well as information on how to reset values using RegRx, see Section 3-G later in this document. Uninstalling SmartSuite for OS/2 Warp 4 on a system that has SmartSuite 96 --------------------------------------------------- If you run the Uninstall program for SmartSuite for OS/2 Warp 4 on a system that also has SmartSuite 96 products installed, the SmartSuite 96 products may not launch or function properly. To resolve this, you will need to reinstall the SmartSuite 96 products. Installing older releases of SmartSuite --------------------------------------- Lotus does not support installing older releases after you've installed the SmartSuite for OS/2 Warp 4 products. ------------------------------------------------- 2. INSTALLING SMARTSUITE FOR OS/2 WARP 4 PRODUCTS ------------------------------------------------- Before you begin the installation of SmartSuite, you should close all Lotus products. A. SmartSuite Installation -------------------------- Follow these instructions to install the SmartSuite for OS/2 Warp 4 products: 1. Be sure you've completed the following BEFORE installing SmartSuite for OS/2 Warp 4: * Install FixPak 6 or higher * Uninstall the Alpha or Beta Releases (see Section 1-C) * Delete obsolete ODBC driver files provided with Alpha or Beta Releases (see Section 1-D) * Close all running Lotus products 2. Read the "SmartSuite Install Release Notes" provided later in this document; they contain important information you should be aware of before installing the SmartSuite for OS/2 Warp 4 products. 3. Insert the SmartSuite CD-ROM in your CD-ROM drive. 4. Open an OS/2 command prompt window and enter X: (where "X" represents the drive letter of your CD-ROM drive) and then press ENTER. 5. Type: INSTALL (to begin the SmartSuite installation process). 6. Press ENTER. Install consists of a series of dialog boxes that are generally self-explanatory. If you need more information when using a dialog box, choose Help by clicking Help. NOTE 1: We recommend you allow SmartSuite Install to modify your CONFIG.SYS file because there are numerous updates required for the SmartSuite products to run properly. A backup copy of your existing CONFIG.SYS file will be saved as CONFIG.nnn. NOTE 2: If you use a laptop and have multiple versions of CONFIG.SYS (such as one for office/LAN use and another for mobile use), it may be better for you to answer "No" to the "Allow install to modify CONFIG.SYS?" question. If you answer "No," the SmartSuite Install program will create a CONFIG.ADD file that you can use to manually update each of your CONFIG.SYS files. The CONFIG.ADD file is a coy of your CONFIG.SYS file plus the new entries. 7. If you find that one or more products will not launch after installing the SmartSuite products and restarting your system, refer to the following sections in this document for additional information: * Section 2-B "SmartSuite Install Release Notes" * Section 3 "If You Can't Launch a SmartSuite Product" B. SmartSuite Install Release Notes ----------------------------------- 1. You must first install FixPak 6 or higher before you install any of the SmartSuite for OS/2 Warp 4 products. 2. If you installed VisualAge C++ on your system, your CONFIG.SYS file may be set up to use the level of SOM that was packaged with VisualAge C++. For SmartSuite for OS/2 Warp 4, you will need to use the more current level of SOM that ships with OS/2 Warp 4. As a result, you must verify that your CONFIG.SYS file conforms to the following: LIBPATH: if there is an entry for \IBMCPP\DLL, it must be AFTER the \OS2\DLL entry PATH: if there is an entry for \IBMCPP\BIN, it must be AFTER the \OS2\DLL entry SOMDDIR: should be set to :\OS2\ETC\DSOM 3. If you installed Netscape on your system, the variable SET ULSPATH in your CONFIG.SYS file may have been altered inappropriately. This is known to cause problems with 1-2-3 for OS/2 Warp 4. For example, 1-2-3 might crash when you attempt to enter data in a cell. As a result, you must reset the SET ULSPATH variable in your CONFIG.SYS file to the following: SET ULSPATH=X:\LANGUAGE (where "X" is your boot drive) This is the value set by the operating system when you initially installed OS/2 Warp 4. Products are not supposed to modify this value. C. Multilingual Installation ---------------------------- You can install copies of the SmartSuite products in multiple languages. You can also run these products in different languages at the same time. If you want to install the SmartSuite products in more than one language, Lotus recommends that you complete a full Custom install of all SmartSuite products first. The first language you install becomes the default language. Then you can choose which products to install in subsequent languages. To add additional language versions, you must run SmartSuite Install again. The Install program informs you that you already have a copy of the product in a different language, and preserves the directory structure of the default language. NOTE: For information about Node and Server installations, refer to the READNET.TXT file located in the root directory of the SmartSuite CD-ROM. As you add additional language versions of SmartSuite products, the Install program adds program icons for the additional language versions to the Lotus SmartSuite for OS/2 Warp 4 folder. For example, if you install German as the secondary language, the icon for the German version of Word Pro is labeled "Lotus Word Pro für OS/2 Warp 4 - DE" and can be found in the main SmartSuite folder on your desktop. "DE" is the extension used for the German versions of the SmartSuite products. The following extensions are used for some of the other secondary language installs. No extension is used for the primary language install. Extension Language --------- -------- EN English DE German FR French DA Danish ES Spanish IT Italian PT Portuguese NL Dutch For each primary and secondary language installation, a separate icon is created for the "Lotus Accessories" folder and the "Lotus Assistance Center" folder. ------------------------------------------- 3. If You Can't Launch a SmartSuite Product ------------------------------------------- A. Troubleshooting SOM ---------------------- SmartSuite for OS/2 Warp 4 products access the OS/2 System Object Model (SOM) during product launch. Minor inconsistencies in CONFIG.SYS settings for SOM can cause launch-time crashes in 1-2-3, Approach, and Organizer for OS/2 Warp 4. There are some general guidelines for troubleshooting problems with SOM. Below is a list of four CONFIG.SYS settings you should check if you're unable to launch 1-2-3, Approach and/or Organizer: 1. The SET SOMIR= statement must NOT reference any *.IR files that do not exist and must not contain any extra or any missing semicolons. If any *.IR files are referenced that do not exist or if you have any syntax errors in the SET SOMIR= statement prior to the LTOLSO20.IR file name, you will most likely see an OLE or other error message, or the product will fail to launch without giving any error. Check your SET SOMIR= statement and verify that there are no syntax problems (such as double semicolons), and that all of the *.IR files referenced in the statement do exist, and that the statement hasn't been cut off (with a carriage break) by editing the CONFIG.SYS file using an editor that wraps lines at 256 characters. NOTE: Only 1-2-3 will issue the OLE Initialization error. 2. If you have VisualAge C++ installed, follow the instructions provided in Section 2-B, above, to verify your CONFIG.SYS file is set up to use the correct level of SOM. 3. If you're using Workgroup Enabled SOM/DSOM you may find the statement SET SOMSOCKETS=TCPIPSockets in your CONFIG.SYS file. An OLE error message, "Error occurred initializing OLE," may occur when launching a SmartSuite application if a semi-colon (;) is inserted at the end of the SET SOMSOCKETS=TCPIPSockets statement. 4. Be sure you have a SET SOMTHREADPEER=1 statement somewhere in your CONFIG.SYS file. If SmartSuite products work at first and then some fail to launch ----------------------------------------------------------------- If the SmartSuite products launch successfully after you first install them, and then at a later time, some of the products (1-2-3, Approach, and/or Organizer) suddenly stop working, check to see if the affected product is displaying the symptoms below. 1. The products display the following behavior: * 1-2-3 terminates unexpectedly while loading a file. * Organizer traps (SYS3170) in SOMD.DLL. * Approach terminates after the splash screen displays. * Word Pro starts. * Freelance Graphics starts. The file \OS2\ETC\DSOM\SOMDIMPL.DAT is corrupted. To recover, do this: * If a backup exists, restore the contents of the \OS2\ETC\DSOM directory from a backup. * If no backup exists, rename or delete the files in \OS2\ETC\DSOM. NOTE: Lotus recommends that you rename the files in the \OS2\ETC\DSOM directory instead of deleting them. 2. The products display the following behavior: * 1-2-3 displays the following message when attempting to load a file: "Error occurred initializing OLE." * Organizer displays the following message and terminates: "ASWAN_ERROR: (Error 65535(0xffff): E_UNEXPECTED - Unexpected failure, ASD_UNCHANGED). * Approach starts (Automation does not work). * Word Pro starts. * Freelance Graphics starts. This is more likely to happen immediately after installation (see next section), but it could occur after using the products for a while. Solution 1: The SET SOMDDIR= entry in CONFIG.SYS references a path that does not exist. To recover, do this: * SOMDDIR should be set to X:\OS2\ETC\DSOM (where "X" is the OS/2 boot drive), for example, SET SOMDDIR=C:\OS2\ETC\DSOM. Solution 2: The file \OS2\ETC\DSOM\SOMDCLS.DAT has a size of 0 bytes. To recover, do this: * If a backup exists, restore the contents of the \OS2\ETC\DSOM directory from a backup. * If no backup exists, rename or delete the files in \OS2\ETC\DSOM. NOTE: Lotus recommends that you rename the files in the \OS2\ETC\DSOM directory instead of deleting them. If SmartSuite products fail to launch immediately after installation -------------------------------------------------------------------- If 1-2-3, Approach, and/or Organizer fail to launch immediately after completing the installation, check to see if the affected product is displaying the symptoms below. 1. The products display the following behavior: * 1-2-3 displays the following message when attempting to load a file: "An unexpected OLE error occurred. OLE error: 8007000a." * Organizer fails to start. * Approach terminates unexpectedly. * Word Pro starts. * Freelance Graphics starts. The SET SOMIR= entry in the CONFIG.SYS file may be truncated. To recover, do this: * Make sure that the SET SOMIR= entry in the CONFIG.SYS file is not truncated or split to another line. The SET SOMIR= statement in the CONFIG.SYS file should include the following for the SmartSuite products: X:\LOTUSW4\ETC\WPSC2.IR;X:\LOTUSW4\ETC\ORGANIZE.IR; X:\LOTUSW4\ETC\APPROACH.IR;X:\LOTUSW4\ETC\L14SOM.IR; X:\LOTUSW4\ETC\LTSCTO31.IR;X:\LOTUSW4\ETC\LTSOMO10.IR; X:\LOTUSW4\ETC\LTSRXO20.IR;X:\LOTUSW4\ETC\LTOLSO20.IR; X:\LOTUSW4\ETC\FLG.IR; (where "X" is the drive where SmartSuite is installed) 2. The products display the following behavior: * 1-2-3 displays the following message when attempting to load a file: "An unexpected OLE error occurred. OLE error: 8000759b." * Organizer fails to start. * Approach terminates unexpectedly. * Word Pro starts. * Freelance Graphics starts. The SET SOMIR= statement may contain an error in syntax. To recover, do this: * Make sure that each entry for a *.IR file in the SET SOMIR= statement in the CONFIG.SYS file is separated by a semi-colon. * Make sure that there are no spaces in the SET SOMIR= statement in the CONFIG.SYS file. * Make sure the directory path for each semi-colon separated entry in the SET SOMIR= statement in the CONFIG.SYS file exists. B. Matrox Mystique or Matrox Millennium Video Card -------------------------------------------------- If you experience an OS/2 system hang or an application crash while launching any of the SmartSuite for OS/2 Warp 4 products and you're using a Matrox Mystique or Matrox Millennium video card, one or more of the following should allow you to successfully launch the product(s) experiencing the hang or crash. * Disable the product's logo (or "splash") screen by adding the parameter shown below to the Parameters field on the Program page of the Properties notebook for the product's program icon: Product Parameter Results in the following: ------- --------- ------------------------- 1-2-3 -q no logo, no Welcome dialog, new file Approach -s no logo, but Welcome dialog available Freelance -q logo presented, but no Welcome dialog Organizer -nosplash no logo Word Pro -s no logo, but Welcome dialog available * If you're using a color depth of 16,777,216 colors, change your color depth to 65,536 colors. You can change your color depth by selecting a different screen resolution from the Screen tab of the System notebook found in the System Setup folder normally found in the OS/2 System folder. * Obtain the latest Matrox Mystique or Matrox Millennium video driver. You can download the latest driver from http://www.matrox.com. C. Conflicts with OS/2 Utilities -------------------------------- If you're running any OS/2 utilities that add frame controls (such as an exit button, a roll-up/collapse button, etc.) to product windows, you should disable the utility and then try launching the SmartSuite product(s) again. D. DeskMan/2 ------------ If you're running DeskMan/2 you may experience a crash in PMWINX.DLL when attempting to launch 1-2-3, Approach, or Organizer for OS/2 Warp 4. For additional information and details on how to obtain an updated version of DeskMan/2 that solves this problem, visit the "Frequently Asked Questions" area of the DevTech Web site at http://www.devtech.com/DeskMan/faqs. (Note: URL is case-sensitive.) E. Disabling SmartSuite Product Splash Screens ---------------------------------------------- If you have a problem launching any of the SmartSuite products, your problem may be related to the video card/video driver combination you're currently using. Sometimes disabling the product splash screen allows the product to launch correctly. For information on disabling the product splash screen, refer to Section 3-B above. F. Launching Approach --------------------- If you only have a problem launching Approach: 1. Be sure you have a SET LOTUS_CLS=X:\LOTUSW4\COMPNENT (where "X" is the correct drive letter) and that the subdirectories are named correctly. If this environment variable is not set, you may see the Approach splash screen (or logo screen) for a moment followed by Approach failing to launch. Approach needs this variable set in CONFIG.SYS to locate and initialize LotusScript at product launch time. 2. Launch Approach by opening an OS/2 window, then switch to the \LOTUSW4\APPROACH subdirectory, type the command APPROACH FILENAME.APR (where "FILENAME.APR" represents any Approach database file that is located in the \LOTUSW4\WORK\APPROACH subdirectory), and then press ENTER. This method will work if the cause of the Approach launch problem was a corrupted "thumbnail" (or bitmap preview of the file) in the most recently used Approach file, which Approach attempts to display in the Approach Welcome dialog box. Once you successfully launch Approach you can disable the Welcome dialog box using the command File - User Setup - Approach Preferences. Or you can simply re-save the problematic file while in the Worksheet view or any other view that does not contain any rounded rectangles or buttons. This will insure that the file is re-saved with a valid thumbnail. G. Using the RegRx Utility -------------------------- FixPak 6 (and higher) includes a new, enhanced OS/2 Open32 Registry structure that uses SYSTEM.DAT and USER.DAT registry files located in the \OS2\SYSTEM subdirectory. The SmartSuite Install program sets up (initializes) the OS/2 Open32 Registry with information required for launching and running the SmartSuite products properly. If a SmartSuite for OS/2 Warp 4 product cannot be launched, you may see error messages such as: 1-2-3 "Tool module (LTEDR40.DLL) not found. Make sure..." Approach "Couldn't find SmartIcons. Please run INSTALL.EXE..." Organizer "An error occurred. Save your file and close..." Freelance "Out of Memory" NOTE: Word Pro usually launches even with registry errors. If you encounter this problem, you can easily reset the Open32 Registry for the specific product(s) by using the Lotus OS/2 Registry Utility (REGRX.EXE). This utility is installed in the \LOTUSW4\COMPNENT subdirectory at the time you install one or more of the SmartSuite for OS/2 Warp 4 products. NOTE: The RegRx utility can only be used on standalone installations. Node installations must reinstall SmartSuite for OS/2 Warp 4 to correct registry problems. To use this utility to reset the Registry, do the following: 1. Open an OS/2 window and switch to the \LOTUSW4\COMPNENT subdirectory. 2. Type REGRX and press ENTER to launch the Lotus OS/2 Registry Utility. 3. Read the Registry Modification Warning screen and click OK. 4. Select Services / Initialize SmartSuite application(s). 5. Select the SmartSuite product to be reset (you can only select one product at a time) and click OK. 6. Check the Lotus path (Lotus Parent directory) and the Product path specified, and change the drive letter, or make other modifications as required. These two paths MUST be correct for the registry initialization to work properly. 7. Click Initialize to cause the Registry Utility to reset the Open32 Registry with the entries required for the selected product. You should see the message: "SmartSuite registry initialization completed successfully." If you see "Internal error (898) detected. This registry operation is canceled," you specified the Lotus Parent directory incorrectly. 8. Repeat steps 5-7 for each SmartSuite product that needs to be reset. 9. To end the RegRx program, press F3 or ALT+F4, or select Close from the system menu of the RegRx main window. 10. You should now be able to launch the SmartSuite for OS/2 Warp 4 product(s). The Registry updates are effective immediately. You do not need to restart your system. ---------------------------------------- 4. AFTER YOU INSTALL SMARTSUITE PRODUCTS ---------------------------------------- A. Installing the Most Recent Printer Drivers --------------------------------------------- You can download the latest printer drivers from the IBM Personal Software Services Web site at http://ps.software.ibm.com. B. Installing the Most Recent Video Drivers ------------------------------------------- If you experience video display problems such as incorrect painting of controls, stray lines, missing colors on dialogs, etc., you may need a newer version of the video driver. There are several ways to obtain updated video drivers for OS/2 Warp 4: * Contact the manufacturer of your video driver to obtain the the most recent version of the driver. * Download the latest video drivers from the IBM Personal Software Services Web site at http://ps.software.ibm.com. * Call IBM at 1-800-237-5511 and choose "OS/2" on the phone menu. * Contact your IBM representative. C. Reading Individual Product README Files ------------------------------------------ The README files of the individual products contain product-specific information about functions and features, as well as other important information. These files are available both from the CD-ROM and in each product's subdirectory after installation. In addition, after installation, you can access them by clicking the Product Updates icons in the Lotus Assistance Center folder in the Lotus SmartSuite for OS/2 Warp 4 folder. On the CD-ROM, look for: After installation, look for: ----------------------- ---------------------------- ENGLISH\123\README.12 LOTUSW4\123\README.TXT ENGLISH\APPROACH\README.AP LOTUSW4\APPROACH\README.TXT ENGLISH\FLG\README.FL LOTUSW4\FLG\README.TXT ENGLISH\ORGANIZE\README.OR LOTUSW4\ORGANIZE\README.TXT ENGLISH\WORDPRO\README.WP LOTUSW4\WORDPRO\README.TXT NOTE: The Word Pro README file is also available as a README.LWP file and can be viewed in Word Pro using the File - Open menu command. It is located in the \LOTUSW4\WORK\WORDPRO directory. The latest editions of these README files are available on our Web site at http://www.lotus.com/smartsuiteos2. Click the "Downloads" link to check for updated README files. D. Adobe Acrobat Reader and Online Books ---------------------------------------- If you selected the Books and Scripts option during the SmartSuite for OS/2 Warp 4 installation, the Install program for Adobe Acrobat 3.0 for OS/2 Warp will be placed in the \LOTUSW4\ACROREAD folder on your hard drive. You can install the Acrobat Reader after you complete the installation of SmartSuite for OS/2 Warp 4 by double-clicking on the "Click here to install Adobe Acrobat Reader 3.0" icon found in the Online Books folder which is located in the Lotus Assistance Center folder. NOTE 1: If you already have the Acrobat Reader installed, you do not need to install it again. If you need support with installing and using Acrobat Reader, please contact Adobe. NOTE 2: If the install of the Acrobat Reader fails, select the option to delete the installed files, restart your OS/2 Warp 4 system, and try the installation again. If you're running 4OS2, an OS/2 shareware program, you may not be able to execute the install program. To work around this problem, start a regular command shell by typing CMD at the 4OS2 command prompt, and then manually run the Adobe Acrobat Reader Install program from the \LOTUSW4\ACROREAD subdirectory. Installing the Acrobat Reader takes just over 6 MB of hard disk space. If you install the Acrobat Reader, an Adobe Acrobat folder will be placed on your OS/2 desktop containing the Acrobat Reader. After installing the Reader, you will be able to read the .PDF files found in the Online Books folder by simply double-clicking their icons. It is not necessary to restart your computer after installing the Acrobat Reader. If you encounter video display problems when viewing the online books, check to see if the problem is occurring in another video driver or in a different resolution. If the problem is apparent in only one video driver or only in one resolution in the same driver, contact IBM about obtaining an updated video driver. For more information on video drivers, refer to Section 4-B above, "Installing the Most Recent Video Drivers." E. Installing ODBC Drivers -------------------------- The following Intersolv version 3.01 32-Bit ODBC drivers are automatically installed to the \LOTUSW4\COMPNENT subdirectory during the installation of SmartSuite: * Btrieve (*.dta) * DB2 * dBASEFile (*.dbf) * Informix5 * Oracle7 * Sybase * TextFile (*.*) NOTE: To use the Btrieve, DB2, Informix5, Oracle7, and Sybase ODBC drivers with SmartSuite products, you must install the ODBC Client Software for OS/2, which may be obtained from the original vendor. The Client Software is not shipped with SmartSuite for OS/2 Warp 4. SmartSuite for OS/2 Warp 4 provides this set of ODBC drivers so that ODBC data sources files can be viewed in 1-2-3, Approach, Organizer, and Word Pro. ODBC support is automatically integrated into Organizer. If you want to view ODBC data source files in 1-2-3, Approach, or Word Pro, you need to follow the instructions below to: * Select ODBC support during a Custom install of SmartSuite. * Configure the ODBC drivers you want to use. Selecting ODBC support during a Custom install of SmartSuite ------------------------------------------------------------ 1. Initiate the SmartSuite Install program. 2. In the Select Lotus SmartSuite Applications dialog box, select one or more of the SmartSuite products you want to install and then click Next. 3. In the Type of Install dialog box, select Custom Install and then click Next. 4. In the Select SmartSuite Application to Customize, select either 1-2-3, Approach, or Word Pro and click Customize. 5. In the Custom Install dialog box, scroll through the tab panels to locate the option for ODBC, and then select it. 6. Repeat steps 4 and 5 to install the ODBC support option for the other two SmartSuite products (1-2-3, Approach, or Word Pro). 7. Follow the instructions on the screen to complete the installation. Configuring the ODBC drivers ------------------------------- You need to configure the ODBC drivers so that the SmartSuite products can access your data source files. 1. Open the Lotus Accessories folder and double-click the ODBC Administrator icon. The Create New Data Source dialog box appears. 2. On the User DSN tab, click Add. 3. Select the name of the ODBC driver that corresponds to the data source you want to access. For example, click on Intersolv 3.01 32-BIT Btrieve (*.dta), Intersolv 3.01 32-BIT DB2, Intersolv 3.01 32-BITdBASEFile (*.dbf), and so on. Use the horizontal scroll bar to view the driver names. 4. Click Done. The ODBC Driver Setup dialog box for the driver you selected appears. 5. Specify the appropriate information for each field. Each driver's Setup dialog box has a different number of fields and tabs for configuring settings. To avoid problems when using Approach, use all UPPERCASE identifiers when specifying the name of the new ODBC data source. NOTE: To get help on installing a specific ODBC driver, open the Lotus Accessories folder and double-click the ODBC Administrator Help icon. Expand the Notices category for the driver you want to install and double-click "Configuring Data Sources." 6. Click OK when you complete all the settings. The newly configured ODBC driver appears in the list of drivers displayed in the Create New Data Source dialog box. 7. Click OK to close the ODBC Administrator. The values you specify in the Driver Setup dialog box become the defaults for your connection to the data source. You can modify these settings by reconfiguring the data source in the Driver Setup dialog box. After you have installed ODBC support (using Custom install) and configured an ODBC data source, you can open a data source file in a SmartSuite product. For more information about viewing ODBC data source files in 1-2-3, Approach, and Word Pro, refer to each product's online Help. F. Using the Sybase ODBC Driver ------------------------------- If you want to access Sybase data source files, you need to do the following: 1. Follow the instructions in Section 4-E (above) to install the SmartSuite products using a Custom install. Be sure to select the option for ODBC support. (Note that the option is not visible in the first two tabs; you have to scroll through several tabs in the notebook to see the ODBC support option.) 2. Install the Sybase Open Client version 10.0.4. This product must be obtained from the original vendor. During the installation, the file LOCALES.DAT is installed to the \SQL10\LOCALES directory. 3. Follow the instructions in Section 4-E above to configure the ODBC Sybase driver using the ODBC Administrator. 4. If you are using an English language version of SmartSuite, edit the file SQL10\LOCALES\LOCALES.DAT so that the content reflects the following: ------------------------------------------------ [NT] ; En_US added for compatibility with SmartSuite for OS/2 (LANG env. var.) locale = En_US, us_english, iso_1 locale = enu, us_english, iso_1 ... [OS2] locale = default, us_english, cp850 ; En_US added for compatibility with SmartSuite for OS/2 (LANG env. var.) locale = En_US, us_english, cp850 ... ------------------------------------------------ NOTE 1: Enter the text exactly as above using upper- and lowercase. NOTE 2: If you are using a non-English language version, you will need to modify the LOCALES.DAT file with information specific for the language version you are using. You can test the configuration by running the program SQL10\BIN\SYBPING.EXE. If you get warning messages, then you need to verify that you modified the LOCALES.DAT file correctly. If the file is correct, check the CONFIG.SYS file to make sure the \SQL10 directory is listed correctly in the LIBPATH statement. For more information, see the note below. NOTE: OS/2 Warp 4 installs LIBCS.DLL in the \OS2\DLL directory, and this interferes with Sybase's version of a DLL with exactly the same name. All Sybase users must ensure that Sybase's DLL directory (usually \SQL10\DLL) is listed BEFORE \OS2\DLL in the LIBPATH statement of the CONFIG.SYS file. The Sybase installer does this by default, but if you move the Sybase directory to the end of LIBPATH, you will not be able to access Sybase data sources unless you rename OS/2's version of LIBCS.DLL. G. Using the IBM DB2 Drivers ---------------------------- Lotus recommends using the OS/2 drivers supplied with DB2 rather than the Intersolv 3.01 32-bit DB2 Drivers. For more information, see the Approach README file. H. Using cc:Mail Releases 6.x and 8.1 with TeamMail --------------------------------------------------- If you are running cc:Mail Releases 6.x or 8.1, refer to the EXTRA.TXT file in the \EXTRA directory for information on how to ensure that cc:Mail works correctly with TeamMail. ----------------------------------- 5. UNINSTALLING SMARTSUITE PRODUCTS ----------------------------------- A. Using the Uninstall Program ------------------------------ For current information, refer to Section I-6 above. B. Uninstalling a Network Distribution Install ---------------------------------------------- For current information, refer to Section I-6 above. C. Uninstalling SmartSuite 96 for OS/2 Products ----------------------------------------------- Refer to Section IV-1-E for information about uninstalling these products. ---------------------------- 6. LOTUSSCRIPT RELEASE NOTES ---------------------------- A. LotusScript in SmartSuite for OS/2 Warp 4 vs. LotusScript in SmartSuite 96 for OS/2 -------------------------------------------- Some significant changes have been made to the LotusScript Word Pro interface that existed in SmartSuite 96. For example, Word Pro has an Integrated Development Environment (IDE )and a Dialog Editor. You can use this environment to create, program, and save dialogs. If you created dialogs in Word Pro 96, you will need to recreate them in Word Pro for OS/2 Warp 4 and save them in an .LWP file. For more information on the IDE or Dialog Editor, see the online Help. Freelance Graphics, however, has basically remained the same. B. LotusScript and REXX ----------------------- LotusScript for OS/2 Warp 4 is enhanced with the LotusREXXManager. When you use LotusScript in the OS/2 operating environment, you can use the LotusREXXManager as an interface with the OS/2 IBM REXX interpreter. The LotusREXXManager allows users of Lotus SmartSuite and Lotus Notes to access REXX functionality implemented in OS/2. It also allows users to extend the capabilities of LotusScript by using REXX commands and functions. To view the LotusREXXManager class reference help: 1. Start 1-2-3, Approach, or WordPro. 2. Open the Script Editor In Word Pro, choose Edit - Script & Macros - Show Script Editor. In 1-2-3, choose Edit - Scripts & Macros - Show Script Editor. In Approach, choose Edit - Show Script Editor. 3. Choose Help - LotusScript. 4. Expand the LotusScript Language Reference category. 5. Expand the LotusScript and REXX Integration category. 6. Expand REXX reference 7. Select the desired class, property, method, or event. Note: An older version of the LotusScript/REXX .DLL is also available in Freelance Graphics; however the implementation is not documented. Freelance Graphics uses the LTSRXO10.DLL to run the commands REXXCMD and REXXFUNCTION. For more information about the REXXCMD and REXXFUNCTION commands, see the online Help for Freelance Graphics. These commands are not documented in the REXX information for 1-2-3, Approach, or Word Pro. C. Troubleshooting and Limitations ---------------------------------- LotusScript IDE --------------- When writing scripts using the LotusScript Script Editor, you may encounter the following limitations: * While debugging a script, you cannot step into a class destructor, an %INCLUDE file, or a USE module. * Extended characters above codepoint 128 (such as LMBCS codes) do not display correctly when a script file is generated in a different code page and imported into the script editor. * OS/2 does not support text lines of over 512 characters. Word Pro -------- * When you use the REXXManager in Word Pro, you cannot set breakpoints in the IDE to debug Script-REXX problems. Freelance Graphics ------------------ * Events are not available in Freelance Graphics for OS/2 Warp 4. They are available in 1-2-3, Approach, and Word Pro for OS/2 Warp 4. * The Freelance Graphics script properties "OleObj" and "IsOLEObj" cannot run in OS/2. You can, however, use these to write scripts that will run in Freelance Graphics 96 and 97 for Windows 95. * Several Freelance Graphics properties, methods, and classes can only be used in Freelance Graphics for Windows. These are marked as such in the Freelance Graphics LotusScript Reference in online Help. LotusScript Language Reference ------------------------------ You may encounter the following limitations while programming in the LotusScript language: * If a run-time error occurs within a class constructor's parameter expression, the class constructor halts execution. After the error occurs, the object is deleted, and LotusScript will attempt to execute the class destructor. This may cause another run-time error if the destructor relied on the action of the constructor. * Circular structures are not properly destroyed by LotusScript, and the memory for those structures is not released until you end the session. * Errors occurring within a class destructor must be handled within that procedure; error-handling routines outside of the destructor cannot trap errors occurring within the destructor. * For converting between decimal numbers and strings, the conversion functions CDbl and CStr should be used in favor of Val and Str. CDbl and CStr honor the OS/2 setting for the decimal symbol, while Val and Str do not. For example, if the decimal symbol is a comma (,), the number one-and-five-tenths is represented as the string "1,5". The code shows how to convert this string to its numeric form: Dim x As Double x = CDbl( "1,5" ) X now contains the decimal value of one-and-five-tenths. The CStr function is used to convert it to a string containing the regional digit separator: Dim y As String Dim y As Double x = 1.5 y = CStr( X ) results in y containing the string "1,5" (again assuming the specified decimal symbol is the comma). NOTE: Although CDbl will always work, you may want to use CSng or CCur instead, depending on the desired data type of the result, or the magnitude of the number being converted. * The UBound function sometimes returns incorrect data when used with a dynamic array that is passed as an argument to a procedure. * The Inspector doesn't display properties for native classes. * If you change a class to a property, the associated methods become module-level procedures. D. Ordering Printed Documentation about LotusScript --------------------------------------------------- The book "Developing SmartSuite Applications Using LotusScript" contains basic information about the application programming interfaces (APIs) of 1-2-3, Approach, Freelance Graphics, and Word Pro, and introduces new developers to the concepts of programmable objects and how to manipulate them. Other books available in printed form in the LotusScript Documentation Set for OS/2 include: * "LotusScript Language Reference" Provides a comprehensive summary of conventions and basic commands for the LotusScript language. This book provides the foundation for programming any product that supports the LotusScript programming language. This book is also available as an Adobe Acrobat .PDF file in SmartSuite. * "The LotusScript Programmer's Guide" describes the basic building blocks for LotusScript applications and provides many working examples. This book is also available as an Adobe Acrobat .PDF file in SmartSuite. To order the LotusScript Documentation Set for OS/2, you can use the order form in the book "Installing and Using SmartSuite Products," or you can use the order form supplied in online Help. To find the order form in online help, do the following: 1. Start 1-2-3, Approach, or Word Pro. 2. Choose Help - Help Topics 3. Search the Help Index for "Order Form." E. Sample LotusScript Applications ---------------------------------- The book "Developing SmartSuite Applications Using LotusScript" provides many sample applications that you can use to modify and extend the capabilities of SmartSuite. For your convenience, some of these scripts can be installed as independent applications by doing a custom install. To install the sample applications, complete the following steps. 1. Choose to do a custom install. 2. In the Install Select SmartSuite Applications to Customize dialog box, select "Books and Scripts." 3. Choose Customize. 4. Click the "Sample Scripts" tab. 5. Select "Sample LotusScript Application Files." 6. Click OK. 7. Finish the install with the desired options. The install program will install the sample applications into the \LOTUSW4\SAMPLES\SCRIPTS directory of the drive specified. Each file is complete with instructions on what task it accomplishes and code comments. NOTE: These applications are written in English for use with the English product. Some problems have been encountered when running some of the scripts in a SmartSuite product for another language. See the list of files below for information about specific problems. List of Sample Applications available through Custom Install ------------------------------------------------------------ ODATENTR.123 ------------ Description - The script is attached to the Click event for the 1-2-3 command button named cmdPrint on the first sheet. When the user clicks the button, 1-2-3 displays a message box, selects a named range for printing, and prints the range. Potential problems - NONE OSIGNMEM.LSS ------------ Description - The script automatically adds name and company information to the end of the current document using information from the Personal tab in the Word Pro preferences dialog box. Potential problems - NONE OMENUITM.LWP ------------ Description - Creates a menu item in Word Pro from which you can run the OSIGNMEM.LSS application. Potential problems - NONE OVIDOSUM.LWP OVIDOSUM.APR OVIDOSUM.DBF ------------ Description - Opening the .LWP file in Word Pro for OS/2 creates a a custom menu that allows you to open a database in Approach, move data from Approach into Word Pro, and manipulate the Approach data. Potential problems - The data comes into the Word Pro document very slowly and sometimes does not format correctly. OCUSFUNC.123 ------------ Description - Creates an @function that calculates the time that has elapsed between two times and displays the information as a label. Potential problems - The output of this script is noted in hours, minutes, and seconds. If you are running this application in a language other than English and would like for the output to be noted differently, you will need to modify the output by modifying the value of the output variable. OSAVVIEW.123 ------------ Description - Stores a list of previously opened workbooks (along with size, window position, etc.) in a text file and opens the workbooks. Potential problems - NONE OLAB2VAL.123 ------------ Description - Converts labels in a selected range to values. Potential problems - NONE OLET2NUM.123 ------------ Description - Converts a number to a column or sheet letter. Also, converts a letter to sheet number. Potential problems - This script works, but was created for the 26 letter English alphabet. If you have accented or foreign characters in your worksheet, the script results are not guaranteed. OXTABREP.123 ------------ Description - Creates a crosstab table in a new sheet. Potential problems - This script contains hard-coded macros which may not work in non-English SmartSuite products. OAUTOSAV.123 ------------ Description - Displays a custom dialog box that enables Auto Save functionality. Potential problems - NONE OGLRANGE.123 ------------ Description - Displays a custom dialog box that lets the user select a range and then choose from a number of changes that apply to the entire range. Potential problems - NONE ONOTEDAT.LSS ------------ Description - Access data from a Notes database. Potential problems - NONE OFINDREC.APR OFINDREC.DBF ------------ Description - Prompts the user for information and executes a find operation. Potential problems - NONE ORES_SET.LSS ------------ Description - Uses a result set to loop through each record and makes changes. Potential problems - NONE OMOD_REC.APR OMOD_REC.NBF OMOD_REC.DBT ------------ Description - Uses the result set from ORES_SET.LSS to loop through each record in the current set and modify it. Potential problems - NONE ONEW_DOC.LSS ------------ Description - Creates a new Approach document that displays the data from a result set. Potential problems - NONE OCHG_SUM.APR OCHG_SUM.NBF OCHG_SUM.DBT ------------ Description - Prompts the user for a field by which to group records, then groups the records and displays the output. Potential problems - NONE OCLIPART.LSS ------------ Description - Adds a piece of clip art to the current page. Potential problems - In order to run this script, you must import the .LSS file into the Script Editor. OBULLIST.LSS ------------ Description - Fills a bulleted list with predefined text. Potential problems - To run this script, your presentation must have a title page. OTXT2TAB.LSS ------------ Description - Converts text into table entries. Potential problems - NONE OAGENDA.LSS ------------ Description - Turns information in a table into an agenda or "to do" pages. Potential problems - To run this script, you must have the table highlighted. OAUTOMAS.MWP ------------ Description - When you use this SmartMaster to create a new document, it prompts you for personal information and inserts the information into Click here blocks. Potential problems - NONE OCLKHERE.MWP ------------ Description - Validates the type of information entered into specified Click here blocks and prompts the user to enter information in the correct format. Potential problems - NONE OCUSMEN.LSS ----------- Description - Creates a custom menu and menu items. Potential problems - NONE OCUSVIEW.LSS ------------ Description - Creates a custom view using splits and multiple-page views. Potential problems - NONE OFUNCKEY.LSS ------------ Description - Resets the function keys as style accelerators (similar to their use in Ami Pro.) Potential problems - NONE OMRG_LET.LWP OMRG_DAT.LWP ------------ Performs a merge with a previously created data file. Potential problems - NONE --------------- 7. KNOWN ISSUES --------------- A. If You Are Installing Lotus Notes ------------------------------------ If you plan to install SmartSuite for OS/2 Warp 4 and Lotus Notes on the same system, you should install Lotus Notes for OS/2 BEFORE installing any of the SmartSuite for OS/2 Warp 4 products. If you install SmartSuite for OS/2 Warp 4, and then later install Lotus Notes for OS/2 on the same system, you will NOT be able to successfully run the Uninstall utility for SmartSuite for OS/2 Warp 4 because Lotus Notes will, during its installation, delete entries found in the files required by the Lotus SmartSuite Uninstall program. B. Multiple Products in the Startup Folder ------------------------------------------ If you attempt to launch multiple SmartSuite for OS/2 Warp 4 products at the same time during OS/2 boot-up by placing copies of their program icons in your Startup folder, you may encounter a situation where one or more of the products crash on launch. If you encounter this problem, remove one or more of the SmartSuite for OS/2 Warp 4 products from the Startup folder. C. Running a Tour and SmartSuite Product at the Same Time --------------------------------------------------------- If you are running a product tour and need to work in one of the SmartSuite products, close the tour before working in the product or the tour may crash. D. Printing Without the HP/GL-2 Option -------------------------------------- The HP/GL-2 (Hewlett-Packard Graphical Language/2) option is a performance enhancement added to the job properties of some printer drivers, including HP LaserJet. When HP-GL/2 mode is enabled, all the vector drawing and area fills are handled by the driver using HP-GL/2 commands, while the bitmaps are handled by the OS/2 Graphics Engine which are rendered last. If your printed output contains text and graphics, especially overlapping text and graphics, the printed output may be incorrect when using the HP/GL-2 option, since the graphics are handled after the text. For example: * In 1-2-3 and Word Pro, text on top of bitmaps will not appear. * In Organizer, white text on black backgrounds will not appear, and some lines in printed timelines will not appear. To avoid seeing problems such as these in all of the SmartSuite products, turn OFF the HP-GL/2 option in your printer's Job Properties panel. If you are running Word Pro, you can turn off the HP-GL/2 option from the Printer icon on the Desktop to have it affect all Word Pro printing. To do this, follow these steps: 1. Right-click on the printer icon on the desktop. 2. In the pop-up menu, click Properties. 3. Click the Printer Driver tab. 4. Click Job properties. 5. In the Job Properties panel, click on the Options tab. If HP-GL/2 is listed as a Performance Option, make sure that the box is not checked. For all SmartSuite for OS/2 Warp 4 products running on FixPak 6 or later, you can turn off the HP-GL/2 option using either method. E. Duplex Printing ------------------ On some newer HP LaserJet printers (for example, 5Si, 5Si Mx, 5Si Mopier), a duplex unit is available as an add-on feature. The options for 2-sided printing are by default not selectable in the printer Job Properties panel and 2-sided printing is not possible without these options. To enable the options for 2-sided printing, do this: 1. Right-click on the Printer icon on the desktop. 2. In the pop-up menu, click Properties. 3. Click the Printer driver tab. 4. Right-click on the printer driver in the "Default printer drivers" box. 5. Click Properties. 6. In the Available options box on the Configure panel, select "Duplex Unit (for 2-sided printing)." 7. Click Add to add it to the "Installed options" box. 8. Click Save. Your Job Properties should now have both 2-sided printing options available for selection. When printing duplex from some of the SmartSuite products using the HP LaserJet or PostScript printer drivers, you may see that the back of the first page is blank but all other pages are duplexed (printed double-sided). While Word Pro does not have this problem, it may occur in the other SmartSuite products. The problem has been reported to IBM and the fix is included in the HP LaserJet driver in versions 30.547 and higher. At the time of the writing of this file, the fix for the PostScript driver was not yet available. You can check the current version of the drivers to see if the fix has been provided. See Section 4-A for instructions on how to download the latest printer drivers. F. Forms Mismatch ----------------- If you get a forms mismatch, you need to verify that the correct form is connected to the correct Paper Source. To do this, follow these steps: 1. Right-click the Printer icon on the desktop. 2. Click "Properties" in the pop-up menu. 3. Click the "Printer driver" tab. 4. Double-click the Printer icon to display the Printer Properties. 5. Look at the field "Default Form/Source." It should show the form you want to print on. If it doesn't, click on the down triangle to see more selections and select the form you want to use. 6. If your form is not listed, click "Form Connections." In the Form Connections panel make sure the "Paper Source" you want to use has the form of interest assigned to it. 7. Click OK to close the panels. G. Enhancing the Printing Performance -------------------------------------- Font selection -------------- The selection of text fonts can significantly affect printing performance. OS/2 supports two types of fonts: downloaded system fonts and printer device fonts. Device fonts are built into the laser printer and perform much faster. When text is formatted for the printer by the OS/2 spooler, one of two paths is taken: (1) for each system font text character, the spooler must request a bitmap of the character from the OS/2 operating system, or (2) for device fonts, the text character is sent directly to the printer as an ASCII character. The following is a list of fonts which may be supported by your laser printer as device fonts. The list varies between laser printer models and manufacturers. Univers CGTimes Antique Olive Coronet Courier Garmond Antiqua Albertus Garmond Kursiv Garmond Halbfett Letter Gothic Marigold WingDings Reg Arial Reg Symbol True Type Times New CGOmega There are a number of system and add-on fonts for OS/2 which do not perform as well as device fonts, including Helvetica and Times New Roman. You can try substituting the device font equivalents; for example, Univers for Helvetica and CGTimes for Times New Roman. Big Buffer ---------- The Big Buffer option allows the OS/2 spooler to temporarily use 4MB of system memory to format the document for the printer; the default for OS/2 Warp Versions 3 and 4 is 1 MB. Big Buffer is set in the Printer Properties (or Printer Setup) - Options (or Advanced Options) panel. Increasing the value of Big Buffer will increase the performance of printing, while decreasing the amount of available memory. Spooling format --------------- Some products support spooling in either metafile (STD) or bitmap (RAW) formats. The overall time for both formats to print a document is about the same. However, the STD format is sent to the OS/2 spooler much faster than the RAW format and returns control of the mouse and cursor to the user sooner. When RAW format is used, the product must format the document in the foreground which ties up the keyboard much longer, whereas with STD format, the OS/2 spooler formats the document in the background. The STD or RAW format selection, if available, is in the Printer Properties panel of the product. NOTE: Organizer and Approach normally print in RAW mode. WordPro, Freelance, and 1-2-3 allow you to make the choice between STD and RAW mode. Spooler priority ---------------- Increasing the priority of the OS/2 spooler improves printing time by up to one-third, but decreases the responsiveness of the mouse and keyboard accordingly. If absolute printing time is important, setting the OS/2 spooler priority to the highest setting will help. You might also consider foreground printing for a single-user printer by disabling the OS/2 spooler. Both of these options are set at the OS/2 Spooler icon which is in the OS/2 System - System Setup folder. Click on the OS/2 Spooler icon with the right mouse button. You can select "Disable Spooler" or click on "Settings" to open the OS/2 Spooler Settings notebook to change the "Spooler Priority." Disk cache ---------- Smaller improvements can be gained by increasing the disk cache size for the file system on which the spooler stores its temporary files. The spooler temporary directory can be changed in the OS/2 Spooler Settings notebook. Generally, sizes larger than 4096 kilobytes for a desktop PC provide little, or no improvement. Shared network printers can benefit more when the disk cache is increased on the server. Increasing disk cache permanently reduces the amount of memory available to other products. For information on setting these parameters, type: HELP DISKCACHE for the FAT file system HELP HPFS.IFS for the HPFS file system Typically, the default disk cache sizes perform well for most documents. H. Printing Tips ---------------- * On some monochrome printers, colored device fonts print in black because the printer cannot gray scale its device fonts. If you need the text or image printed in shades of gray to represent the colors, you should check the Printer Setup for your printer driver. Many printer drivers provide an option for enabling and disabling the printer fonts and the downloaded system fonts. Disabling these options in Printer Setup may allow the text or image to print in shades of gray. * Bitmap patterns will most likely print darker than they display on the screen because the screen resolution is usually lower than the printer resolution. If your printout is too dark, you can either change (usually decrease) the resolution of the output or make the fill color lighter on a darker background. * When printing, you should set your printer driver Job Properties to your desired options before printing. Many of the OS/2 printer driver defaults are set for best results with presentations using less than 256 colors. If you are printing high quality images you should set your printer driver to 24-bit or presentation quality graphics. NOTE 1: 24-bit is the highest quality and will produce the smoothest gradations, but is slower and may require more memory to print. 8-bit is faster but may produce noticeable gradations and may change the colors of some bitmaps. NOTE 2: Normally you should close the product before changing the Job properties. The change becomes effective the next time you launch the product. The only exception to this is Freelance Graphics. To change the Job properties for Freelance Graphics, select Job properties from the Print dialog box within the product. * When using the IBMPCL3, IBMPCL5, IBM4019 printer drivers, you should turn on Big Buffers in Job Properties - Advanced Options to avoid an occasional problem with multi-page documents printing all white after some number of pages. NOTE: There are some occasions when the printing resolution is too high for the amount of system memory installed and Big Buffers cannot be turned off. The only option in this circumstance is to lower the printing resolution in the printer driver Job Properties dialog box or install more system memory. * The following tip applies to Freelance Graphics only: If the edges of your presentation are clipped off when printing, part of your presentation was probably drawn outside the printable area of your printer. To view the printable area on the screen, choose View - Set View Preferences - Printable area. Since different printing devices have different unprintable areas, you should be careful not to draw too close to the page margins when designing presentations that are intended to be printed on a variety of printers. When changing the printer driver you should choose the "Scale down everything on the page so that all items are visible on the new device" option.