═══ 1. Special Notices ═══ References in this help to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM licensed program in this help is not intended to state or imply that only IBM's licensed program may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this help. The furnishing of this help does not give you any license to these patents. The following terms, denoted by an asterisk (*) in this help, are trademarks of the IBM corporation in the United States and/or other countries: IBM OS/2 WorkFrame/2. ═══ Product information ═══ This window contains information about the WorkFrame/2* Setup program. To continue with the Setup program, click on OK. For more information about setup and installation, press F2 from this help window. ═══ 2. Using Setup ═══ Use the WorkFrame/2* Setup program to: o Install the WorkFrame/2 product on your hard disk o Remove the WorkFrame/2 product from your system o Migrate WorkFrame/2 projects and language profiles from previous versions of the WorkFrame/2 o Selectively install or re-install selected WorkFrame/2 features, and install WorkFrame/2 from a network o Set monitor and project settings For the most recent information about the Setup program and other WorkFrame/2 components, read the READ.ME file displayed in the main Setup window. ═══ Updating Your CONFIG.SYS File ═══ The WorkFrame/2* installation program will not create duplicate entries for WorkFrame/2 environment variable settings in your CONFIG.SYS file if you are re-installing WorkFrame/2 Version 2.1 in the same directory. If this is the first time you are installing the WorkFrame/2 product or if you are re-installing it to a different directory, the installation program will update your CONFIG.SYS file to contain the necessary WorkFrame/2 settings. Updates to your CONFIG.SYS file include the following additions: o C:\IBMWF\BIN to the PATH variable o C:\IBMWF to the DPATH variable o C:\IBMWF\HELP to the HELP and BOOKSHELF variables o C:\IBMWF\DLL to the LIBPATH variable. Note: Substitute your selected target installation directory for C:\IBMWF. ═══ 3. Options ═══ Use the Options pull-down to select setup and installation options. Pull-down Summary Install Starts the installation program. Undo installation Deregisters the WorkFrame/2* product from your OS/2* system. Migrate Migrates projects and language profiles from previous versions of the WorkFrame/2 product. Selective setup Installs or restores selected features on your system. Settings Lets you set monitor and project settings. Show status Displays the WorkFrame/2 Install Status window that indicates the current status of the install. ═══ 3.1. Install ═══ To begin installing the WorkFrame/2* product on your system, select Install from the Options pull-down menu. A window appears where you can select installation options. You can use the preselected IBM* installation defaults, or set your own options. The installation program creates all the necessary directories and subdirectories, and copies the files to the appropriate location on your hard disk. The program also updates your CONFIG.SYS file. Note: Installing WorkFrame/2 Version 2.1 does not overwrite any previous versions of the WorkFrame/2 product (versions 1.0 or 1.1). Multiple versions can co-exist in your system. Note: If you are re-installing the WorkFrame/2 application, you will need to delete any existing WorkFrame/2 templates from the OS/2* Templates folder to avoid duplicates. Related information: o How WorkFrame/2 installation works ═══ 3.1.1. WorkFrame/2 Installation ═══ WorkFrame/2 installation is a two-phase process: o Phase 1 involves copying WorkFrame/2 files onto your hard disk. After step one has completed, you are asked to shutdown and reboot your system. Shutdown of your system after phase 1 has completed can take up to a minute as the OS2.INI file is being updated. o Phase 2 starts automatically after you reboot. It involves registering WorkFrame/2 classes to the Workplace Shell, and creating the WorkFrame/2 folders and objects on your Desktop. If you are reinstalling the WorkFrame/2 Version 2.1 product, you will need to reboot your system again after phase 2 is completed for WorkFrame/2 objects you previously created, such as projects and actions profiles, to reappear on the Desktop. If this is your first time installing the WorkFrame/2 product, or if you did not previously create any objects, you do not need to reboot after phase 2 of installation is complete. ═══ 3.1.2. Installation Options ═══ Use the installation Options window to specify the Target Path drive and directory where you want the WorkFrame/2* files installed. The default is to install the WorkFrame/2 files in the IBMWF directory on your boot drive. If you are installing for the first time, the target path fields are set to their default values. If you are reinstalling, the target path is set to the values you specified the last time you installed. When you have specified your target path, click on the OK pushbutton to start the installation. ═══ Target Path ═══ Use the Drive and Directory fields to specify the drive and directory to which the WorkFrame/2* files are to be installed. Leading and trailing backslashes (\) and blanks are ignored. You cannot use drive A: or B: as the target drive. The default path is the directory IBMWF on your boot drive. ═══ OK ═══ When you have selected your target path for the install, click on the OK pushbutton to validate the options and start the installation. ═══ Reset ═══ Click on the Reset pushbutton to update the installation target path settings to their initial values. If you are installing for the first time, the target path settings are reset to their default values. If you are reinstalling, the settings are reset to the settings you selected the last time you installed. ═══ Default ═══ Click on the Default pushbutton to set the options to their default values. ═══ Cancel ═══ Click on the Cancel pushbutton to remove the installation Options window from the screen and cancel the current operation without saving any changes. ═══ Install Backup ═══ The installation program tried to create a backup file for your CONFIG.SYS environment file using your specified file name and the extension .BAK, but the file already exists. In the Backup filename field in the Install Backup window, you can type a different name for the backup file, or use the same name to overwrite the existing backup file. Click on OK to create the backup file. If you do not want to create a backup file, click on Cancel to close this window and continue with the installation. ═══ OK ═══ When you have chosen the backup file name, click on the OK pushbutton to back up the CONFIG.SYS file. ═══ Cancel ═══ Click on the Cancel pushbutton to close the Install Backup - CONFIG.SYS window and return to the installation program without saving any changes. The backup file will not be created. ═══ 3.2. Undo Installation ═══ Select Undo installation to make all WorkFrame/2 objects deletable. Undo installation performs two tasks: o Deregisters all the WorkFrame/2 Version 2.1 classes from the Workplace Shell o Makes any installed WorkFrame/2 Version 2.1 objects and folders deletable. If Undo installation was performed successfully, the Delete menu item should appear on the pop-up menu of all WorkFrame/2 objects and folders. Undo installation does not: o Remove any WorkFrame/2 objects or folders from the Desktop o Delete any installed WorkFrame/2 files o Remove any WorkFrame/2 entries from your CONFIG.SYS file. Note: You do not need to perform Undo installation in order to re-install this version or a higher version of the WorkFrame/2 product. Use Undo installation only if you want to remove the WorkFrame/2 product from your system. Related Information: o Removing the WorkFrame/2 application from your system ═══ Removing WorkFrame/2 ═══ To fully delete the WorkFrame/2* product from your system, perform the following steps: 1. From the Options pull-down on the Setup window, select Undo installation to make all WorkFrame/2 objects, files, and folders deletable. 2. If you plan to re-install the WorkFrame/2 product at a later date, delete the WorkFrame/2 templates from the OS/2* Templates folder or you will see duplicate templates the next time you install. 3. Next, delete the WorkFrame/2 folder from the Desktop by selecting Delete from its pop-up menu, or by dragging it to the shredder. If the folder could not be deleted because some objects within it were in use, ensure that no part of the WorkFrame/2 is in use, then try deleting the folder again. If the problem persists, continue with the next step then try deleting the folder again after you reboot. 4. Edit your CONFIG.SYS file and remove any WorkFrame/2 entries. 5. Shutdown then reboot your system to free any WorkFrame/2 DLLs in use. 6. Delete the installed WorkFrame/2 files by dragging the main WorkFrame/2 directory folder from the OS/2 Drives folder to the Shredder, or by selecting Delete from its pop-up menu. 7. If the WorkFrame/2 folder is still present on your Desktop, try deleting it again now. The WorkFrame/2 product should now be completely removed from your Desktop and file system. ═══ Deleting WorkFrame/2 Templates ═══ To delete the WorkFrame/2 templates, perform the following steps: 1. Open the OS/2 Templates folder from the Desktop. 2. Select a WorkFrame/2 template other than the Actions Profile template, then display its pop-up menu by clicking on it with mouse button 2. 3. Select Open  Settings from the pop-up menu to open the template's settings notebook. 4. From the Settings notebook, select the General page. 5. From the General page, deselect the Template checkbox. 6. Repeat steps 1 to 5 for each WorkFrame/2 template in the folder, except for the Actions Profile template, which is automatically deleted when you reboot after a de-installation. 7. Next, from an OS/2 command prompt, make your boot drive the default drive. For example, if your boot drive is C:, type C:, then change the current directory to DESKTOP\TEMPLATE by typing cd DESKTOP\TEMPLATE. In the DESKTOP\TEMPLATE directory, you should find two files and one directory, each respresenting a WorkFrame/2 template. For a FAT system, they are usually named: ACTIONS_ (file) WORKFRAM (file) WORKFRA1 (directory) They may have different names of the forms: ACTIONS?? (file) WORKFR?? (file) WORKFR?? (directory) where ? represents a file name character. 8. Delete the template object files. The WorkFrame/2 template objects are removed from the Templates folder when the files are deleted. The next time you install the WorkFrame/2 product, a new set of WorkFrame/2 templates are created. ═══ 3.3. Migrate ═══ Select Migrate to convert projects and profiles from previous versions of the WorkFrame/2 product to the current version. The new objects appear in a folder on the desktop. ═══ Migrate Projects and Language Profiles ═══ Enter the fully qualified path names of WorkFrame/2 version 1.0 or 1.1 project files and language profiles, or select the Find push button to find them. The project files and profiles in the indicated path are converted into objects for WorkFrame/2 Version 2.1 if the objects do not already exist. Only one path may be entered at a time. You can use OS/2* wildcards to specify the path. If only a project file name or mask is entered, the migration program converts the specified projects and their associated profiles. If only a profile name or file mask is entered, only the specified profiles are converted, and not the projects associated with them. Select Migrate to begin the conversion or select Cancel to close the window without taking any action. The migrated projects and profiles will be placed in a folder called WorkFrame/2 Migrate on the Desktop. ═══ Migrate ═══ Click on the Migrate push button to start the migration of the files specified in the migration entry field. ═══ Cancel ═══ Click on the Cancel push button to cancel the current operation without saving any changes. No objects will be migrated. ═══ Find ═══ Click on the Find push button to select a file for migration. ═══ Find Projects and Profiles to Migrate ═══ Use the Find window to select which objects you want migrated. The Migrate window will show the directory where the Setup program assumes version 1.x level of the WorkFrame/2 product was installed. If the directory indicated is wrong, you can switch to the correct directory using the Find window. Projects and profiles have the extensions .PRJ and .PRF respectively. To select one or more files: 1. Click on the down arrow to the right of the Drive field to display all the drives in your system. 2. Select a drive from the Drive list. 3. Select a directory from the Directory list. 4. Type the name of the file you want to migrate in the Open filename entry field or select one or more files from the File list. 5. Click on the Migrate push button to migrate the objects represented by the selected files. For a detailed explanation of each field, select its name from the list below: o Drive o Directory o Open filename o File o Type of file o Migrate. ═══ Open filename ═══ Type the name of the file you want to select in this field, or select a file from the File list. ═══ Type of file ═══ Click the down arrow to the right of the Type of file field to display the available file types. The File list displays all the files of your selected file type in the currently selected directory. ═══ Drive ═══ Click the down arrow to the right of the Drive field to display all the drives in your system. The Directory displays all the directories in your selected drive. ═══ Directory ═══ The Directory list box displays all the directories in the drive you selected in the Drive field. Select the directory of the files you want to migrate from this list. ═══ File ═══ The File list box displays all the files (matching the Type of file choice) in the directory you selected from the Directory list. Select one or more files you want to migrate from this list. ═══ Migrate ═══ Click on the Migrate push button to migrate the selected files. ═══ Migration Status ═══ This window shows you how the migration process is progressing. Click on the OK pushbutton to continue remove the Migration Status window from the screen when the migration process has completed. ═══ OK ═══ Click on the OK push button to remove the Migration Status window from the screen when the migration process has completed. ═══ Migration Results ═══ This window appears if there were any project files or profiles which were not migrated for one of the following reasons: o They could not be found o They already exist as WorkFrame/2* Version 2.1 objects. This window appears, for example, if a composite project being migrated contains a project which no longer exists, or if there are project objects with the same name as those being migrated, or if the projects have been previously migrated. Objects not found are listed in the Projects and profiles not found list box. Objects which already existed as WorkFrame/2 Version 2.1 objects when the migration process was started are listed in the Already existing objects list box. Select OK to close the window once you have viewed the information. ═══ Migration List ═══ The Migration List window shows all the projects and language profiles that were successfully migrated to WorkFrame/2 Version 2.1. Select OK to close the window once you have viewed the information. ═══ 3.4. Selective Setup ═══ Use Selective setup to: o Copy WorkFrame/2* files from a source directory to a target directory o Update the CONFIG.SYS file o Add users to a LAN-based WorkFrame/2 environment o Update the Desktop for the WorkFrame/2 application o Restore the Default Actions Profile to its original state. ═══ 3.4.1. Using Selective Setup ═══ Use the Selective Setup window to restore certain WorkFrame/2* components, or to set up your environment to share the WorkFrame/2 application from a LAN server. Installing WorkFrame/2 from a LAN server is different from an ordinary installation, because most of the WorkFrame/2 files are left to reside on the LAN, and only some are copied onto the target directory on your workstation. To use this window: 1. In the Source path field, indicate where the WorkFrame/2 Version 2.1 product is installed, or, in the case of a LAN install, indicate the name of the directory where the WorkFrame/2 server files are installed. 2. In the Target Path fields, indicate the Drive and Directory where you want the WorkFrame/2 LAN client files to be installed. 3. Then, select any combination of options you want to setup or restore. To install WorkFrame/2 Version 2.1 on your LAN workstation, select the Install IBM WorkFrame/2 from network checkbox. Selecting this check box automatically selects the the Copy files, Update CONFIG.SYS and Update desktop check boxes necessary for a WorkFrame/2 LAN installation. Select Update Default Actions Profile to restore your Default Actions Profile to its initial state. If you are using Selective Setup for the first time, the options are updated to their default values. If you are updating your environment, the options you chose the last time you used Selective Setup are shown. When you have specified the options you want, click on the OK pushbutton to perform your selected actions. ═══ Source Path ═══ In the Source path entry field, type the path where the WorkFrame/2* files are to be installed from. In the case of a LAN installation, type the name of the directory where the WorkFrame/2 server files are installed. By default, this field initially contains the directory in which the WorkFrame/2 product was installed. ═══ Target Path ═══ In the Target path entry fields (Drive and Directory), type the drive and directory where the WorkFrame/2* files are to be copied to. The target drive cannot be A: or B:. By default, these fields initially contain the name of your boot drive and the IBMWF directory. ═══ Install IBM WorkFrame/2 from Network ═══ To install WorkFrame/2 Version 2.1 on your LAN workstation, select the Install IBM WorkFrame/2 from network checkbox. Selecting this check box automatically selects the Copy files, Update CONFIG.SYS and Update desktop check boxes which are necessary for a WorkFrame/2 network installation. ═══ Copy Files ═══ Select the Copy files checkbox to copy essential WorkFrame/2* files from the path specified in the Source path field to the drive and directory specified in the Target path fields. If the specified target path does not exist, it is created before the files are copied. ═══ Update CONFIG.SYS ═══ Select the Update CONFIG.SYS check box to have the Selective Setup program update your CONFIG.SYS file to include the correct environment variable settings for the WorkFrame/2* product. If you have previously installed the WorkFrame/2 product, and your CONFIG.SYS file already has the correct environment variable settings, no action will be taken. However, if the settings have changed since the initial install, or are invalid for any reason, your CONFIG.SYS file will be updated with the correct settings. ═══ Update Desktop ═══ Select the Update Desktop checkbox to create or update the IBM* WorkFrame/2* V2.1 objects on your Desktop. Objects within the WorkFrame/2 folder will also be updated. ═══ Update Default Actions Profile ═══ Select the Update Default Actions Profile check box to create or restore your Default Actions Profile to the IBM*-supplied settings. ═══ OK ═══ When you have selected the WorkFrame/2 features you want to set up, click on the OK pushbutton to start your selected action. ═══ Reset ═══ Click on the Reset pushbutton to reset the options to settings they had when you first opened the Selective Setup window. If you are using Selective Setup for the first time, the settings are reset to their default values. If you are updating your environment, the settings are reset to the options you chose the last time you used the Selective Setup utility. ═══ Default ═══ Click on the Default pushbutton to reset the Selective Setup options to their default values. ═══ Cancel ═══ Click on the Cancel pushbutton to cancel the current operation without saving any changes. ═══ Undo Installation ═══ The WorkFrame/2* product is being deregistered from the Workplace Shell. Please wait until the process has completed. ═══ 3.5. Settings ═══ Select this option to open the Settings window where you can set options on WorkFrame/2* monitor and project defaults. ═══ WorkFrame/2 Settings ═══ Use the WorkFrame/2 Settings window to specify options on WorkFrame/2* monitor and project defaults. When you have made your choices, select Set to implement them. If you want to close the window without making any changes, select Cancel. ═══ Set ═══ Click on the Set pushbutton to make your WorkFrame/2* settings active as currently shown. ═══ Cancel ═══ Click on the Cancel pushbutton to cancel the current operation without saving any changes. ═══ 3.5.1. Monitor Settings ═══ From the Settings window, you can set Monitor defaults for: Automatic scrolling on To have the monitor scroll to its new lines automatically Restore last size To have a new monitor window appear in the same size as the last monitor window that was closed. ═══ 3.5.2. Project Settings ═══ From the Settings window, select the Refresh when tools finish check box to have project views automatically refreshed every time a tool has finished running in the Monitor window or every time a WorkFrame/2-enabled tool has created a new file. Otherwise, refreshes only occur when the Refresh now option is selected from the project's system menu. ═══ 3.6. Show Status ═══ Select Show status to display the Install Status window. ═══ Install Status ═══ The Install Status window shows you: o The files that are currently being copied to your hard disk, and the directories from which they are being copied on the installation disk o The directories on your hard disk to which the files are being copied o The percentage of bytes already installed, compared to the total number of bytes needed to complete the installation. ═══ Hide ═══ Click on the Hide pushbutton to remove the Install Status window from the Desktop. To show the Install Status window once it is hidden, select Show status from the Options pulldown on the Setup menu bar. Hiding the Install Status window does not stop the installation process, nor does it stop the particular action it is reporting. ═══ 4. Help ═══ Use the Help pull-down to find out how to use help, to get general help on the program, to go to the help index, or to look at the product information. The following options are available: Help index Displays the help index. General help Displays general help for the installation program. Using help Provides detailed information on the kinds of help available and how to use help. Product information Displays the product copyright information. Help is always available. You can get help in 4 ways: 1. Press F1 at any time for help about a specific action bar pull-down or option (if one was currently selected) 2. Select a Help topic from the Help pull-down 3. Click on the Help button in a dialog or message box 4. Press F2 at any time to get general information about the currently active window. For the most recent information about the program, read the READ.ME file displayed in the main Install window. ═══ 4.1. Using Help ═══ Select Using help for information on how to use the Help facility. ═══ 4.2. General Help ═══ Select General help to get general information about the WorkFrame/2* Setup program. ═══ 4.3. Help Index ═══ Select Help index to display the Help index. ═══ 4.4. Product Information ═══ Select Product information to display product information for the WorkFrame/2* Setup program. ═══ 4.5. Keys Help ═══ The WorkFrame/2* Setup program has no specific key assignments. For help on general keys, see Key Assignments in the Master Help Index. ═══ Message Help ═══ Explanation: The Setup program cannot open the initialization file indicated in the message. Recovery: Select Retry to attempt to open the initialization file again. If this message continues to appear, contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: The Setup program cannot open the initialization file indicated in the message. Recovery: Select Retry to attempt to open the initialization file again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: The WorkFrame/2* Setup program cannot open the WFINST.INI file containing the initialization information for the program. Recovery: Ensure that the WFINST.INI file exists on the installation diskette, and that it is not already in use. Then, restart the program. If the file has been corrupted, contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: The WorkFrame/2* Setup program cannot find the necessary initialization data in the WFINST.INI file. Recovery: Ensure that the WFINST.INI file is not already in use, then restart the program. If the file has been corrupted, contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: The WorkFrame/2* Setup program could not be initialized. There may not be enough memory available. Recovery: Stop any large processes that are running. Then restart the program and try again. ═══ Message Help ═══ Explanation: Not enough memory is available for the background thread needed to install the files. Recovery: Stop any large processes that are running and ensure your swap path is large enough. If you are using a virtual disk, redefine it to a smaller size. Then, click on Retry to try the operation again. Click on Cancel to stop the installation program. ═══ Message Help ═══ Explanation: There may not be enough free storage space on the indicated drive to install the selected options. Recovery: Perform one of the following actions: 1. Ignore the warning and continue with the installation by clicking on the OK button. However, the program may not be able to install all of the options. 2. Delete some files from your hard drive to make more space available. Note: If you are reinstalling the WorkFrame/2* product to the same target directory, you may not need as much space as indicated in the message. ═══ Message Help ═══ Explanation: The WorkFrame/2* cannot display the indicated window. There may not be enough memory available. Recovery: Stop any large processes that are running, and try the program again. ═══ Message Help ═══ Explanation: There is not enough memory available to complete the the installation. The installation program has stopped. Recovery: Stop any large processes that are running, and ensure the swap path is large enough. If you are using a virtual disk, redefine it to a smaller size, then retry the program. You may need to obtain an additional memory card if the problem persists. ═══ Message Help ═══ Explanation: A call to an OS/2* API failed to open a WorkFrame/2 folder on the Desktop. Recovery: Select Retry to try the operation again. If the error persists, select Cancel to stop the installation process, reboot your system, then try the installation again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program was unable to write to either the IBMWFV2.INI or OS2.INI files to store information about the options installed. Recovery: Make sure there is available disk space, and that the file is not already in use. Then, click on the Retry pushbutton. If the error persists, click on the Cancel push button to halt the installation process, then try the installation again. ═══ Message Help ═══ Explanation: An operating system error occurred while WorkFrame/2* was copying the indicated file. See the OS/2* Return Codes Help for more information on the error. Recovery: Make sure enough disk space is available, and that the path specified is valid. Correct the error if possible, and try the operation again. ═══ Message Help ═══ Explanation: The path specified as the main WorkFrame/2* directory is not correct. See the OS/2* Return Codes Help for more information on the error. Recovery: Ensure the path is valid and that the WorkFrame/2 files are installed in the specified directory, then try the program again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program encountered an unexpected error from an OS/2* file call. See the OS/2* Return Codes Help for more information on the error. Recovery: Because the error may have affected the program, correct the error if possible, then try the program again. ═══ Message Help ═══ Explanation: The specified file is missing from the source directory. Recovery: Ensure that the specified source path is valid, and that the WorkFrame/2* files are installed in the specified directory. Then, try running the program again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program cannot create the target directory specified. See the OS/2* Return Codes Help for more information on the error. Recovery: Make sure that the path specified is valid, and that there is enough disk space available. Correct the error if possible, then try the operation again. ═══ Message Help ═══ Explanation: The operating system cannot find the boot drive. The WorkFrame/2* installation program has stopped. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible, then restart the program and try again. If the error persists, contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program cannot create the installation directory specified. There may not be enough memory or disk space available. See the OS/2* Return Codes Help for more information on the error. Recovery: Stop any large programs that are running and ensure the swap path is large enough. Then try the operation again. If there is not enough disk space to create the directory, try installing the product on another drive. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program was unable to back up the indicated file. See the OS/2* Return Codes Help for more information on the error. Recovery: Click on OK to return to the Backup window. Make sure the path and file name specified are valid, that the file is not already in use, and that there is enough disk space available. Then, try the operation again. ═══ Message Help ═══ Explanation: This error occurred for one of the following reasons: o The WorkFrame/2* installation program cannot find the files on the installation diskette to install an indicated option o The files cannot be unpacked using UNPACK.EXE o The target files are in use. The return code from UNPACK.EXE indicates the cause of the error. For more information about return codes, refer to the OS/2* online information on UNPACK.EXE (type help unpack on the OS/2 command line). Recovery: Ensure that you have Version 2.1 of UNPACK.EXE. If you are reinstalling, ensure that no part of the WorkFrame/2 product is in use, then try the operation again. If the problem persists, the files may have been damaged or destroyed. Contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: A directory with the same name as the specified installation directory already exists. If you continue with the WorkFrame/2* installation, any file with the same name as an installation file will be overwritten. Recovery: If you do not want to overwrite existing files, Click on No to cancel the current operation, then change the name of the target installation directory. Otherwise, click on Yes to overwrite the existing files. ═══ Message Help ═══ Explanation: The operating system cannot find the starting directory of the installation program. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible, then restart the program and try again. If the error persists, contact your IBM* Service Representative for help. ═══ Message Help ═══ Explanation: The help file for the WorkFrame/2* installation program, WFINST.HLP, cannot be copied to the help path. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible. Ensure that enough disk space is available, and try again. ═══ Message Help ═══ Explanation: The indicated help file for the WorkFrame/2* could not be installed. See the OS/2* Return Codes Help for more information on the error. Recovery: Click on the Retry pushbutton to try the operation again. If the error persists, click on the Cancel pushbutton to continue installation without copying the indicated help file (help may be incomplete or missing), or wait for the current installation process to complete then try running the installation program again . ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program could not deregister the indicated class. It could have been deregistered earlier by another process. Recovery: You do not need to take any action. Just select OK to continue. ═══ Message Help ═══ Explanation: The installation program was unable to create a WorkFrame/2* class. Recovery: Click on the Retry pushbutton to have the installation program try the operation again. If the error persists, click on the Cancel pushbutton to stop the installation. Then, try running the installation program again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program could not find the indicated object. It could have been deleted by another process. Recovery: You do not need to take any action. Just select OK to continue. ═══ Message Help ═══ Explanation: The installation program was unable to create a WorkFrame/2* object. Recovery: Click on the Retry pushbutton to try to create the object again. If the error persists, click on the Cancel pushbutton to stop the installation, then try running the installation program again. ═══ Message Help ═══ Explanation: The installation program was unable to set data within an object. Recovery: Select Retry to try the operation again. If the error persists, select Cancel to stop the installation, then try running the installation program again. ═══ Message Help ═══ Explanation: The installation program could not destroy the indicated WorkFrame/2* object. Recovery: Select Retry If the error persists, select Cancel to stop the installation, then run the installation program again. If it fails again, contact your IBM* Service Representative. ═══ Message Help ═══ Explanation: The installation program was unable to add the WorkFrame/2* objects to the folder on the Desktop. Recovery: There may not be enough memory available, or the Desktop may be in use. Try the operation again by clicking on the Retry button. Clicking on the Cancel button stops the installation program. ═══ Message Help ═══ Explanation: There are no project files in the specified directory. Recovery: Specify a directory that contains project files. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program has been invoked twice. Recovery: Click on OK to continue working with the first instance of the installation program. ═══ Message Help ═══ Explanation: The indicated diskette has not been inserted into the drive. Recovery: Insert the correct diskette into the diskette drive, then click on OK to continue with the installation. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program was stopped by a user action. Recovery: Click on OK to return to the main installation window. To restart the program, select Install from the Options pull-down menu. To exit the program, select Close from the system menu. ═══ Message Help ═══ Explanation: The projects in this directory have already been converted to work with this version of the WorkFrame/2* product, or objects with the same name as the version 1.0 or 1.1 projects already exist. Recovery: No action is required. Select OK to continue. You can: o Delete the corresponding WorkFrame/2 Version 2.1 objects, then retry the migration operation again if you want to migrate the previously migrated version 1.0 projects again o Rename the corresponding WorkFrame/2 2.1 objects then try the migration operation again o Take no action. Select OK to terminate the migration. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program found a version 1.0 or 1.1 profile in the specified directory, but a Version 2.1 actions profile object (the version 1.0 equivalent of a language profile) with the same name already exists. Recovery: Select OK to continue without recreating the indicated profile. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program found a version 1.0 or 1.1 composite project, but a Version 2.1 composite project with the same name already exists. No conversion will take place. Recovery: Select OK to continue without converting the indicated project. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program found a version 1.0 or 1.1 base project, but a Version 2.1 project with the same name already exists. No conversion will take place. Recovery: Select OK to continue without converting this project. ═══ Message Help ═══ Explanation: The specified folder to contain all the converted objects already exists (that is, the files have already been converted). Recovery: If you want to convert the files again, delete the folder and try the operation again. ═══ Message Help ═══ Explanation: Language profiles cannot be converted into WorkFrame/2* Version 2.1 actions profiles unless the WorkFrame/2 Profiles folder exists. Recovery: If the WorkFrame/2 product installed successfully, this folder should exist unless it was deleted later. If the Profiles folder is missing, reinstall the WorkFrame/2 product then try the migration again. ═══ Message Help ═══ Explanation: Language profiles cannot be converted into actions profiles unless the WorkFrame/2* class DDE3Profile has been registered with the Workplace Shell. Recovery: If the WorkFrame/2 product was installed successfully, this class should exist unless it was deleted later. If the class is missing, reinstall the WorkFrame/2 product then try the migration again. ═══ Message Help ═══ Explanation: Information about the tools added to a previous version of the WorkFrame/2* product is kept in the initialization file, IBMWF.INI. This file could not be found in the directory you specified. Recovery: Verify that you specified the correct directory. If you cannot find the initialization file, add the tools to the Actions Profile manually. ═══ Message Help ═══ Explanation: The information describing which tools have been added to the previous version of WorkFrame/2* could not be found in the initialization file. Recovery: Add the tools to the Actions Profile manually. ═══ Message Help ═══ Explanation: Phase one of the WorkFrame/2* installation has successfully completed. You are now ready to start the second phase. Recovery: To exit the installation program, click on OK to return to the main installation window, and then select Close from the system menu. To reboot your system, select Shut down... from the Desktop's pop-up menu. Once the shut down has finished, restart your system. Phase 2 will begin automatically. Note: Shutting down make take a minute as some initialization files are being updated. ═══ Message Help ═══ Explanation: Phase 2 of the WorkFrame/2* installation has successfully completed, and all selected files and objects have been installed. Recovery: If you are reinstalling the WorkFrame/2 product, shut down and reboot once more to make your previous WorkFrame/2 projects and objects visible on the Desktop. Otherwise, you may begin to use the WorkFrame/2 environment. To exit the installation program, click on OK to return to the main installation window, and then select Close from the system menu. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation has successfully completed, and all selected files and objects have been installed. Recovery: If you are reinstalling the WorkFrame/2 product, shut down and reboot once more to make your previous WorkFrame/2 projects and objects visible on the Desktop. Otherwise, you may begin to use the WorkFrame/2 environment. To exit the installation program, click on OK to return to the main installation window, then select Close from the system menu. ═══ Message Help ═══ Explanation: Because of an operating system error, the WorkFrame/2* installation program was unable to get the maximum path length allowed, and cannot check the length of the path name specified. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible. Then restart the installation program and try again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program encountered an operating system error while checking for disk space. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible, and try the operation again. ═══ Message Help ═══ Explanation: The WorkFrame/2* program was interrupted by a file error while it was accessing the indicated file. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error if possible, and try the operation again. ═══ Message Help ═══ Explanation: This message occurred for one of the following reasons: o Some of the selected options may not have been installed because of file errors o Some files could not be unpacked using UNPACK.EXE o The target files are in use. The return code from UNPACK.EXE indicates the cause of the error. For more information about the UNPACK.EXE error return codes, refer to the OS/2* online information regarding UNPACK.EXE (type help unpack on the OS/2 command line). Recovery: First, ensure that you have Version 2.1 or higher of UNPACK.EXE. If you are reinstalling WorkFrame/2*, make sure that no part of the WorkFrame/2 product is in use. Then, click on Retry to try the operation again. ═══ Message Help ═══ Explanation: An error occurred while the WorkFrame/2* installation program was using UNPACK.EXE to unpack the WorkFrame/2 files. See the OS/2* Return Codes Help for more information on the error. Recovery: Make sure that UNPACK.EXE exists, and that its directory appears in the PATH statement in your CONFIG.SYS file. If you are reinstalling, make sure that no part of the WorkFrame/2 product is in use, then retry the operation. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program was stopped by a user action while the files were being unpacked. The return code from UNPACK.EXE indicates the reason the program ended. For more information about the UNPACK.EXE return codes, refer to the OS/2* online information regarding UNPACK.EXE (type help unpack on the OS/2 command line). Recovery: Try the installation again by clicking on Retry. If the error persists, click on Cancel to stop the installation program, then try the installation again. ═══ Message Help ═══ Explanation: The installation program cannot access the OS2.INI file, which contains information about what WorkFrame/2* files have already been installed. Recovery: Make sure there is available disk space, and that the OS2.INI file is not already in use. Then try the program again. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program encountered an unexpected error while loading the READ.ME file. See the OS/2* Return Codes Help for more information on the error. Recovery: Because the error may have affected the program, correct the error if possible, and try the operation again. ═══ Message Help ═══ Explanation: The installation program encountered errors while replacing a WorkFrame/2* module. Recovery: Select Retry to have the installation program try the operation again. If the error persists, select Cancel to terminate the installation program, then run the installation program again. If the error recurs, call your IBM* Service Representative. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program could not delete one or more temporary files. Recovery: Select Retry If this error persists, select Cancel, close the installation program, then run the installation program again. If the error recurs, call your IBM* Service Representative. ═══ Message Help ═══ Explanation: An error occurred while trying to delete the Installation Phase 2 self-startup program. This program must be removed manually after installation has successfully completed. Recovery: Follow these instructions to manually delete the Installation Phase 2 self-startup program from the OS/2* System Startup Folder after WorkFrame/2 installation is completed: 1. After you have finished installing, open the OS/2 System folder. 2. Open the Startup folder. 3. Delete the WorkFrame/2 Phase 2 object in the Startup folder. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program could not set the extended attributes for a file. See the OS/2* Return Codes Help for more information on the error. Recovery: Select Retry If this error persists, select Cancel, close the installation program, then run the installation program again. If the error recurs, call your IBM* Service Representative. ═══ Message Help ═══ Explanation: The WorkFrame/2* installation program could not allocate the memory required to migrate the files. Recovery: Select OK, close the installation program, then try the migration again. ═══ Message Help ═══ Explanation: This error occurred for one of the following reasons: o The WorkFrame/2* installation program was unable to find a base project file belonging to a composite project. It could be that there are no project files in the specified directory or that a composite project contains a base project that no longer exists. o The WorkFrame/2 migration program found version 1.0 or 1.1 project files in the specified directory, but a version 2.1 object with the same name already exists. It could be that the version 1.0 or 1.1 projects have already been migrated. Recovery: Select OK to display a window that lists the missing project files. Ensure all base project files exist in the specified directory for the composite project being migrated. If the project files have already been migrated, and you want to migrate the project files again, delete the created WorkFrame/2 Version 2.1 objects and start the migration again. ═══ Message Help ═══ Explanation: You have indicated that you want to deregister the WorkFrame/2* product from the OS/2* Desktop. Recovery: Select Yes if you want to go ahead with the deregistration; select No to cancel the WorkFrame/2 operation. ═══ Message Help ═══ Explanation: Unexpected errors were encountered while performing Undo Installation. Recovery: Select OK to stop the Undo Installation process, then try running Undo Installation again. If the error persists, reboot your system and try again. ═══ Message Help ═══ Explanation: UNPACK.EXE failed while trying to unpack files from the install disk to the target drive. The return code from UNPACK.EXE indicates the cause of the error. For more information about the UNPACK.EXE error return codes, refer to the OS/2* online information regarding UNPACK.EXE (type help unpack on the OS/2 command line). Recovery: Correct the error, if possible, then try the operation again by clicking on Retry. If the error persists, click on Cancel to stop the installation program, then try the installation again. ═══ Message Help ═══ Explanation: An unexpected error was encountered while trying to run UNPACK.EXE to unpack the files from the install disk to the target directory. See the OS/2* Return Codes Help for more information on the error. Recovery: Correct the error, if possible, then try the operation again by clicking on Retry. If the error persists, click on Cancel to stop the installation program, then try the installation again. ═══ Message Help ═══ Explanation: Invalid extended attributes were detected in one or more files. Some files may have been corrupted. See the OS/2* Return Codes Help for more information on the error. Recovery: Select OK to cancel the installation. Then, try to correct the error and start the WorkFrame/2* Setup program again. ═══ Message Help ═══ Explanation: Invalid extended attributes were detected in one or more files. See the OS/2* Return Codes Help for more information on the error. Recovery: Select OK to cancel the installation. Then, try to correct the error and start the WorkFrame/2* Setup program again. ═══ Message Help ═══ Explanation: The specified target directory for WorkFrame/2* installation is a network drive. Use Selective Setup to set up a user to share the WorkFrame/2 product from a LAN workstation. Recovery: Specify a local drive for the target directory, or use Selective Setup to install the IBM WorkFrame/2 application from a network. Click on the OK pushbutton to continue. ═══ Message Help ═══ The specified drive does not exist or is not ready. Recovery: Ensure that the specified drive exists, and that it is ready. Click on OK to return to the Installation Options window, then enter a valid drive. ═══ Message Help ═══ Explanation: A call to a DOS API failed during migration. Recovery: Select OK to terminate the migration process, then retry the migration operation. ═══ Message Help ═══ Explanation: The migration program encountered an unknown error while trying to load a list box. Recovery: Select OK to close the message box and terminate the migration process. Then, retry the operation. ═══ Message Help ═══ Explanation: The specified directory could not be found. Recovery Ensure that an existing directory containing project files is specified for the project. Click on OK to continue. ═══ Message Help ═══ Explanation: No project files or initialization (.INI) files containing information on tools to be migrated to WorkFrame/2 Version 2.1 were found in the specified directory. Recovery: Specify a directory containing the required project or initialization files. ═══ Message Help ═══ Explanation: A fully qualified path name (containing a directory and a file name or mask) was expected in the migration path entry field, but no directory name was found. Recovery: Click on OK to continue, then retry the operation entering a fully qualified path name in the entry field. ═══ Message Help ═══ Explanation: A fully qualified path name (containing a directory and a file name or mask) was expected in the migration path entry field, but no file name or mask was found. Recovery: Click on OK to continue, then retry the operation entering a fully qualified path name in the entry field. ═══ Message Help ═══ Explanation: The specified initialization (.INI) file was not found. Recovery: Ensure that the file exists in the specified path. ═══ Message Help ═══ Explanation: The Setup program was not able to write your specified settings to the OS2.INI file. Recovery: Make sure there is available disk space, and that the OS2.INI file is not already in use. Then try the operation again. ═══ Message Help ═══ Explanation: A call to a DOS API failed during migration. Recovery: Select OK to close the message box and terminate the migration process. Then, retry the operation. ═══ Message Help ═══ Explanation: All WorkFrame/2* Version 2.1 classes have been deregistered from the Workplace Shell, and all WorkFrame/2 objects have been made deletable. The WorkFrame/2 objects on the Desktop, and the files in the WorkFrame/2 directory still exist, but you may delete them if you want. Recovery: Delete the WorkFrame/2 files and objects if you want to remove the WorkFrame/2 product from your system. Otherwise, no action is required. Click on OK to continue. ═══ Message Help ═══ Explanation: Phase 1 of installation has completed successfully. Shutdown your system, then reboot. Phase 2 will start automatically after you reboot. Note: It could take up to three minutes for OS/2* to completely shut down your system after WorkFrame/2 Setup Phase 1 has completed. Recovery: Click on OK to continue. ═══ Message Help ═══ Explanation: A DOS API call failed while the Setup program was querying the OS/2* version installed on your system. Recovery: Click on OK to terminate WorkFrame/2 Setup program, then try running it again. ═══ Message Help ═══ Explanation: You do not have the required version of OS/2* installed in your system to correctly run the WorkFrame/2* application. Do you want to continue with the installation? Recovery: Click on Yes to install the WorkFrame/2 product anyway. However, you may experience unexpected errors if you run the WorkFrame/2 application under an incompatible version of OS/2. Click on No to terminate the installation. ═══ Message Help ═══ Explanation: An error occurred while trying to copy the indicated file to the target drive to perform a Copy Files operation. See the OS/2* Return Codes Help for more information on the error. Recovery: Ensure that all WorkFrame/2 objects are closed and that there is enough space in the target drive to copy the WorkFrame/2 files. Then, select Retry to try the operation again. If the error recurs, select Cancel to cancel the current operation and return to the previous screen, then try the Copy Files operation again. ═══ Message Help ═══ Explanation: A newly created folder or container could not be found due to an unknown error. Recovery: Click on Retry to try the operation again. If the error recurs, click on Cancel to terminate the installation, then reboot your system and try the installation again. ═══ Message Help ═══ Explanation: The installation program was unable to create a WorkFrame/2* class. Recovery: Click on the Retry pushbutton to have the installation program try the operation again. If the error persists, click on the Abort pushbutton to stop the installation. Then, try running the installation program again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: The installation program was unable to create a WorkFrame/2* object. Recovery: Click on Retry to have the Setup program try the operation again. If the error persists, click on the Abort push button to stop the installation, then try running the installation program again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: The installation program was unable to create a WorkFrame/2* object. Recovery: Click on the Retry pushbutton to try to create the object again. If the error persists, click on the Abort pushbutton to stop the installation, then try running the installation program again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: The installation program could not destroy the indicated WorkFrame/2* object. Recovery: Click on Retry If the error persists, click on Abort to stop the installation, then run the installation program again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: A newly created folder or container could not be found due to an unknown error. Recovery: Click on Retry to try the operation again. If the error recurs, click on Abort to terminate the installation, then reboot your system and try the installation again. You can also click on the Ignore pushbutton to have the Setup program ignore the error and continue with the installation, however, the associated feature will not be installed. ═══ Message Help ═══ Explanation: The icon file, DEFPRO.ICO, for the Default Actions Profile could not be found in the WorkFrame/2 root directory. The Setup program cannot recreate the Default Actions Profile without the icon file. Recovery: Ensure that the specified target directory is the main WorkFrame/2 directory then try the operation again. Click on Cancel to terminate the Update Default Actions Profile operation. ═══ Message Help ═══ Explanation: The indicated file could not be deleted by the Setup program. See the OS/2* Return Codes Help for more information on the error. Recovery: No action is required. Click on OK to continue. ═══ Message Help ═══ Explanation: A DOS API call to open the WFINST.INI file to load WorkFrame/2 Desktop data failed. Recovery: Click on OK to terminate the Setup program, ensure that the WFINST.INI file in the WorkFrame/2 root directory is valid, then try running Setup again. If the error persists, reboot your system and try running the Setup program again. ═══ Message Help ═══ Explanation: The WFINST.INI file is invalid. Recovery: Click on OK to terminate the Setup program, ensure that the WFINST.INI file in the WorkFrame/2 root directory is valid, then try running Setup again. If the error persists, reboot your system and try running the Setup program again. ═══ Message Help ═══ Explanation: The Setup program could not find the definition for the Default Actions Profile in the WFINST.INI file. Recovery: Click on OK to terminate the Setup program, ensure that the WFINST.INI file in the WorkFrame/2 root directory is valid, then try running Setup again. If the error persists, reboot your system and try running the Setup program again. ═══ ═══ A trademark of the IBM Corporation. ═══ ═══ Deregistration makes the Workplace Shell unaware of the WorkFrame/2 product while letting the WorkFrame/2 files and objects remain in the directory structure. You can delete them manually if you want.