═══ File Date Conflict ═══ A file to be transferred has an older date than a file of the same name that currently exists in the indicated destination directory. Select Yes to overwrite the newer, existing file. Select No if you do not want to overwrite the existing file, but want to continue with the file transfer. Select Cancel if you want to abort the file transfer. You may want to do this so that you can investigate the origin of the existing file before overwriting it. You can always restart the installation process after you have determined the origin of the existing file. Note: If OS/tools** DLL file names conflict with DLLs from some other application we suggest that you select Cancel, go back to the Install Options dialog, and enter the same directory in "Transfer Libraries to:" field as in the "Transfer Programs... to:" field. Be sure to enter a directory that either does not yet exist, or contains only OS/tools files. If you KNOW a file that has a date conflict is part of a previous OS/tools application installation, you should choose to have the newest file remain in the destination directory (i.e., select No). You can prevent possible conflicts with previously installed OS/tools files by selecting Uninstall from the File menu before you select Transfer Files. The Uninstall menu item will only be available when there is a version of the COMi device driver currently loaded. FYI A Dynanmic Link Library file named "C215MT.DLL" is included with all OS/tools installation files. This file is provided by Borland International for distribution by developers using their 32-bit OS/2 compiler and tools. Be sure to retain the most recent version of this file. ═══ Configuration Complete ═══ A COMi initialization file has been successfully created or modified. In order for the serial device(s) you have defined to become accessable to applcations you must shut down this OS/2* session and re-boot. See "shutting down OS/2" in the Master Help Index for detailed instructions on shutting down an OS/2 session. ═══ Incomplete Installation ═══ No COMi initialization file has been created or modified. There must be at least one defined serial device in a COMi initialization file before COMi will be loaded at system start-up. ═══ Delete Access Denied ═══ One or more files were not deleted because they were being accessed by this or some other process. If one or more of the programs that were previously installed are running, you will not be able to delete those files or any DLLs, that they require to run. To complete the un-install process do the following: 1. Close this program. 2. Close all other programs installed by this program (i.e., all COMscope sessions) 3. Run the file "DEL_COMi.CMD from the root directory of your boot drive Example: [C:\]DEL_COMi It is recommended that you exit Install NOW, and complete the above instructions, BEFORE you continue installing any programs or files. This will insure that any outdated program files and DLLs WILL be deleted, allowing newer replacements to be installed Note: The file "DEL_COMi.CMD" will be automatically deleted as soon as you install any program or files from this installation program. * ═══ Delete Folder? ═══ A folder and program objects (icons) for OS/tools' programs were created during a prior installation of those programs. The program objects have already been deleted. Selecting Yes will cause the folder to be deleted, along with any object you may have dropped into it. The folder will be deleted even if you have renamed it, or have moved it from the Desktop. Selecting No will cause that folder to be left as is. Note: If you are unsure of the contents of the "OS/tools Utilities" folder you can open that folder now and move any remaining objects you wish to save, then select Yes to cause the "OS/tools Utilities" folder to be removed. ═══ Create New Path? ═══ If you select the Yes push button the path named in the message box will be created. If you select the Cancel push button you will be returned to the Install Options dialog box to allow you to select another path. ═══ Cannot Open CONFIG.SYS ═══ Your system configuration file (CONFIG.SYS) may have been opened by another process. You will have to manually remove any DEVICE=d:\path\comdd.SYS statements from your CONFIG.SYS to complete this uninstall process. ═══ Uninstall Request ═══ If you answer Yes all files that were transferred with the currently loaded COMi device driver will be deleted. COMscope normally creates a profile the first time it is run. All COMscope profiles will also be deleted. Unless you have added files and/or sub-directories to the installed program directory, that directory will be removed. Any "Library" directories created by INSTALL will also be deleted. In addition all DEVICE= statements placed into your CONFIG.SYS file by the device driver configuration process will be removed from your CONFIG.SYS file. Note: If you run INSTALL from the directory it was installed to (i.e., double-clicking the COMi Installation icon in the OS/tools folder), the files "INSTALL.EXE" and "INSTALL.HLP" will not be deleted. If you want these files deleted you must either delete them manually or run INSTALL from the distribution diskette or directory. ═══ Help for Install Options Dialog ═══ Either accept the directory path(s) suggested by Install or enter your choice(s}. Select the OS/tools** products you wish to install and/or transfer. If you want Install to create folders and icons for the program(s) you are installing then select the Create Desktop Folder and Program Objects checkbox. Note: If a previous version of an OS/tools device driver or is loaded, Install will suggest the path(s) in which the old device driver and releted files are located. Otherwise Install will suggest the default system path(s) on your boot drive. ═══ 1. Keys Help for Keys ═══ There is only one key used by Install: Press F3: to close or exit Install. You can also exit Install by selecting the File | Exit menu item, by selecting the Close item from the system menu pop-up, or by double clicking on the system menu button (upper left corner). ═══ 2. Help for OS/tools' Install ═══ OS/tools** Install is designed to ease installation and configuration of all OS/tools products. Install will copy all files required by the OS/tools product, or products, you have purchased to any drive or directory you specify. Install can create Desktop icons and/or folders for OS/tools products that require them. Install will also start any special programs required to complete the installation and configuration of OS/tools' products, after all files have been transferred. Well, what would you expect, it is just an installation program, and Thank You for purchasing OS/tools products. Related Information: o Installation Options o Choosing File Locations o Transferring Files o Configuring Device Drivers o Uninstalling ═══ 2.1. Uninstalling ═══ If you have a previously installed version of the COMi device driver loaded, or after you have successfully installed and configured this version, and re-started your computer, so that the new COMi device driver is loaded, the Files | Uninstall menu item will be available. Selecting Uninstall will: 1. Delete all files transferred from the distribution disk during the loaded COMi's installation process. 2. Remove all DEVICE= statements related to these programs from your CONFIG.SYS file. 3. Delete any desktop objects created during the install process. 4. Remove any directories that were created during the installation. Note: Directories will only be removed if you have not added any files other than those transferred during the install process. If a directory is not empty after all OS/tools' installed files are deleted, the directory will not be removed. For example: if you have saved COMscope I/O stream capture files in the COMscope default directory, those files will not be deleted, and Uninstall will not be able to remove that directory. If you run INSTALL from the directory you want to "uninstall" from (i.e., from the install object in the OS/tools folder), the files "INSTALL.EXE" and "INSTALL.HLP" will not be deleted. If you want these files deleted you will either have to run INSTALL from the distrubution diskette or directory, or delete those two files manually. FYI INSTALL queries a currently loaded COMi device driver to determine its location on disk. If there is a previously installed COMi version loaded, and there is an installed files log (INST INF.LOG) present in the loaded device driver's directory when INSTALL is started, the File | Uninstall menu item will be enabled. You may use "uninstall" to remove a previous COMi/COMscope installation's files any time that version of COMi is loaded, even after you have selected File | Trasnfer Files and the new installation has been transferred to your system. This is possible until you re-start your machine and the new version of COMi is loaded. ═══ 2.2. Selecting Installation Options ═══ Before you can cause Install to transfer files to your system you must select and/or set various installation options To select installation options: 1. Select File 2. Select Install Options... ═══ 2.3. Choosing File Locations ═══ If you are installing an OS/tools** device driver, COMi** for instance, you will have to select a program destination on a hard disk drive that is available during boot-up, preferably the drive your OS/2 system boots from. If you are installing an OS/tools application (i.e., COMscope** or TBOSsim**) that requires Dynamic Link Libraries to be transferred to your system, you will have to select a library destination that is either in the same directory as the OS/tools program(s) you are installing, or in a directory that is named (described) in the "LIBPATH" statement in your CONFIG.SYS file. The "\OS2\DLL" directory on your boot drive is the default directory suggested for library files by INSTALL. We suggest that you use this directory unless you have reason to believe there will be a file name conflict when using this directory. If there is a version of the COMi device driver currently installed, and loaded, INSTALL will suggest the directories in which the loaded device driver is currently installed. You may enter other directory names. If you intend to "uninstall" a currently installed OS/tools product, you must select the Uninstall menu item before selecting the Transfer Files menu item. INSTALL will NOT add a path description to your CONFIG.SYS "LIBLATH" statement. ═══ 2.4. Transferring Files ═══ Install will copy, and unpack if necessary, all required files for any OS/tools product you are installing. To transfer files from the distribution disk: 1. Select File 2. Select Transfer Files Note: The Transfer Files menu item will not be available for selection until you have sucessfully selected Install Options. ═══ 2.5. Configuring Device Drivers ═══ Each OS/tools' device driver comes with a program to configure installation and start-up parameters for that device driver. In most cases, the configuration program is a Presentation Manager program. When this is the case that program in started by Install, as part of each installation process, with any parameters required for that particular installation. To start the configuration process for an OS/tools device driver: 1. Select Config 'driver'... Note: The Config 'driver'... menu item will only be available after you have successfully transferred all required device driver files from the distribution disk. ═══ ═══ Industry Standard Architecture or AT bus. Machines that are compatible with the IBM* AT* persional computer are of this type. ═══ ═══ MicroChannel* Architecture. Machines that are compatible with the IBM* PS/2* are of this type. ═══ ═══ You can check (select) a button either by clicking your left mouse button on the button or using the TAB key to move so the the required button has the focus then pressing the space bar. ═══ ═══ A symbol that shows that a menu choice is currently active. ═══ ═══ In OS/2*, applications and the various functions they need to operate can be linked at run-time. This means that program code that is seldom used can be stored on disk and loaded into memory only when it is required. It also makes it possible for mutiple applications to use the same program fragment to accomplish similar tasks. As a matter of fact all of the OS/2 Application Programming Interface is implemented as a set of Dynamic Link Libraries. This way the code that any application needs to accomplish common tasks need only be loaded once for all applications that may need to complete that task (i.e., read from, or write to, a file). ═══ ═══ IBM, AT, Micro Channel, and PS/2 are tradmarks of International Business Machines. ═══ ═══ OS/tools, COMi, COMscope, and TBOSsim are tradmarks of OS/tools Incorporated.