Convenience Package for OS/2 Warp(R) 4 README _____________________________________________ This README contains installation instructions and other information for the Convenience Package for IBM OS/2 Warp 4 (also called the "Convenience Package"). The Convenience Package for OS/2 Warp 4 provides updates and additional functions to IBM OS/2 Warp 4. In addition, the IBM OS/2 Developer's Toolkit has been included with the Convenience Package and can be installed separately. To install the Toolkit, change into the \toolkit directory on the Convenience Package for OS/2 Warp 4 Installation CD, and type TKINSTAL. Select the drive where you want to Toolkit installed and click on the Install button. After the installation completes, restart your system. For more details on installing the Toolkit, see the readme file in the \toolkit directory. Note that the Toolkit is only available in English. If there are any updates to this README information after the Convenience Package is shipped, they will be placed on the "Network Computing Software Support News" Web site (also called FIXNEWS). This Web site contains a list of Fix-related news items. The URL of the FIXNEWS Web site is: http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/fixnews.html CONTENTS ________ 1.0 System prerequisites 2.0 Installation instructions 2.1 Before installation 2.1.1 SOURCEPATH variable 2.1.2 Corrections to sample response files before CID installation 2.2 Starting installation with diskettes 2.2.1 Creating installation diskettes 2.2.2 Modifying the installation diskettes for new hardware 2.2.3 Starting the installation process with diskettes 2.3 Installing from CD 2.4 Installing Multimedia device support 2.5 Installing the Convenience Package over a Previous Version of OS/2 2.5.1 CHKINST 2.5.2 CONFIG.SYS File 2.5.3 Japanese printer drivers 2.5.4 PCMCIA 2.5.5 Response file migration 2.5.6 Multiple SOMIR statements in CONFIG.SYS 2.5.7 LAN Distance Remote Client 2.6 Installing a previous version of OS/2 after installing the Convenience Package 2.7 Installing on a hidden partition 2.8 Installing on an IBM ThinkPad(R) computer 2.8.1 Disabling busmastering on IBM ThinkPad computers 2.8.2 Reinstalling Crystal Audio drivers 2.9 Customizing installation through a command file 2.10 Troubleshooting installation 2.10.1 Migrating Multimedia support 2.10.2 Installing the Java(TM) demos on a drive other than the boot drive 2.10.3 WINOS2 installation dialog box 2.10.4 Volume and partition errors 2.10.5 IBM Ultrabay(TM) and external floppy problems on IBM ThinkPad 760ED computers 2.10.6 IBMLANLK log error 2.10.7 Setting the File and Print Sharing User ID and Password 3.0 Optional software 3.1 USB Support 3.2 PCI Yamaha YMF724 (DS-1) Audio 3.3 PCI Ensoniq ES1371 Audio 3.4 Options for the IBM ThinkPad computer 3.5 Macromedia Flash Player 4.0 Installing other software 4.1 Installing IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 4.1.1 Setting up font directories for OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 4.2 Installing Java 1.1.8 Components 4.3 Installing Virtual Private Networks and Network File Systems 5.0 New and updated features 5.1 Additional network adapter support for Remote IPL (RIPL) clients 5.2 Additional Adaptec driver support 5.3 New driver for when resetting system to VGA mode 5.4 New RAS utilities 5.5 New REXX functions 5.6 JFS Lazywrite parameters in CONFIG.SYS 6.0 Troubleshooting 6.1 Application and Component Considerations 6.1.1 IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 incompatibilities 6.1.2 Changing the LIBPATH after installing Lotus Notes(R) Domino(TM) Server 6.1.3 Network printing 6.1.4 StarOffice 5.1x 6.1.5 Power Management 6.1.6 Display Data Channel detection 6.1.7 DBCS language-specific fonts 6.1.8 FTP 6.1.9 OS/2 Window default size 6.1.10 Products that add locked device driver statements 6.1.11 Lotus Domino Go Webserver DLLs 6.1.12 TCP/IP NFS and IBM VisualAge C++ compatibility problem 6.1.13 Tivoli Management Agent 6.1.14 TME 10 Distributed Monitoring 6.1.15 WorkSpace On-Demand 6.1.16 DBCS: Fonts are displayed incorrectly 6.1.17 Adobe Type Manager 6.1.18 WebSphere Application Server Standard Edition 3.02 for OS/2 6.1.19 Running JAVAKEY 6.1.20 Creating partitions with LVM command-line interface 6.1.21 Syntax Highlighting in DBCS version of EPM 6.2 Remote IPL 6.2.1 TR Shared RAM Token Ring Adapter on RIPL clients 6.2.2 RIPL clients must be restarted manually after running TCPCFG2 6.2.3 RIPLing a Convenience Package for OS/2 Warp 4 client 6.3 Commands, CONFIG.SYS statements, and Messages 6.3.1 Kernel file message 6.3.2 VIRTUALADDRESSLIMIT 6.3.3 XCOPY 6.4 Associated bitmap-fonts 6.5 Hardware device and device driver considerations 6.5.1 3Com Fast Etherlink XL network adapter boot problem 6.5.2 Dell OptiPlex GX110 6.5.3 Device driver adapters 6.5.4 IBM ISDN Co-Processor adapters 6.5.5 PCMCIA flash memory and hard disk support 6.5.6 Universal Serial Bus devices 7.0 Additional information included with this product 7.1 README files 7.2 Books 8.0 Notices 9.0 Trademarks _____________________________________________________________________ 1.0 SYSTEM PREREQUISITES _________________________ The following are the minimum system requirements for the Convenience Package: o 133 MHz Intel-compatible Pentium(R) system o 32 MB RAM (minimum); 64 MB recommended o 250 MB for the base installation plus default installed components; 500 MB recommended If you are running one of the following operating systems, you can "migrate" your system--that is, you can install the Convenience Package on top of your existing operating system: Warp 3 Warp Connect Warp Server Client Warp 4 If you are not running one of these operating systems, it is recommended that you format the partition where you plan to install the Convenience Package instead of installing the Convenience Package directly over an existing copy of the operating system. 2.0 INSTALLATION INSTRUCTIONS ______________________________ If you are doing a Configuration, Installation and Distribution (CID) installation, start with the section titled "Before installation." If your system can boot from a CD, skip to the section titled "Installing from CD." If you have problems installing the Convenience Package from CD, follow the instructions below about creating and using installation diskettes. If you need to create installation diskettes to start the installation process, start with the section titled "Starting installation with diskettes," and then proceed to the "Installing from CD" section. If you are installing over a previous version of the operating system (also referred to in this document as "migration"), it is important that you follow the steps in this README file, including ensuring that the Multimedia Device Support field on the System Configuration panel is set to "None" during the initial migration. Multimedia Support requires a second installation step, after completing installation of the base operating system, using Selective Install. See Step 7 under "Installing from CD" and the section titled "Migrating Multimedia Support." Note: If you are installing over an previous version of OS/2, you should back up your system before installing the Convenience Package. 2.1 Before installation ----------------------- This section provides information about the installation of the Convenience Package that you will need before you install. Read this section prior to installing this product. 2.1.1 SOURCEPATH variable ------------------------- For a CID installation using RSPINST.EXE, you must define the SOURCEPATH variable in both the response file and in the CONFIG.SYS file. In the response file (MCP.RS) make sure a line appears that is similar to the following line: SourcePath=D:\OS2IMAGE Where D: is the drive letter assigned to your CD-ROM drive. In the CONFIG.SYS file make sure a line appears that is similar to the following line: SET SOURCEPATH=D:\OS2IMAGE Where D: is the drive letter assigned to your CD-ROM drive. 2.1.2 Corrections to sample response files before CID installation ----------------------------------------------------------------- If you are doing a CID installation on OS/2 Warp 4, you need to check the sample response files provided for CID installations of the base OS/2 operating system (\SAMPLE.RSP and \CID\EXE\OS2\SAMPLE.RSP). Some keywords are present in the file that are only pertinent to the server version of the product, OS/2 Warp Server for e-business. These keywords are: Smp= SMPPath=C:\OS2\BOOT Before using the response files to install the Convenience Package for OS/2 Warp 4, edit the SAMPLE.RSP file using a text editor, search for these keywords, and comment the statements out by placing an asterisk ('*') at the beginning of the line containing the statement. 2.2 Starting installation with diskettes ---------------------------------------- To create installation diskettes for installing the Convenience Package, start with the section titled "Creating installation diskettes". If you need to modify the diskettes for your particular system hardware, see the sections under "Modifying the installation diskettes for new hardware." 2.2.1 Creating installation diskettes -------------------------------------- If your system cannot boot from the Convenience Package for OS/2 Warp 4 Installation CD, or if you need to add device drivers before you begin installation, you must create installation diskettes to start your system and begin the installation process. You can create installation diskettes on any system that is already started and that has a diskette drive and a CD-ROM drive. To create installation diskettes: 1. Gather three blank diskettes and the Convenience Package for OS/2 Warp 4 CD 2. Label the three diskettes as follows: - Installation Diskette - Diskette 1 - Diskette 2 3. Insert the Convenience Package for OS/2 Warp 4 CD. 4. Open an OS/2 window. 5. From an OS/2 command prompt, type e: and press Enter (where e: is the drive letter of the CD-ROM drive). 6. At the OS/2 command prompt, type CDINST and press Enter. 7. At the prompt "Press any key when ready", press a key. 8. Insert the blank diskette labeled Diskette 1 and press Enter to copy the files. 9. Remove Diskette 1 from the diskette drive and press Enter. 10. Insert the blank diskette labeled Diskette 2 and press Enter to copy the files. 11. Remove Diskette 2 from the diskette drive and press Enter. 12. Insert the blank diskette labeled Installation Diskette into the diskette drive and press Enter to copy the files. NOTE: You are prompted to leave the Installation Diskette in the diskette drive and to restart the system. Do NOT follow the prompt. Instead, continue as instructed below. 13. Remove the Installation Diskette from the diskette drive and press Enter. 14. Close the OS/2 window. Now that the installation diskettes are created, you can either add device drivers to them, or you can start the installation process. To modify the installation diskettes for your particular system--for example, to add device drivers to the diskettes--see "Modifying the installation diskettes for new hardware" and the sections that follow it. To start the installation process, see "Starting the installation process with diskettes". 2.2.2 Modifying the installation diskettes for new hardware ------------------------------------------------------------ The Convenience Package includes support for many device drivers. If, however, support for your hardware is not included, you need to create installation diskettes, and then add the necessary device drivers to the installation diskettes before starting installation. For example, you might have a hard disk controller with a CD-ROM drive attached to it that is not supported by the operating system. If during the installation process you receive a message stating that your CD-ROM drive is not supported, or if you are prompted to insert the CD-ROM, the necessary device driver is probably not on the installation diskettes. To locate the device driver you need, either contact the manufacturer of the device or see the OS/2 Device Driver Pak Online at the following address: http://service.software.ibm.com/os2ddpak/index.htm Graphics adapter device drivers (GRADD) and other video drivers can be found via the internet at: http://service.software.ibm.com/ps.ww/countries After you obtain the appropriate device driver, you can modify the installation diskettes to support the new hardware in one of the following ways: o Add a device driver to the installation diskettes. o Replace a device driver on the installation diskettes. o Add parameters to existing device drivers. o If there is not enough space on the installation diskettes to copy the new device driver, see "Creating Space on the installation diskettes for device drivers." o If you want to replace one or more system files with a newer version, see "Replacing system files on the installation diskette." Remember, if anything goes wrong, you can always recreate the installation diskettes. See "Creating installation diskettes" for information on how. 2.2.2.1 Adding a device driver to the installation diskettes ------------------------------------------------------------- Use this procedure when the device driver is new or is not included with the Convenience Package. If there is not enough space on the installation diskettes to copy the new device driver, see "Creating space on the installation diskettes for device drivers." To add a new device driver to the installation diskettes: 1. If your device driver requires a BASEDEV= statement in the CONFIG.SYS file, add your device driver to Diskette 1. Otherwise, the device driver uses a DEVICE= statement and is copied to Diskette 2. 2. Modify the CONFIG.SYS file on Diskette 1 as follows: a. Make sure the following statement exists in the CONFIG.SYS file: SET SAVECONNECT=1 b. Add the following statement to ensure that the device driver is copied throughout the installation process: SET COPYFROMFLOPPY=1 c. Add the appropriate statements to the CONFIG.SYS file: BASEDEV=driver_name DEVICE=driver_name NOTE: If the connection to the hard disk or CD-ROM drive is lost during the installation process or when you restart your system, make sure the CD-ROM device driver statement is in the CONFIG.SYS file on the correct diskette, and make sure that the CD-ROM device driver is copied to the \OS2\BOOT directory. All device driver statements must include path information, such as DEVICE=C:\OS2\BOOT\COM.SYS. 2.2.2.2 Replacing a device driver on the installation diskettes ---------------------------------------------------------------- Use this procedure to install a newer version of a device driver that was included with the Convenience Package. If there is not enough space on the installation diskettes to copy the new device driver, see "Creating space on the installation diskettes for device drivers." To replace a device driver that resides on Diskette 1 or Diskette 2: 1. Copy the new device driver file over the existing file on Diskette 1 or Diskette 2. 2. Add the following statement to the CONFIG.SYS file on Diskette 1: SET COPYFROMFLOPPY=1 The installation program uses the new device driver and copies the necessary files to the target volume. 2.2.2.3 Adding or modifying parameters for existing device drivers ------------------------------------------------------------------- Use this procedure when you need to add or modify parameters to existing device drivers and these parameters must be copied to the target volume during installation. To add or modify parameters for existing device drivers, modify the CONFIG.SYS file on Diskette 1 as follows: a. Add or modify the required parameters for the device driver's BASEDEV= and DEVICE= statements. b. Make sure that the following statement exists in the CONFIG.SYS file on Diskette 1: SET SAVECONNECT=1 The installation program copies the modified lines to the CONFIG.SYS file on the target volume. 2.2.2.4 Creating space on the installation diskettes for device drivers ------------------------------------------------------------------------ If you need to create free space on Diskette 1, depending on your system hardware configuration, you can try one or more of the following procedures before you copy the new device drivers to the installation diskettes. For each file you delete from the diskette, you must also remove or comment out the corresponding statement from the CONFIG.SYS file and from the SNOOP.LST file. o If you are installing the Convenience Package on a system that does not have a SCSI (Small Computer System Interface) adapter, you can delete one or more of the following files to free up to 600KB of diskette space: AHA152X.ADD DPT20XX.ADD AHA154X.ADD FLASHPT.ADD AHA164X.ADD IBM2SCSI.ADD AHA174X.ADD QL10OS2.ADD AIC7770.ADD QL40OS2.ADD AIC7870.ADD QL510.ADD AIC78U2.ADD o If you are installing the Convenience Package on a SCSI system, determine which SCSI adapter you are using, and remove the SCSI drivers that you are not using. If you have a problem starting the system after removing the SCSI drivers, you have removed the wrong drivers from Diskette 1. Copy the SCSI drivers from the original Diskette 1 to the Diskette 1 you modified. o If you are not using a RAID (Redundant Array of Independent Disks) array system, you can remove the following files to free 45KB of diskette space: DAC960.ADD IPSRAID.ADD If you need to create free space on Diskette 2, you can remove certain files before you copy the new device drivers to the installation diskettes. To avoid installation problems, do not remove any files other than the ones listed below: Remove one or more of the following files to free up to 89KB of diskette space: TEDIT.EXE TEDIT.HLP RMVIEW.EXE RMINFO.DLL NPXEMLTR.DLL 2.2.2.5 Replacing system files on the installation diskettes ------------------------------------------------------------- Use this procedure to install a newer version of one or more of the system files included on the Installation Diskette. The system files include the following: OS2KRNLI OS2LDR OS2LDR.MSG OS2BOOT To add a new system file or files to the Installation Diskette: 1. Copy the new system file or files over the existing file or files on the Installation Diskette. 2. Add the following statement to the CONFIG.SYS file on Diskette 1 to ensure that the new system file or files are copied throughout the installation process: SET COPYFROMFLOPPY=1 2.2.3 Starting the installation process with diskettes ------------------------------------------------------ To begin the installation process: 1. Gather the Installation Diskette, Diskette 1, Diskette 2, and the Convenience Package for OS/2 Warp 4 CD. 2. Insert the Installation Diskette. 3. Insert the Convenience Package for OS/2 Warp 4 CD. 4. Turn on or restart the system. 5. From here, proceed as indicated under "Installing from CD," picking up at step 3. For more information, refer to the online help screens by pressing F1. 2.3 Installing from CD ---------------------- To install the Convenience Package: 1. Insert the Convenience Package for OS/2 Warp 4 Installation CD and restart the system. 2. When prompted, remove the CD, insert the Convenience Package for OS/2 Warp 4 CD, and press Enter. 3. Follow the prompts on the screen as directed. For more information, refer to the online help screens by pressing F1. 4. When the "Installation Volume Selection" panel is displayed, choose to accept the default volume or to specify a different volume for the installation and press Enter. NOTES: o If you are installing the Convenience Package on a system without an existing operating system, choose to specify a different volume. Doing so will start the Logical Volume Manager (LVM) and enable you to create a new volume for the installation. After you create a new volume and exit LVM, installation continues. o If you specify a different volume as the installation volume, the partition must be set to installable. You can set the partition to be installable with LVM. 5. Select one of the following formatting options to format the installation volume and press Enter: Do not format the volume. Perform a long format. Perform a quick format. 6. If you selected either a long or quick format, select the file system for the installation volume and press Enter. A pop-up warning about overwriting existing data is displayed. Click OK. The installation volume is formatted. When the format is complete, the system is automatically restarted and installation continues. 7. On the System Configuration panels, specify the hardware and country options that you want and click Next. For information about these options, click Help. If you are installing over a previous version of the operating system, make sure the Multimedia Device Support field on the System Configuration panel is set to "None." Multimedia Support requires a second installation step, using Selective Install, after completing installation of the base operating system. See "Migrating Multimedia Support." This step is not necessary if you are formatting your install partition before installation. 8. On the Setup and Installation panels, select the operating system features (such as printer utilities, or a development kit such as the IBM OS/2 Warp Developer Kit, Java(TM) Edition, Version 1.1.8) to install and click Next. For information about these features, click Help. For additional information, click More. If you want Multimedia Software Support you should select the Multimedia Software Support check box, even if you selected "None" in the Multimedia Device Support field in step 7. Note: Multimedia must be installed on the boot drive of the system. 9. Click Next to begin component installation. 10. Enter your name and company information into the appropriate fields and click Next. 11. Select the services that you want to install and click Next. For information about these services, click Help. 12. The Configuration panel is displayed. The installation items that you can configure are listed on the left side of the window. The items with green check marks next to them are correctly configured. Any item with a red arrow next to it must be configured. To configure an item: a. Click the item that you want to configure. The configuration options for that item are displayed on the right side of the window. b. Make your configuration choices for the item. c. When you are finished, click another item from the list to configure. 13. Click Install, and then click OK to complete the installation. NOTE: Your system is restarted automatically twice during the last phase of installation. 2.4 Installing Multimedia device support ---------------------------------------- This section applies if you are formatting your install partition before you install the Convenience Package. If you are installing the Convenience Package over an existing operating system (also called "migration"), see "Migrating Multimedia support." The installation process does not automatically detect multimedia devices (audio cards); therefore, you must manually select the Multimedia Device Support option during installation if you want to install support for your device and configure its settings. If you choose not to install support for your multimedia device during installation, you can set the operating system to automatically detect the device and configure its settings after installation, as follows: 1. Delete the AUDFSAFE.TXT file from the OS2\INSTALL directory in the installation volume. For example, if you installed the operating system on volume D:, delete the AUDFSAFE.TXT file from the D:\OS2\INSTALL directory. 2. From the Desktop, double-click OS/2 System. 3. Double-click System Setup. 4. Double-click Install/Remove. 5. Double-click Selective Install. The System Configuration window is displayed. 6. Click Multimedia Device Support to install multimedia device drivers and configure the settings. Click Next. Continue through the subsequent windows until the installation has completed. Note: Multimedia must be installed on the boot drive of the system. 2.5 Installing the Convenience Package over a previous version of OS/2 ----------------------------------------------------------------------- Read the following information if you are installing the Convenience Package over a previous version of OS/2. 2.5.1 CHKINST ------------- If CHKINST, a migration utility that scans your system for potential migration problems (such as corrupt partitions or LVM-incompatible volumes), fails, check that: 1. Syntax and parameters passed to CHKINST are correct. 2. VCU.EXE and VCU.MSG are in the directory where you are using CHKINST. If these files are not in the directory, copy them from the root directory of the CD. 2.5.2 CONFIG.SYS ---------------- If you are installing the Convenience Package over a previous version of OS/2, the installation process automatically migrates your existing CONFIG.SYS file. However, if you changed any of the following statements, the changes are not migrated. o BUFFERS o FILES o IFS o IOPL o SET o AUTOSTART o SET RESTARTOBJECTS o Other statements that have been added by applications In audio device driver statements, parameters added after the Device Name parameter are not migrated. For example, in a Pro Audio Spectrum device driver statement, parameters after PAS161$ are not migrated. To preserve your changes to these statements you must manually migrate your CONFIG.SYS file. 2.5.3 Japanese printer drivers ------------------------------- If you are using Japanese 16-bit printer drivers (DESKJET.DRV, EPSON.DRV,ESCPAGE.DRV, PMLIPS3.DRV or PSCRIPT.DRV) on your current system and you plan to migrate your system to the Convenience Package without formatting, you must manually replace the 16-bit drivers with 32-bit drivers. All the printers supported by 16-bit drivers are supported by 32-bit drivers. Below are the 16-bit printer drivers and their newer equivalents: 16 bit driver 32-bit driver -------------- ---------------- DESKJET.DRV --> OMNI.DRV EPSON.DRV --> OMNI.DRV ESCPAGE.DRV --> OMNI.DRV PMLIPS3.DRV --> OMNI.DRV PSCRIPT.DRV --> PSCRIPT2.DRV To install the 32-bit drivers during installation, select from the proper printer model in printer selection panel and continue to install. To install the 32-bit drivers after installation, use "Selective installation" and select the appropriate printer model you want. NOTE: OS/2 clients and server must use the same level printer drivers. 2.5.4 PCMCIA ------------ Before installing the Convenience Package over an existing version of OS/2 on a system with PCMCIA support installed, edit the CONFIG.SYS file and remove or comment out lines that contain any of the following driver names: o PCMSSDIF.SYS o PCM2SRAM.SYS o FLSH2MTD.SYS o PCM2FLSH.SYS o PCM2ATA.ADD o OS2PCARD.SYS To comment out a line in the CONFIG.SYS file, add the keyword "REM" to the beginning of the line. Save the changed CONFIG.SYS file, and then shut down and restart the system. If any of these drivers are present, the file and print sharing client installation program will fail. 2.5.5 Response file migration ----------------------------- Before performing a response file migration, run CHKDSK on the drive where the operating system is installed to ensure that there are no errors in the file allocation table or directory. If errors are found in the file allocation table or directory, type the following command to repair those errors: CHKDSK C: /F where C: is the drive where the operating system is installed. NOTE: Using the /F parameter locks the drive that CHKDSK is scanning. Because of this, the drive to be fixed cannot be the startup drive or the drive that contains the CHKDSK program. For more information about CHKDSK, see the "Command Reference." 2.5.6 Multiple SOMIR statements in CONFIG.SYS ---------------------------------------------- If you are installing the Convenience Package over an existing copy of the OS/2 operating system, after installation is complete, you should check your CONFIG.SYS file to verify that you only have one "SET SOMIR=" statement. If you find more than one, you must merge the two copies into a single statement (eliminating any duplicate entries). 2.5.7 LAN Distance Remote Client --------------------------------- The LAN Distance Remote Client must be removed before you migrate to the Convenience Package. 2.6 Installing a previous version of OS/2 after installing the Convenience Package -------------------------------------------------------------- The Convenience Package for OS/2 Warp 4 uses the Logical Volume Manager (LVM) to configure and manage disk drives on the system. LVM replaces FDISK. Because of this, if you want to install an older version of OS/2 (such as OS/2 Warp 4.0) on the same computer as the Convenience Package, you need to use both LVM and FDISK during installation. After installation, use LVM for all disk management. To install a previous version of OS/2 on the same computer as the Convenience Package for OS/2 Warp 4: 1. From the Convenience Package for OS/2 Warp 4, use LVM to create an installable volume for the OS/2 version you want to install. a. Start LVM by typing the following command at the command line: lvm /si:fs /size:120 b. Install Boot Manager, if it is not already installed. c. Create a compatibility volume for the OS/2 version. d. Mark the compatibility volume as "installable." e. Save your changes and exit LVM. 2. Locate the installation diskettes for the OS/2 version. Replace all of the device drivers on the diskettes with their counterparts from the Convenience Package. Do not replace any of the device managers (.DMD files). 3. Add the following line to the CONFIG.SYS file on the OS/2 installation diskettes: SET COPYFROMFLOPPY=1 4. Install the OS/2 version. a. Boot the system using the OS/2 installation diskettes you updated in step 2. Begin the installation process. b. When you are asked to select a drive for the installation, do not accept the default. FDISK is displayed. c. Find the FDISK partition you marked installable with LVM. (It will appear with "--> LVM*" next to the name.) d. Use FDISK to mark this partition installable. Press F1 for help instructions on using FDISK. ATTENTION: Do not use FDISK to do anything other than mark the partition installable. e. Save and exit FDISK. The installation window is displayed. f. Accept the default drive and continue with the installation. ATTENTION: FDISK is not supported as part of the Convenience Package. Any use of it beyond the scope of these instructions could harm your system. Use LVM for any disk management. 2.7 Installing on a hidden partition ------------------------------------- If you are going to install the Convenience Package on a hidden primary partition on a machine with multiple, hidden, primary partitions, you must follow this procedure. This procedure is not necessary if you are installing on a logical drive in an extended partition. As you are going through the installation process, you will reach a screen that identifies the target partition where the operating system will be installed. Do not accept the default drive; it might be pointing at the wrong primary partition. Select the second option, "Select another drive," which will start the Logical Volume Manager (LVM) program. The last drive you booted from (usually C:), should be highlighted. If this is not the drive you intend to install to, Press ENTER and select 'HIDE DRIVE FROM OS/2'. Next, highlight the volume on which you want to install the operating system. Press ENTER and select 'CHANGE DRIVE LETTER'. The default should be "C:" and you should select it. Next select that the volume should be bootable, and supply a name for the Boot Manager menu. With the new C: still highlighted, press ENTER again, and set the drive 'Installable'. Next press F3 to exit LVM, saving the changes. You will have to restart the machine, as drive letters have changed. When you get back to the screen that identifies the target partition where the operating system will be installed, you can select the second option again, to check that the proper drive is selected. Then press F3 to return (you do not need to save again) and continue with installation. NOTE: After you have used LVM on your physical disk drives, you cannot use FDISK from Warp to work with your drives. The LVM program creates a compatibility volume, and replaces the drive names with '->LVM'. From this point on, you must use LVM to manage your disk partitions. 2.8 Installing on an IBM ThinkPad computer ------------------------------------------ The following IBM ThinkPad installation options are not supported on the Convenience Package for OS/2 Warp 4: o Warm Docking support o Infrared support If you are installing the Convenience Package over an earlier version of the operating sytem and have been using the TrackPoint 4 mouse driver, you will need to reinstall the driver after migration. See the section titled "TrackPoint 4" for installation instructions. 2.8.1 Disabling busmastering on IBM ThinkPad computers ------------------------------------------------------ If you are installing the Convenience Package on an IBM ThinkPad 600, 760, or 770 series system, you must first disable busmastering for the ThinkPad's IDE controller. By default, busmastering is enabled. If busmastering is not disabled, the following problems may occur: Extremely slow installation Prolonged hard disk activity Appearance of system stop during hard disk accesses System might trap on going into suspend mode To disable busmastering for the ThinkPad s IDE controller, you must modify the CONFIG.SYS file used during installation. This means that you must use diskettes to start the installation process. See the following sections for details: o "Creating installation diskettes," o "Adding or modifying parameters for existing device drivers," and o "Starting the installation process with diskettes." After you have created your installation diskettes, open the CONFIG.SYS file on Diskette 1 and change the existing BASEDEV statement from BASEDEV=IBM1S506.ADD to: BASEDEV=IBM1S506.ADD /A:0 /!BM After you have finished installing the Convenience Package, verify that the change is still present in the system's CONFIG.SYS file. If it is not, add it manually. 2.8.2 Reinstalling Crystal Audio drivers ----------------------------------------- If you are installing the Convenience Package over an existing copy of the OS/2 operating system on an IBM ThinkPad T20, T21, or 600X series system, you will have to reinstall the Crystal Audio drivers on your system after you have completed installation of the Convenience Package. 2.9 Customizing installation through a command file --------------------------------------------------- ATTENTION: This procedure is only for experienced REXX programmers. To automatically update or add additional device drivers and other system files during the initial installation and to prevent these device drivers from being replaced by older versions, write a REXX command file, INSTEXIT.CMD. This command file is executed at defined points during the installation process, accesses the hard disk of the target machine, and can make additional configuration changes or copy additional files. The INSTEXIT.CMD can be placed on any of the installation diskettes (and therefore is not applicable if you install using from CD). Installation phases -------------------- The INSTEXIT.CMD file is called during the different phases of installation. Those phases are described below: Phase 1: The installation volume is selected and formatted. The base OS/2 operating system files are copied. Phase 2: Hardware, software, and networking products are selected and configured. The remainder of the operating system is installed. Phase 3: Networking products are installed. INSTEXIT calls during installation ----------------------------------- The INSTEXIT.CMD file is called two times during installation; during phase 1 and during phase 3. It is also called once during Selective Install for Networking. o Phase 1: The installation program calls the INSTEXIT.CMD file before the first reboot during installation. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word PHASE1 to indicate the exit is being called in phase 1 of installation. Example call: instexit.cmd C E PHASE1 1>nul 2>&1 The INSTEXIT.CMD return code is logged in \IBMINST\LOGS\CONINST.LOG. After INSTEXIT.CMD is completed, installation continues. o Phase 3: The installation program calls the INSTEXIT.CMD file at the end of Phase 3 if the file exists in the root directory of the installation volume. If the file is found, the install shield is disabled. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word PHASE3 to indicate the exit is being called in Phase 3 of installation. Example call: instexit.cmd C E PHASE3 The INSTEXIT.CMD return code is logged in \OS2\INSTALL\NPINST.PRD. After INSTEXIT.CMD is completed, the install shield is restored and the system automatically restarts. o Selective Install for Networking: The installation program calls the INSTEXIT.CMD file at the end of Selective Install if the file exists in the root directory of the installation volume. If the file is found, the install shield is disabled. The following three parameters are passed: 1. The target drive letter (example C). 2. The CD-ROM drive letter (example E). 3. The word SELECT to indicate the exit is being called by Selective Install for Networking. Example call is instexit.cmd C E SELECT The INSTEXIT.CMD return code is logged in \OS2\INSTALL\NPINST.PRD. After INSTEXIT.CMD is completed, the install shield is restored and the system automatically restarts. NOTES: 1. You must remove the exit command at the end of installation or properly use the third input parameter to ensure proper processing in the exit for all three types of calls (Phase 1, Phase 3, and Selective Install for Networking). 2. During the call in Phase 3, some files for products installed might be locked until the system is restarted. 3. During Phase 1, user input prompts must be written using VIO calls. During Phase 3 and Selective Install for Networking, input can be made using REXX I/O methods. Alternately, REXX can call a program executable file to do user prompting. 4. The install shield is disabled during Phase 3 and Selective Install for Networking so your exit command can prompt users to insert your device driver diskette or provide other instructions. When the install shield is disabled, users can see the OS/2 Warp 4 Desktop. Discourage users from accessing the Desktop when the install shield is disabled. Sample INSTEXIT.CMD File ------------------------- You can use the following sample file as a template. -------------------------Sample file--------------------------- /* REXX COMMAND FILE */ /* Installation Exit */ parse arg targetdrive cddrive installphase if installphase = 'PHASE1' then do /* phase 1 processing */ end if installphase = 'PHASE3' | installphase = 'SELECT' then do /* phase 3 and selective install for networking processing */ end if installphase = 'PHASE3' then do /* phase 3 specific processing */ end return 0 --------------------------endfile------------------------------- 2.10 Troubleshooting installation --------------------------------- There are problems that might occur in certain circumstances during installation of the Convenience Package. This section lists some of the known installation problems. 2.10.1 Migrating Multimedia support ----------------------------------- Multimedia Support requires a second migration step after you have completed migrating the base operating system. Additional manual steps might also be necessary to install drivers and locate icons. 2.10.1.1 Migrating Multimedia ----------------------------- To migrate Multimedia Support: 1. Double click the OS/2 System folder, the System Setup folder, and the Install/Remove folder, and then start Selective Install. 2. On the first panel, System Configuration, click the icon to the left of the Multimedia Device Support field. A list of available drivers will be displayed. If you find the driver that you want to install, select it. If you don't, leave the selection blank. In either case, continue with Selective Installation to install the rest of the Multimedia Support. If the multimedia driver that you wanted to install was not in the list, see "Manually Installing Multimedia Drivers" for information on how to install your driver. 3. Click Next to continue with migration. 4. At the OS/2 Setup and Installation panel (the third panel), select the Multimedia Software Support check box. Note: Multimedia must be installed on the boot drive of the system. 5. Select Next to continue with Selective Installation. Follow the directions on the screen. 6. At the end of Selective Install, restart your system. The multimedia drivers should be working correctly. 2.10.1.2 Manually installing Multimedia drivers ----------------------------------------------- For multimedia drivers that do not work after migrating the Multimedia Support (for example, the VIDRMP.SYS driver for the Real Magic Pro card), you must install the drivers manually. To install multimedia drivers manually, have your diskette ready, and enter the MINSTALL command from an OS/2 Command Line window. Follow the directions on the screen to complete installation. 2.10.1.3 Recovering Multimedia icons ------------------------------------ If icons for some of the multimedia programs are missing, open the Previous Desktop folder and use, copy, or drag the icons from there to your new desktop. 2.10.2 Installing the Java demos on a drive other than the boot drive --------------------------------------------------------------------- If you do not install the IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 (Java Technology Edition) on the boot drive (for example, C:), the Java demos do not install correctly. If you install the Java Technology Edition on a drive other than the boot drive and you want the demos, you must install the Java Technology Edition using Selective Install. If you install the Java Technology Edition on the boot drive, the demos install correctly. 2.10.3 WINOS2 installation dialog box ------------------------------------- When installing one language's version of WINOS2 over another's, you might see a dialog box titled "Display Driver Install" displayed that notifies you that the version of a file being installed is older than the version of the file that is already installed. The dialog box prompts you for verification that you want to overwrite the target file. The correct response is to accept the version being installed. 2.10.4 Volume and partition errors ---------------------------------- You might experience problems during installation if your system BIOS is unable to handle Logical Block Addressing (LBA) for drives over a particular size. This may cause the following errors: o LVM does not allow bootable volumes to be created past the first 1024 cylinders of a disk, even though LBA mode is enabled in the BIOS. An error message might appear stating that bootable partitions must reside within the first 1024 cylinders of the disk. o Installation proceeds normally through the phase 1 (text mode). When you restart the system as instructed, any the following errors might occur. - "Missing operating system. System halted" message appears - Boot Manager reports "selected partition not formatted," even though the partition is formatted and can be accessed when the system is booted from diskettes. - Systems hangs at blinking cursor. "## OS/2" logo never appears. If any of these problems occur, try the following solutions: o Make sure LBA mode is enabled within the system BIOS for your system. See the documentation that came with your system for details on how to do this. NOTE: If you make changes to the LBA settings in BIOS, you must repartition the hard disk. o Contact the system manufacturer for a BIOS update. o Common drive "limits" are 4.3GB and 8.4GB for newer systems. Check the documentation that came with your system or with your system manufacturer to determine the largest bootable device that your system supports. o Put the boot volume within the first 2GB of the drive. o Disable LBA in the system BIOS, and ensure that the boot volume resides within the first 500M of the drive. NOTE: If you make changes to the LBA settings in BIOS, you must repartition the hard disk. o Some drives have jumpers that can be set to overcome incompatible BIOS. Check the drive documentation for details. NOTE: Setting these jumpers typically reduces the usable space on the drive and requires you to repartition the drive. 2.10.5 IBM Ultrabay(TM) and external floppy problems on IBM ThinkPad 760ED computers -------------------------------------------------------------------- If you install the Convenience Package over an existing copy of the operating system on an IBM 760ED ThinkPad computer, and you select the options to install support for Ultrabay and for an external floppy drive, the options might not install completely. If you have this problem, open the system's CONFIG.SYS file in a text editor and make the following two changes: o Locate the existing BASEDEV=IBM1FLPY.ADD statement and change it to: BASEDEV=IBM1FLPY.ADD /A:0 /FORCE:2 /U:0 /F:1.44MB /U:1 /F:1.44MB o Then, locate the existing BASEDEV=IBM1S506.ADD statement and change it to: BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI /FORCE 2.10.6 IBMLANLK log error ------------------------- When migrating from Warp Server acting as a client (that is, no server code, just the requester, the peer, or both) to the Convenience Package for OS/2 Warp 4, an error might occur in the log files stating: LSI0102: IBMLANLK detected errors processing c:\os2\install\IBMSHST.LOG You can ignore this error. 2.10.6 Setting the File and Print Sharing User ID and Password -------------------------------------------------------------- If you choose to install File and Print Sharing Services, during the configuration phase of installation you will be prompted for a user ID and password to be used for the administrator user ID for your workstation. No matter what you enter, the initial user ID and password will be set to one of the combinations in the table below, depending on the language you are installing. YOUR SYSTEM'S LANGUAGE USER ID PASSWORD ====================== ======== ======== Canadian French IDUTIL MOTDEPAS Catalan IDUSUAR CONTRASE Danish BRUGERID KODEORD English USERID PASSWORD Finnish OMATUNN TUNNSANA French IDUTIL MOTDEPAS German BENUTZER KENNWORT Italian ID CHIAVE Norwegian BRUKER PASSORD Spanish IDUSUAR CONTRASE Turkish KULLNC PAROLA All other languages USERID PASSWORD After installation is complete you can logon using the user ID and password from the table. As soon as you can, you should change the user ID's password, or create a new user ID and delete the original one with the User Profile Management tool. Note that this is your File and Print Sharing user ID, which is used to administer the sharing of your files or printer with other users on a peer-to-peer network connection. Your LAN user ID is not affected and will work normally. 3.0 OPTIONAL SOFTWARE ______________________ The Convenience Package CD includes support for the following optional software: Universal Serial Bus (USB) Devices ThinkPad TrackPoint 4 Mouse Ensoniq PCI audio adapters Yamaha PCI audio adapters 3.1 USB Support --------------- USB base device driver support must be installed before any other USB device drivers. The USB base device drivers support the keyboard, mouse, speakers, modem, floppy disk drives, LS-120 drives, ZIP 100 drives, and ZIP 250 drives. To install USB base device driver support: 1. Open the CONFIG.SYS file in a text editor. 2. Remove the "REM" keyword from the following statements: REM BASEDEV=USBUHCD.SYS REM BASEDEV=USBD.SYS /REQ:USBUHCD$ REM BASEDEV=USBHID.SYS REM BASEDEV=USBMSD.ADD REM DEVICE=x:\OS2\BOOT\USBKBD.SYS (where x: is the boot drive) REM DEVICE=x:\OS2\BOOT\USBMOUSE.SYS REM DEVICE=x:\OS2\BOOT\USBCOM.SYS 3. Save and close the file. 4. Restart the system. 3.1.1 USB Audio --------------- To install support for USB Audio: 1. Insert the Convenience Package for OS/2 Warp 4 CD. 2. At a command prompt, change to the x:\options\USBaudio directory, where x:\ is the CD-ROM drive. 3. Type MINSTALL. 3.1.2 USB printer support ------------------------- To install or upgrade USB printer support: 1. Open an OS/2 Command Line window. 2. Using the MD command, create a temporary work directory on your hard disk and CD into it. 3. From the newly created temporary work directory created in step 2, type the following command: x:\OPTIONS\USBPRINT\USBPRTyy Where x: is the drive letter assigned to your CD-ROM drive, and yy is the national language you wish to install (for example, set yy to EN to install English). 4. Open the existing printer object properties window. If you do not have an existing printer object, create a new one. 5. Select the Output Port page. 6. Right-click on the LPT1 port icon, and select the Install menu option. Once the dialog has opened, click the "Install new port" button. 7. Once the "Install New Port" dialog opens, select the "New port drivers" radio button in the Port Driver Selection section, and enter the path to your temporary working directory into the Directory field. 8. Click Refresh. 9. Select the USB port and click Install. 10. Shutdown and restart your operating system after you have finished. 3.1.3 USB port support for IBM ThinkPad docking stations -------------------------------------------------------- To support the USB port on ThinkPad docking stations: 1. Open the CONFIG.SYS file in a text editor. 2. Add the following statement: BASEDEV=USBUHCD2.SYS 3. Save and close the file. 3.2 PCI Yamaha YMF724 (DS-1) Audio ----------------------------------- To install support for PCI Yamaha YMF724 (DS-1) audio: 1. Insert the Convenience Package for OS/2 Warp 4 CD. 2. At a command prompt, change to the x:\options\Yamaha directory, where x:\ is the CD-ROM drive. 3. Type MINSTALL. 3.3 PCI Ensoniq ES1371 Audio ----------------------------- To install support for PCI Ensoniq ES1371 Audio: 1. Insert the Convenience Package for OS/2 Warp 4 CD. 2. At a command prompt, change to the x:\options\Ensoniq directory, where x:\ is the CD-ROM drive. 3. Type MINSTALL. 3.4 Options for IBM ThinkPad computer -------------------------------------- 3.4.1 TrackPoint 4 ------------------ To install ThinkPad TrackPoint 4 support: 1. Insert the Convenience Package for OS/2 Warp 4 CD. 2. At a command prompt, change to the x:\options\TP4 directory, where x:\ is the CD-ROM drive. 3. Type INSTALL. 3.5 Macromedia Flash Player --------------------------- The Macromedia Flash Player enables you to view internet multimedia Web sites that use Flash 4 technology based on the standard developed by Macromedia, Inc. To install: 1. Insert the Convenience Package CD. 2. At a command prompt, change to the x:\options\flash directory, where x:\ is the CD-ROM drive. 3. Type FLASHOS2. 4.0 INSTALLING OTHER SOFTWARE ______________________________ You might need to take some extra steps when installing certain other software packages on the Convenience Package for OS/2 Warp 4. 4.1 Installing IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 -------------------------------------------------------------------------- Netscape Communicator must be installed on your system before you can install IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 (IBM Developer Kit V1.3) on the Convenience Package. To install the IBM Developer Kit: 1. Insert the OS/2 Warp 4 CD. 2. Open an OS/2 window. 3. Type 'J13KICK' on the command line. 4. Follow the installation instructions on the screen. 4.1.1 Setting up font directories for OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 --------------------------------------------------------------- By default, OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 assumes that the system fonts are installed on the boot drive in the \PSFONTS directory. If you install fonts on other drives, including, for example, the \JAVA13\JRE\LIB\FONTS directory, you must set the JAVA_FONTS environment variable in the CONFIG.SYS file. For example, if you install OS/2 on the C: drive, then you install some Chinese OS/2 system fonts on the E: drive, then you install the Java fonts on the D: drive, you would need to use the JAVA_FONTS variable. Otherwise, the Chinese characters might not display correctly in programs that use the Java GUI (graphical user environment), such as TCPCFG2 or LVMGUI. To correct this, you would the following line to your CONFIG.SYS file: SET JAVA_FONTS=C:\PSFONTS;E:\PSFONTS;D:\JAVA13\JRE\LIB\FONTS; You must restart your system for the change to take effect. 4.2 Installing Java 1.1.8 Components ------------------------------------ The Convenience Package automatically installs the Java 1.1.8 Runtime, RMI Runtime and the Swing Runtime components. The runtime and toolkit components have been updated to the o118-20001004 service level. The Debugger, Toolkits and Samples are not automatically installed from the Convenience Package installation program. If you want to install these additional components, follow these steps: 1. Insert the Convenience Package for OS/2 Warp 4 CD. 2. Create a temporary directory, on a drive with approximately 100MB of free disk space. 3. CD into this directory, and run the following commands: y:\javainrt -d y:\javainsr -d -ov y:\javainrm -d -ov y:\javainst -d -ov y:\javaintk -d -ov where y:\ is the CD-ROM drive. 4. Type "install" from the temporary directory. This starts Netscape, which is used to install the rest of the Java components. 4.3 Installing Virtual Private Networks and Network File Systems ---------------------------------------------------------------- To install Virtual Private Network (VPN) or Network File System (NFS), invoke the TCP/IP installation program under \CID\SERVER\TCPAPPS of the Convenience Package for OS/2 Warp 4 CD by typing "install". For a CID installation, select these components in the TCP/IP CID Install response file. 5.0 NEW AND UPDATED FEATURES _____________________________ The Convenience Package includes many new or updated features. This section contains information about these features. 5.1 Additional network adapter support for Remote IPL (RIPL) clients -------------------------------------------------------------------- Support has been added for the IBM PCI Token-ring/IBM PCI Token-ring 2 adapters for OS/2 Warp 4 RIPL clients. 5.2 Additional Adaptec driver support ------------------------------------- The Convenience Package includes support for additional Adaptec AIC U160 SCSI controllers. The additional controllers are controlled by the Adaptec AICU160.ADD driver. The additional controllers are: AIC-7892 Single Channel PCI-to-Ultra160 SCSI ASIC AIC-7899 Dual Channel PCI-to-Ultra160 SCSI ASIC AHA-3960D/39160 Dual Channel 64-bit PCI-to-Ultra160 SCSI Adapter 29160 Single Channel 64-bit PCI-to-Ultra160 SCSI Adapter 29160N Single Channel 32-bit PCI-to-Ultra160 SCSI Adapter (OEM) 29160LP Single Channel 64-bit Low Profile PCI-to-Ultra160 SCSI Adapter Installation Instructions for the new driver: 1. Type CDINST from the CD-ROM drive to create boot diskettes. For additional information on creating installation diskettes, see "Creating installation diskettes." 2. Delete some of the files on Diskette 1 so that 160 KB of disk space is available on the diskette. For additional information on freeing up space on installation diskettes, see "Creating space on the installation diskettes for device drivers." 3. Copy the driver, AICU160.ADD onto Diskette 1. 4. Add the following lines to the top of the CONFIG.SYS file on Diskette 1: BASEDEV=AICU160.ADD SET COPYFROMFLOPPY=1 5. Boot from the Installation Diskettes you created in step 1. 6. Follow the installation instructions displayed on the screen. 5.3 New driver for when resetting system to VGA mode ---------------------------------------------------- When you press the Alt-F1 key during system startup, it takes you to the Recovery Choices screen. The F3 key, when pressed from the Recovery Choices screen, resets the system video mode during system startup. In previous releases of the operating system, the key's function was to "reset to VGA." In the Convenience Package this has been changed to reset to another general purpose display driver with a higher resolution and better color capabilities then VGA mode (the Recovery Choices screen still says "F3 - Reset primary video display to VGA and reboot", but the system will be reset to the new driver). The new driver is called the "Generic VESA Unaccelerated & VGA GRADDs." This default GRADD driver is also the driver now chosen by default on non-migration installations, when no other, more specific driver is available for your display adapter. The original VGA driver is still installed automatically for when using F4 from the Recovery Screen to go to the Maintenance Desktop. The original VGA driver is still available for trouble shooting purposes, by pressing Alt-F1 at system startup, then pressing F2 to get to an OS/2 command prompt, then entering the "SETVGA" command, and then typing "EXIT" to close the command prompt. Generally you will be able to use the new Alt-F1 and F3 at system startup whenever the documentation for another display driver requires you to "reset to VGA" prior to installing the driver. However, if you experience problems installing another display driver, then using SETVGA for "reset to VGA"--instead of Alt-F1 and F3--as part of the installation process for the other display driver might solve these problems. If you experience problems or are otherwise unsatisfied with the display driver chosen automatically for your display adapter by the install process, you can use Selective Install to choose either: Generic VESA Unaccelerated GRADD Generic VESA Unaccelerated & VGA GRADDs as a possibly slower, but generally dependable alternative. Alternatively, you can try the latest version of the IBM Special Edition of SciTech Display Doctor, or one of the other display drivers available through the OS/2 Device Driver Pak Online at the following Web site: http://service.software.ibm.com/os2ddpak/index.htm The README.TXT for that driver includes a continually updated extensive list of display adapters for which the driver provides support which generally includes hardware acceleration and selectable refresh rates. Updates to other display drivers are available at the same web address. 5.4 New RAS utilities --------------------- Two new RAS (reliability, availability, and serviceability) utilities are included: PSFILES.EXE and PSSEMS.EXE. PSFILES.EXE can dump out information about open files on the system. By default, it dumps out the information for all processes. Alternately, "PSFILES xxx" will dump out information for PID xxx (xxx is a hex number, e.g. from PSTAT). PSSEMS.EXE can dump out information about open 32 bit semaphores on the system By default it prints out all the shared (i.e. system-wide) semaphores. Usage is: pssems [/n] [hex_pid | /a] ; where /n suppresses shared semaphores and /a prints pruivate sems for all system processes. Note: These RAS Utilities are added to the OS2 directory on your system. 5.5 New REXX functions ---------------------- The Convenience Package includes several new REXX functions. SysQueryExtLIBPATH ------------------ Syntax: SysQueryExtLIBPATH(flag) Parameters flag - The flag controlling which extended LIBPATH should be returned: 'B' Return the BEGINLIBPATH setting. 'E' Return the ENDLIBPATH setting. Function: This function returns the current path to be searched before or after the system LIBPATH when locating DLLs. Examples: /* Show the current setting of the extended LIBPATH */ say "BEGINLIBPATH is:" SysQueryExtLIBPATH("B") say "ENDLIBPATH is: " SysQueryExtLIBPATH("E") Return: Current BEGINLIBPATH or ENDLIBPATH SysQuerySwitchList ------------------ Syntax: SysQuerySwitchList(stem, [flags]) Parameters: stem - The name of a REXX stem variable. SysQuerySwitchList sets REXX variable stem.0 to the number of Window List entries and stores the individual entries in stem.1 to stem.n. flags - Any combination of the following: 'I' Include invisible entries in the list. 'G' Include grayed entries in the list. 'N' Include entries in the list that are not jumpable. 'D' Return the list in the detailed form:PID SID Visibility Jumpable ProgType Name Function: obtains information about the entries in the Window List. By default only visible and jumpable entries will be returned. Examples: /* Type the Window List */ call SysQuerySwitchList "list." do i = 1 to list.0 say 'Entry' i 'is' list.i end Return: Returned values are directly taken from the SWCNTRL structure. For description of the possible values see the Presentation Manager Guide and Reference. SysSetExtLIBPATH ---------------- Syntax: SysSetExtLIBPATH([path],flag) Parameters: path - The extended LIBPATH string. The string can be up to 1024 characters long. The extended LIBPATH may contain the strings "%BEGINLIBPATH%" or "%ENDLIBPATH%" in which case the current values will be inserted in the resulting extended LIBPATH. However, if the resulting extended LIBPATH is longer than 1024 characters, the function will return an error. To remove the current extended LIBPATH you can specify an empty string or omit this parameter. flag - flag controlling which extended LIBPATH should be set: 'B' Set the BEGINLIBPATH. 'E' Set the ENDLIBPATH. Function: This function defines the current path to be searched before or after the system LIBPATH when locating DLLs. Examples: /* Add D:\TEST to BEGINLIBPATH and delete ENDLIBPATH */ Call SysSetExtLIBPATH "D:\TEST;%BEGINLIBPATH%", "B" Call SysSetExtLIBPATH , "E" Return: The OS/2 error code will be returned (0 if successful). SysSwitchSession ---------------- Syntax: SysSwitchSession(name) Parameters: name - name of the session to switch to. The name must match the appropriate program name as used in the Window List (see function SysQuerySwitchList). Function: This function makes a specific program the active program. Return: The function returns the error code from WinSwitchToProgram (0 if successful). SysDumpVariables ---------------- Syntax: result = SysDumpVariables([filename]) Parameters: filename - name of the file where variables are appended to (dump is written to STDOUT if omitted) Function: This function dumps all variables in the current scope either to the specified file (new data will be appended) or to STDOUT if the filename parameter is omitted. The format of the data is (one variable per line): Name=MYVAR, Value="This is the content of MYVAR" Examples: Call SysDumpVariables "MyVars.Lst" /* append vars to file */ Call SysDumpVariables /* list vars on STDOUT */ Return: 0 - dump completed OK -1 - failure during dump SysSetFileDateTime ------------------ Syntax: result = SysSetFileDateTime(filename [,newdate] [,newtime]) Parameters: filename - name of the file to update newdate - new date to set in format YYYY-MM-DD OS/2: (YYYY > 1980) Win: (YYYY > 1800) AIX/Linux: (YYYY > 1900) newtime - new time to set in format HH:MM:SS (24 hr format) Function: This function can be used to modify the "Last Modified" Date of the specified file. If no new date or new time is specified then the file date and time will be set to the current time (TOUCH). If only one of date or time is omitted then this parameter will be left unchanged. For OS/2 and Windows NT(R) the filename may also specify a directory name. This does not work with Windows(R) 95/98 or AIX/Linux however. The file you want to change must not be opened by another process or at least it must allow shared writes in order to update the timestamp. Examples: Call SysSetFileDateTime "MyFile.Log" /* touch file */ Call SysSetFileDateTime "MyFile.Log", "1998-12-17" Call SysSetFileDateTime "MyFile.Log",, "16:37:21" Call SysSetFileDateTime "MyFile.Log", "1998-12-17", "16:37:21" Call SysSetFileDateTime "C:\MyDir" /* touch dir on OS/2, NT */ Return: 0 - file date/time was updated correctly -1 - failure attribute update SysGetFileDateTime ------------------ Syntax: result = SysGetFileDateTime(filename [,timesel]) Parameters: filename - name of the file to query timesel - What filetime to query: CREATE/ACCESS/WRITE Function: The function call returns the selected file date time attribute of the specified file if this is supported by the operating and file system (e.g. FAT does not provide Create/Access). The selector for the time to be returned can be abbreviated with its first character. For OS/2 and Windows NT the filename may also specify a directory name. This does not work with Windows 95/98 or AIX/Linux however. The file you want to query must not be opened by another process or at least it must allow shared reads in order to query the timestamp. Examples: Say "File creation time:" SysGetFileDateTime("MyFile.Log", "C") Say "File last access time:" SysGetFileDateTime("MyFile.Log", "A") Say "File last update time:" SysGetFileDateTime("MyFile.Log", "W") Say "Directory creation time:" SysGetFileDateTime("C:\MyDir", "C") Return: -1 - file date/time query failed other - date and time as YYYY-MM-DD HH:MM:SS SysStemCopy ----------- Syntax: result = SysStemCopy(fromstem, tostem, [from], [to], [count] [,insert]) Parameters: fromstem - name of source stem tostem - - name of target stem from - first index in source stem to copy to - position where items are copied/inserted in target stem count - number of items to copy/insert insert - 'I' to indicate insert instead of 'O' overwrite Function: Copy elements from the source stem to the target stem. Elements in the source stem are copied starting at the from index (default 1) into the target stem beginning at the to index (default 1). The number of items to copy to the target stem can be specified with count (default is to copy all items in the source stem). You can optionally specify that the items should be inserted into the target stem at the position and the existing items will be shifted to the back accordingly. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Examples: Source.0 = 3 Source.1 = "Hello" Source.2 = "from" Source.3 = "REXX" Call SysStemCopy "Source.", "Target." Call SysStemCopy "Source.", "Target.", 1, 5, 2, "I" Return: 0 - stem copy was successful -1 - stem copy failed SysStemDelete ------------- Syntax: result = SysStemDelete(stem, startitem [,itemcount]) Parameters: stem - name of stem where item will be deleted startitem - index of item to delete itemcount - number of items to delete if more than 1 Function: Deletes the specified item at index startitem in the stem. If more than one item is to be deleted then the count of items can be specified as the third parameter. After deleting the requested items the stem will be compacted, that means items following the deleted items will be shifted up into the vacant positions. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Examples: Call SysStemDelete "MyStem.", 5 Call SysStemDelete "MyStem.", 5, 4 Return: 0 - delete was successful -1 - delete failed SysStemInsert ------------- Syntax: result = SysStemInsert(stem, position, value) Parameters: stem - name of stem where item will be inserted position - index where new item will be inserted value - new item value Function: A new item will be inserted at the specified position in the stem. All existing items in the stem from the specified position will be shifted up by one to make room for the new item. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Example: Call SysStemInsert "MyStem.", 5, "New value for item 5" Return: 0 - insert was successful -1 - insert failed SysStemSort ----------- Syntax: result = SysStemSort(stem, order, type, start, end, firstcol, lastcol) Parameters: stem - name of stem to sort order - 'A' or 'D' for sort order (default: ascending) type - 'C', 'I' for comparison type (case/ignore, default: case) start - first index to sort (default: 1) end - last index to sort (default: last item) firstcol - first column to use as sort key (default: 1) lastcol - last column to use as sort key (default: last column) Function: This call sorts all or the specified items in the stem. Sort order can be specified as ascending or descending, comparison type can respect or ignore the case of the strings being compared. The sorting can further be narrowed by specifying the first and last item to be sorted or by specifying the columns used as the sorting key. The sort uses a quicksort algorithm, so the order of equal elements according to the sort key is undetermined. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Examples: /* sort all elements descending, use cols 5 to 10 as key */ Call SysStemSort "MyStem.", "D",,,,5, 10 /* sort all elements ascending, ignore the case */ Call SysStemSort "MyStem.", "A", "I" /* sort elements 10 to 20 ascending, use cols 1 to 10 as key */ Call SysStemSort "MyStem.",,,10, 20, 1, 10 Return: 0 - sort was successful -1 - sort failed SysVersion ---------- Syntax: result = SysVersion() Parameters: None Function: This function returns a string to identify the operating system and its version. The returned string contains an identifier for the operating system as the first word and then the version in the second word. Examples: Say SysVersion() /* show OS and version */ Return: Operating system and version Possible output for operating systems supported by Object REXX: Say SysVersion() -> "WindowsNT 4.00" Say SysVersion() -> "OS/2 2.40" Say SysVersion() -> "AIX 4.2" Say SysVersion() -> "Linux 2.0.34" Note: This function can be used to replace the operating system specific functions SysOS2Ver(), SysWinVer(), and SysLinVer(). SysUtilVersion -------------- Syntax: result = SysUtilVersion() Parameters: None Function: This function returns a version number that identifies the current level of the REXX Utilities package. This can be used to verify that certain functions are available. Examples: Since this function was not part of the original packaging a sample logic to check for a certain level of REXXUTIL could look like this: If RxFuncQuery("SysUtilVersion") = 1 |, SysUtilVersion() < "2.00" Then Say "Your REXXUTIL.DLL is not at the current level" If a specific function should be used that was added at a later REXXUTIL level a similar check can be performed by querying that function: If RxFuncQuery("SysSetFileDateTime") = 1 Then Say "Your REXXUTIL.DLL is not at the current level" Return: REXXUTIL version number in the format (n.mm) 5.6 JFS Lazywrite parameters in CONFIG.SYS ------------------------------------------ The parameters for the Journaled File System (JFS) installable file system are as follows: IFS=jfs.ifs /L:OFF IFS=jfs.ifs /L:synctime,maxage,bufferidle (JFS ignores any characters between the L (or l) and the colon, so valid flags are /L: /LAZY: /LW: /lazywrite: etc.) OFF forces asynchronous writes to be immediately initiated. synctime is the interval at which the sync thread runs. Default = 64 maxage is the longest time that a frequently modified file is kept in cache. Default = synctime*4 bufferidle is the time indicating a "recent" change. Changes newer than this value are not written unless the last write was older than maxage. Default = MIN(1,synctime/8) (All parameters in seconds) IFS=C:\OS2\JFS.IFS /L:64 synctime = 32, maxage = 128, bufferidle = 4 IFS=C:\OS2\JFS.IFS /LW:10,60,5 synctime = 10, maxage = 60, bufferidle = 5 IFS=C:\OS2\JFS.IFS /LAZYWRITE:4,60 synctime = 4, maxage = 60, bufferidle = 1 IFS=C:\OS2\JFS.IFS /lazy:off All writes initiated immediately (synctime=1, maxage=bufferidle=0) Note: sync thread still runs since trivial things like marking an inode accessed are still deferred. The CACHEJFS.EXE command allows the lazywrite parameters to be changed immediately. The syntax is to the IFS line, except that the /L: prefix is optional. In addition, the CACHEJFS command can modify the minimum and maximum number of free cache buffers to be maintained. Calling CACHEJFS with no parameters reports the current settings. CACHEJFS [[/LAZYWRITE:]{OFF|syncTime[,maxAge[,bufferIdle]]}] /MINFREE:minfree /MAXFREE:maxfree 6.0 TROUBLESHOOTING ____________________ The following sections provide information about restrictions and potential problems that might occur after you have installed this product. 6.1 Application and component considerations -------------------------------------------- Read the following sections for information about the Convenience Package's components and applications. 6.1.1 IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 incompatibilities ----------------------------------------------------------------- The upgrade from IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 to IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 introduced many changes in the functional specification. These changes include renamed classes and deprecated APIs. Applications written for IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 might not run unchanged on IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3. It is recommended that you do not make IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 the default Java Virtual Machine on your system. 6.1.2 Changing the LIBPATH after installing Lotus Notes(R) Domino(TM) Server ---------------------------------------------------------------------------- After installing Lotus Notes(R) Domino Server 4.52 or 4.6x (also called Domino), you must manually adjust the LIBPATH in the CONFIG.SYS file. Domino inserts its DLL directories at the beginning of the LIBPATH, which causes a conflict with the IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 installed with the Convenience Pack. Move the Domino LIBPATH entry to after the JAVA11 path entries, or to the end of the LIBPATH, in the following manner: After Notes Installation: LIBPATH=c:\notes;C:\JAVA11\DLL;C:\JAVA11\ICATJAVA\DLL;... Manually change to: LIBPATH=C:\JAVA11\DLL;C:\JAVA11\ICATJAVA\DLL;...;c:\notes; 6.1.3 Network printing ---------------------- To use a network printer, the printer drivers on both the client and the server must be at the same level. 6.1.4 StarOffice 5.1x --------------------- StarOffice 5.10 does not install correctly; version 5.1A of StarOffice installs successfully. 6.1.5 Power Management ---------------------- The Convenience Package adds several power management functions in support of the Intel SpeedStep(R) power management technology. These functions enable you to fine-tune your system's power/performance behavior. The functions are accessible through the Power icon in the System Setup folder, in the following manner: o Open the Power object. The window displayed will contain a field titled "Power and Performance Optimization," which displays the current SpeedStep state. On systems which do not support SpeedStep technology, the state is always "Maximum Performance" and cannot be changed. o The system menu in the Power Window will have a "Performance" selection which enables you to toggle between two states: Battery Optimized and Maximum Performance. o If you right-click the Power icon and select Properties, the Properties notebook displayed has a tab named "Performance." Click the help button on the "Performance" page for more information on using the SpeedStep features. Note that SpeedStep functions are also displayed on systems that do not have SpeedStep-enabled processors. Altering SpeedStep settings on unsupported systems is harmless, but has no effect. Refer to your system's documentation to determine if it has a SpeedStep-enabled processor. 6.1.6 Display Data Channel detection ------------------------------------ Some computer monitors have an interface that enables the operating system to automatically determine the characteristics of the monitor. This interface is called a Display Data Channel (DDC). At times the information gathered by the operating system is not correct, and you must set the monitor characteristics manually. On the Convenience Package this will most often manifest itself on the Screen page of the System settings notebook (in the System Setup folder). The resolution or refresh rate or both might be blank or incorrect. If you experience this problem you can disable automatic detection by adding the following line to your CONFIG.SYS file: SET VCFG_NO_DDC=TRUE You must restart your system for the change to take effect. After restarting your system, go back to the Screen page in the System settings notebook, and manually select a monitor type. To do so: 1. Open the System settings notebook in the System Setup folder. 2. Click on the Screen tab along the top of the panel. 3. Click on the '+' on the folded-down-page icon in the top right corner of the Screen page to go to page 2. 4. Select your monitor type. 5. Close the System settings notebook and reopen it. 6. You should now see a correct list of available display modes. An example of this type of behavior is found in some models of IBM ThinkPad 770 computers, if you are using a Trident Cyber 9397 Family GRADD driver. The resolution and refresh rate fields on the Screen might be blank, preventing you from changing the display mode. If this is the case, use the solution above and in step 4 select "IBM ThinkPad 1024X768" for the monitor type. 6.1.7 DBCS language-specific fonts ----------------------------------- The Convenience Package includes fonts specifically designed for each Double-Byte Character Set (DBCS) country. Each font is dependent on information from the code page for which it was encoded. If you install a language-specific font on a system with a different language, the font names might appear incorrectly. If you need to display and print documents in multiple languages, use the Unicode encoded fonts, Monotype Sans Duospace WT and Times New Roman WT. You should install a font for a language different from your system's only if you need to print documents formatted on a client using that font. 6.1.8 FTP ---------- Some clients might have difficulty displaying directory information correctly when connecting to an OS/2 ftp server. In particular, the following problems might occur: o Directory listings might appear empty, even if there are files in the directory. o File names might appear as numbers. o File names in a directory might be missing or incorrect. To avoid these problems, try the following on the client: o Configure the server type in the client's preferences as "OS/2." If the OS/2 choice is not available or does not resolve the problem, try using one of the other system types. o If the ftp client does not have the above options, or if the problem still exists, have the client use FTP from the command line. 6.1.9 OS/2 Window default size ------------------------------- In OS/2 Warp 4.0 and later versions, OS/2 windows open maximized to a default position. If you run customized applications that require the window to open to a specific size, you can remove the default size. To remove the default window size and position: 1. Open an OS/2 command window. 2. Move the mouse pointer to the restore icon in the upper right corner of the window. 3. Press and hold the Shift key and right-click the restore icon. 4. Release the Shift key. 6.1.10 Products that add locked file device driver statements ------------------------------------------------------------- If you are installing a product (such as IBM eNetwork Communications Server V5.0) that adds locked file device driver statements to the CONFIG.SYS file, change the order of these statements before you restart your system. Locked file device driver statements must come after all IFS statements. For example, if you are installing IBM eNetwork Communications Server V5.0, your CONFIG.SYS file contains the following lines: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C Move the DEVICE and RUN statements after the IFS statements: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST NOTE: Each entry should be on only one line. The lines above are split for printability. 6.1.11 Lotus Domino Go Webserver DLLs ------------------------------------- If you install or have installed, version 4.6.2.6, or earlier, of Lotus Domino Go Webserver (LDGW) there might be conflicts with some of the DLLs installed. There are two solutions to this problem: o Move the \WWW\DLL that LDGW puts at the beginning of the LIBPATH statement in the CONFIG.SYS file to the end of the LIBPATH. o Delete any of the following files that exist in the \WWW\DLL directory that LDGW installs: API.DLL KEYMAN.DLL BERREAL.DLL NSPCOMMO.DLL CMPVAL.DLL OSSAPI.DLL CMSKEXP.DLL OSSDMEM.DLL CMSKUS.DLL PFX.DLL CPYVAL.DLL SKIT.DLL CSTRAIN.DLL SKIT33.DLL GSKOM30.DLL SOEDBER.DLL GSKSYS.DLL X509CMS.DLL IKMJNI.DLL 6.1.12 TCP/IP NFS and IBM VisualAge C++ compatibility problem ------------------------------------------------------------- If you receive a SYS3175 error when starting NFSD.EXE and you have VisualAge C++ installed, remove \IBMCPP\LOCALE from the SET LOCPATH statement in the CONFIG.SYS file and restart your system. 6.1.13 Tivoli Management Agent ------------------------------ When you uninstall Tivoli (TM) Management Agent, you will receive an incorrect EPFIE231 error message. Ignore this error. Also, if you uninstall TMA, not all the files are removed. You must manually remove the files in the \TIVOLI subdirectory. 6.1.14 TME 10 Distributed Monitoring ------------------------------------ If you are using TME 10 Distributed Monitoring to monitor an OS/2 Warp 4, you might receive an "Exit Code 1001" message. If this occurs, contact Tivoli support for a fix to Tivoli PMR 82307. 6.1.15 WorkSpace On-Demand -------------------------- The following sections contain information about WorkSpace On-Demand. Installing public applications ------------------------------- If you installed LAN Server RIPL support in a volume (other than 386 HPFS) and you want to install public applications (such as Lotus Notes) that use IBM Software Installer on a WorkSpace On-Demand client, you need to set the EPFINSTDIR parameter of the application's installation object to a directory where the client has write access. To set the EPFINSTDIR parameter: 1. Double-click LAN Server Administration. 2. Right-click the application's installation object. 3. On the Parameters page, set the EPFINSTDIR parameter to a directory where the WorkSpace On-Demand client has write access. For example, if a WorkSpace On-Demand client has the following FIT file entry: Z:\EPFTEMP \\\\ set the EPFINSTDIR parameter to Z:\EPFTEMP. WorkSpace On-Demand documentation ---------------------------------- If you are using the Convenience Package to remotely administer WorkSpace On-Demand servers and want access to the WorkSpace On-Demand documentation, you can copy the "WorkSpace On-Demand 2.0 Administrator's Guide" from the WorkSpace On-Demand 2.0 CD (\INSTALL\SERVER\NET\A4E11MST.INF). WorkSpace On-Demand 2.0 removal ------------------------------- When you uninstall WorkSpace On-Demand 2.0, you can reclaim the space allocated to the WorkSpace On-Demand 2.0 and WorkSpace On-Demand 2.0 client directory trees on the server as follows: 1. Log on the LAN with Administrator authority. 2. Delete all the WorkSpace On-Demand clients. 3. Delete all the WorkSpace 2.0 clients. 4. Log off the LAN and stop the server. To reclaim the space used by the WorkSpace On-Demand 2.0 files delete the following directory subtrees: \IBMLAN\RPL\BB20.cc \IBMLAN\RPL\MACHINES\BB20.cc \IBMLAN\RPL\MACHINES\MACADDR (if present) Where cc is the country code 6.1.16 DBCS: Fonts are displayed incorrectly -------------------------------------------- In DBCS countries, some fonts at some sizes might be displayed incorrectly. For example, the top of some DBCS characters might be cut off. In particular, this problem occurs with the "8.Helv" font. If this problem occurs, try changing to another font or font size. For this example, changing the "8.Helv" font to "8.Helv Combined" or "8.Helvetica" corrects the problem. 6.1.17 Adobe Type Manager ------------------------ For Adobe Type Manager font support in WIN-OS/2 for Thailand, enable the WIN_ATM setting for the WIN-OS/2 command prompts. 1. Right-click WIN-OS/2 Window in the Command Prompts folder and click Properties. 2. Click the Session tab. 3. Click WIN-OS/2 Properties. 4. Select WIN-OS/2 Settings and click OK. 5. Select WIN_ATM from the list and change the value to ON. 6. Save the settings and close the Properties notebook. 6.1.18 WebSphere Application Server Standard Edition 3.02 for OS/2 ------------------------------------------------------------------ If you receive an error message saying "Library file CPPOS2.DLL not found" when you install WebSphere Application Server Standard Edition 3.02 for OS/2 (WebSphere) it indicates an incompatibility with your system's default Java(TM) Virtual Machine (JVM). To correct the problem: 1. Open an OS/2 window 2. On the command line, type 'java -fullversion' to determine the system's default JVM. If it is the JVM from IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3, you must change the PATH statement in the CONFIG.SYS file. 3. Open the CONFIG.SYS file in a text editor. 4. Locate the following entries in the PATH and move them to the end of the PATH: x:\java13\jre\bin;x:\java13\bin 5. You will need to shutdown and restart your machine for the change to take effect. After rebooting, when the operating system searches the PATH for the JVM, the entry from IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 will be found first, and it's JVM used. After you have performed these steps, start the WebSphere installation program again. 6.1.19 Running JAVAKEY ---------------------- To run JAVAKEY, you must add the following line to the CONFIG.SYS file: SET SHELLHANDLESINC=10 6.1.20 Creating partitions with LVM command-line interface ---------------------------------------------------------- In order to create a partition using the LVM command line interface, the Free space ID parameter must not have any leading or trailing spaces between it and the surrounding commas. For example, the following line is incorrect: LVM /create : partition , a, 1, 100 , logical , bootable , [ FS1 ] , fromstart The following line is correct: LVM /create : partition , a, 1, 100 , logical , bootable ,[ FS1 ], fromstart 6.1.21 Syntax Highlighting in DBCS version of EPM ------------------------------------------------- If you are using the EPM editor to edit .CMD files on a DBCS version of the Convenience Package, some of the characters might not be visible if you are using Syntax Highlighting. The characters are present in the file, but they are not visible because they are displayed in the same color as the background. To correct this, you must edit the Syntax Highlighting configuration file that is used when you are editing .CMD files. On the boot drive of your system, change into the \OS2\APPS directory and edit a file named EPMKWDS.CMD. Once the file is open, search for lines whose last two entries are "-1" and "15." On each of those lines, change the 15 to a 12. This will make the text display in a color that is different from the background color, so it will be visible. 6.2 REMOTE IPL -------------- The following sections contain information about troubleshooting for Remote IPL (RIPL). There are two key points to make initially about Remote IPL: RIPLing a Convenience Package for OS/2 Warp 4 client ---------------------------------------------------- A Convenience Package for OS/2 Warp 4 client can be RIPLed only from a Convenience Package for OS/2 Warp Server for e-business server. RIPLing from a Convenience Package for OS/2 Warp Server for e-business server ------------------------------------------------------- A Convenience Package for OS/2 Warp Server for e-business server can RIPL either OS/2 Warp 4 clients or Convenience Package for OS/2 Warp 4 clients but not both at the same time. 6.2.1 TR Shared RAM Token Ring Adapter on RIPL clients ------------------------------------------------------ Using TR Shared RAM Token Ring adapters in both a RIPL server and a RIPL client might produce a trap when the RIPL client is started. This trap does not occur with every system restart. A simple workaround is to restart the RIPL client. A longer-term solution is to upgrade to a newer, PCI Token Ring card. 6.2.2 RIPL clients must be restarted manually after running TCPCFG2 ------------------------------------------------------------------- If you configure TCP/IP on a RIPL client that does not have the Boot Manager installed, you might have to reboot manually after completing TCP/IP configuration with TCPCFG2. At the end of TCP/IP configuration of a RIPLed client, a dialog box notifies you that the changes will not take affect until you reboot and that you should click the OK button to reboot the machine. However, clicking the OK button does not restart the machine. It returns you to the OS2 command prompt with the following message: Reboot Server Boot manager not installed If you get this message, restart your system manually. 6.2.3 RIPLing a Convenience Package for OS/2 Warp 4 client ----------------------------------------------------------- A Convenience Package for OS/2 Warp 4 client can be RIPLed only from a Convenience Package for OS/2 Warp Server for e-business server. 6.3 Commands, CONFIG.SYS statements, and Messages ------------------------------------------------- The following section contain information about OS/2 commands, CONFIG.SYS statements, and error messages. 6.3.1 Kernel file message ------------------------- If you receive the error message 'A kernel file is missing from the disk,' the missing file is one of the following: OS2KRNL, OS2LDR, OS2BOOT. These files are hidden in the root directory of the server. You will receive this message if you have deleted one of these files or if your disk becomes corrupt. If your disk is corrupted, replacing the files might or might not fix the problem. 6.3.2 VIRTUALADDRESSLIMIT ------------------------- The default value of the VIRTUALADDRESSLIMIT CONFIG.SYS statement has been changed from 2048 (2 gigabytes) to 1024 (1 gigabyte). 6.3.3 XCOPY ----------- In the XCOPY command syntax using the /S and /E parameters together, if a source is specified without a trailing backslash "\", (for example XCOPY d:\aaa), then that source could be either a file or a directory. Because of this, if the source cannot be found, the root directory tree is replicated on the target. This occurs even if the source not found is a file. For more information about XCOPY, refer to the "Command Reference." 6.4 Associated bitmap-fonts --------------------------- NOTE: This feature is available only for the following languages: o Japanese o Traditional Chinese o Simplified Chinese The Associated Bitmap-fonts feature displays higher quality characters in small point sizes by using bitmap fonts instead of outline fonts. It also improves the rendering performance because the bitmap fonts display more quickly. NOTE: Install all DBCS bitmap fonts for this feature to work effectively. The following limitations and restrictions apply to Associated Bitmap-fonts: o If you want to print output that is identical to your screen layout, disable Associated Bitmap-fonts. To disable this feature: 1. From the System properties notebook (OS/2 System --> System Setup --> System), click the Font page. 2. Click the + symbol to move to the second Font page. 3. Clear the "Activate" check box. 4. Close the properties notebook and restart the system. o Unicode fonts are not supported. o The sample characters in the OS/2 font dialog box cannot switch to a bitmap font. o The IME Conversion String cannot switch to a bitmap font. Japanese users can refer to the "Japanese User's Guide (Nihongo-ban Goshiyou no Tebiki)" for more information. 6.5 Hardware device and device driver considerations ---------------------------------------------------- The following sections contain information about hardware devices and device drivers. 6.5.1 3Com Fast Etherlink XL network adapter boot problem --------------------------------------------------------- If you install the Convenience Package on a PC 365 computer with a 3Com Fast Etherlink XL network adapter, you may experience a system hang during boot. There are two workarounds possible for this problem: o Disable Hardware detection by pressing Alt-F1 then F6 on bootup. This is most appropriate when you are installing from a CD-ROM. o Remark out Serial.snp in the snoop.lst file This is most appropriate when you are installing from a CID server. 6.5.2 Dell OptiPlex GX110 ------------------------- Customers may experience an error when installing the Convenience Package on a Dell OptiPlex GX110 with an integrated ethernet adapter. This system has an integrated 3Com ethernet adapter that appears to the operating system to be a 3Com Fast Etherlink XL/Etherlink XL OS/2 adapter. This causes the incorrect device drivers to be installed(EL90X.OS2 dated 01/24/99 and EL90XIO2.NIF dated 01/09/97) and when the system is restarted the following message is displayed: 3Com Fast Etherlink XL/Etherlink XL OS/2 NDIS driver v4.0z ERROR: Network adapter not found or not responding. Updated device drivers are available from the following 3Com Web site: http://support.3com.com Search for "3C905C" and "3C90XN2.EXE" to locate the panel with the correct download file, then download the EtherCD v5.2 Disk 2 of 2 for the 3C90X Adapter Family, file named 3C90XN2.EXE. This is a self-extracting file. On the diskette created when the file is extracted is a directory named \ndis2\os2. In that directory is the driver for the 3Com Fast Etherlink/ Etherlink Family OS/2 adapter. The files are EL90XIO2.NIF dated 01/09/97 and EL90X.OS2 dated 11/09/99. This driver will work with the integrated adapter in the Dell OptiPlex GX110. 6.5.3 Device driver adapters ---------------------------- o Refer to the Device Driver Pak Online for information regarding device drivers and to download device drivers. Go to the following Web site for more information: http://service.software.ibm.com/os2ddpak/ You can check the LSI Logic Web page for information about LSI Logic (formerly symBIOS) device drivers: http:\\www.lsilogic.com. There you may find READMEs and FAQs. o If you experience difficulty using the 3Com Fast Etherlink XL ethernet adapter, download the latest EL90X.os2 driver from the 3Com Web site: http://www.3com.com. o The SYM8XX driver is included on Installation Diskette 1. If you need this driver, add the following statement to the CONFIG.SYS file on Installation Diskette 1: BASEDEV=SYM8XX.ADD o The SYM_HI driver is included in the scsiadds bundle on the CD in the \os2image\disk_7 directory. If you need this driver, unpack it from the bundle and replace SYM8XX.ADD on Installation Diskette 1 with SYM_HI.ADD. Then add the following statement to the CONFIG.SYS file on Installation Diskette 1: BASEDEV=SYM_HI.ADD o The IBM EtherStreamer MC32 Adapter is not supported. 6.5.4 IBM ISDN Co-Processor adapters ------------------------------------ Intermittent problems can occur on systems with more than two IBM Integrated Services Digital Network (ISDN) co-processor adapters. A message may indicate that an adapter has stopped responding. Attempts to restart the adapter, through Call and Port Management, may result in an error message stating that an internal processing error has occurred in the ISDN Co-Processor Support Program. 6.5.5 PCMCIA flash memory and hard disk support ----------------------------------------------- If you installed PCMCIA support and selected either "PCMCIA Hard Disk" or "PCMCIA Flash," you need to remove REM from the following statements in the CONFIG.SYS file to enable support for these devices: DEVICE=C:\OS2\BOOT\PCMSSDIF.SYS ;Memory Card discriminator DEVICE=C:\OS2\BOOT\PCM2SRAM.SYS ;Linear SRAM driver DEVICE=C:\OS2\BOOT\FLSH2MTD.SYS ;Memory Technology driver DEVICE=C:\OS2\BOOT\PCM2FLSH.SYS ;FLASH memory driver BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP ;ATA PCMCIA driver BASEDEV=OS2PCARD.DMD ;Device Manager for ATA/Memory cards 6.5.6 Universal Serial Bus devices ----------------------------------- For information about Universal Serial Bus (USB) devices, refer to the IBM Technical Databases. 7.0 Additional information included with this product _____________________________________________________ Information for the Convenience Package includes README files on the diskettes and CDs, and several online books. 7.1 README files ---------------- In addition to this README file, other README files are located on the diskettes and CDs that are included with this product. To find these README files, issue the following command from the root directory of the diskette or CD: DIR /S README* An example of this type of README file is README.CID. This file is located on the Convenience Package for OS/2 Warp 4 CD in the OS2UG\DISK_0 directory, and contains instructions for installing this product using the configuration, installation, and distribution (CID) process. 7.2 Books --------- The product library includes several online books. Refer to "Using Online Information" in the Assistance Center on your desktop for summaries of each book. These books are located in the \BOOKS directory on the CD. Several formats are available: HTML, PDF, PostScript, and INF. Additional information related to these products is available on the Web at http:\\www.redbooks.ibm.com. 8.0 NOTICES ___________ Due to the extent of common and connected components between IBM OS/2 Warp 4 and IBM OS/2 Warp Server for e-business, information provided with the Convenience Package for IBM OS/2 Warp 4 may contain references to OS/2 Warp Server for e-business, or to components of OS/2 Warp Server for e-business that are not part of OS/2 Warp 4. These references apply to the combined server plus clients environment. These references do not represent a statement of OS/2 Warp 4 content as delivered or as installed on your machine. For references to information provided only with IBM OS/2 Warp Server for e-business, access the referenced material from the server machine or Convenience Package for IBM OS/2 Warp Server for e-business CD. 9.0 TRADEMARKS ________________ The following terms, are registered trademarks of the IBM Corporation in the United States, or other countries, or both: o IBM o LAN Distance o OS/2 o OS/2 Warp o ThinkPad o WIN-OS/2 o WebSphere The following terms are trademarks of other companies: Approach, Freelance Graphics, Lotus, Lotus Notes, Lotus Organizer, Lotus SmartSuite, and WordPro are trademarks of Lotus Development Corporation in the United States, other countries, or both. Tivoli is a trademark of Tivoli Systems Inc. in the United States, other countries, or both. Intel, Pentium, and SpeedStep are registered trademarks of Intel Corporation in the United States, other countries, or both. Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (c) Copyright IBM Corporation 2000. All rights reserved.