OS/2 Device Driver Pak Online - README Welcome to the OS/2 Device Driver Pak Online Readme Page. This README contains information relating to the OS/2 Device Driver Pak Online, its usage, and any last minute changes. Contents 1. Introduction 2. Installing a device driver 3. Installing OS/2 with drivers not included in your diskettes 4. Installing Display Device Drivers not shipped on the OS/2 Warp Version 4 CD-ROM 5. Installing Display Device Drivers not shipped on the OS/2 Warp Version 4 CD-ROM in a network installation environment 6. Problem reporting 7. License 8. Trademarks Introduction As a convenience to our customers who are installing OS/2 Warp, IBM has created an easy to use distribution method for the wide range of devices supported by OS/2, called the OS/2 Device Driver Pak Online. IBM has not tested these device drivers and does not provide support for these device drivers unless explicitly stated otherwise in the device driver packages. As indicated in the packages, many of the device drivers are supported by the manufacturer of the device. The DD Pak Online is designed for viewing using a web browser. You may use either the web browser which comes with OS/2 Warp, or your favorite web browser to view the wide range of devices supported by OS/2. The content of the HTML pages is arranged to provide ease of use in navigating through the many hardware devices, the manufacturers and their products. It is possible to quickly pinpoint information about a specific device by just knowing the device type (such as CDROM, Display, PCMCIA, etc), the manufacturer of that device, and the actual product name. In addition, detailed product information is available for each device. As an additional aid in helping you to know who to contact and how, hot links are provided to the WWW and FTP sites of the manufacturer and the e-mail address of their support organization. You will also find the telephone number(s) of their BBS, sales offices, and general inquiries, if available. As you view the HTML pages, you will see product names. If a device driver is available for a particular product, the product name will be listed. If your product is not listed, you should use the "Manufacturer Information" to obtain information regarding product availability and support from that manufacturer. The product information page provides detail on the product, such as the chipset in the case of a display adapter. If the device is supported by the base operating system, then instructions on how to install it, and how to contact the manufacturer are provided. Installing a device driver If after browsing through the DD Pak Online, you find a device driver that you would like to install, use your web browser to download the file to a local hard disk on your machine. All device driver files on the DD Pak Online are in a format known as ZIP format. All individual files which form a complete device driver are packed together into a single ZIP'ed file. Once the download is complete, you may unpack the file. To unzip any of the device drivers with a ".ZIP" extension, you will need to use the PKUNZIP2.EXE program. If you are using Warp 4 and Warp 3 Connect, PKUNZIP2.EXE is located in the d:\IBMCOM subdirectory, where "d:" is the drive letter where you installed OS/2 Warp. If you are using Warp 3, PKUNZIP2.EXE is located in the d:\OS2\INSTALL subdirectory where "d:" is the drive letter where you installed OS/2 Warp. You may use this program directly by typing PKUNZIP2 at any OS/2 command prompt, since this program is listed in the path of CONFIG.SYS. Note: Some of the device drivers will have a ".EXE" extension. These drivers may be unzipped by typing the name of the driver file at the command prompt. Here are a few helpful hints on unpacking: * If the device driver file has an extension of .ZIP, unpack the file using the PKUNZIP2.EXE unpacking program. * If the device driver file has an extension of .EXE, you may unpack the driver by entering the driver name at the command prompt. * If the device driver file has an extension of .DSK, use the LOADDSKF.EXE program to create a diskette of the device driver. Installing OS/2 with drivers not included on your diskettes The DDPAK contains some device drivers that are not on the OS/2 Install disks. These are generally BASEDEV's. Note: In Warp 4, BASEDEV=XXX and DEVICE=XXX drivers are included on diskettes 1 and 2 respectively. In prior versions of Warp, these drivers are both on the Install Diskette 1 (D1). For BASEDEV= device drivers , add your device driver to the D1 diskette: 1. Make a backup copy of your D1 diskette. 2. If there is enough room on D1, copy the device driver file onto your D1 diskette. 3. If there is not enough room on D1, the following files may be deleted: README.INS, CDINST.EXE This should free about 43K. If more space is required, delete one or two XXXXXXXX.ADD's from D1 that are not required for installation. You must also delete the corresponding CONFIG.SYS statement or OS/2 Install will not complete. Note: The following files must NOT be deleted from D1: * CLOCK01.SYS * CLOCK02.SYS * IBM1S506.ADD * IBM1FLPY.ADD * IBM2FLPY.ADD * IBM2ADSK.ADD * IBM2SCSI.ADD * IBMINT13.I13 * IBMKBD.SYS * KBDBASE.SYS * OS2LOGO * OS2DASD.DMD * PNP.SYS * RESERVE.SYS * RESOURECE.SYS * SCREEN01.SYS * SCREEN02.SYS * SNOOP.LST * XDFLOPPY.FLT * *.SNP (Files with extension of SNP) 4. Edit the CONFIG.SYS file on the D1 diskette to add the device driver statement to the CONFIG.SYS as the FIRST LINE in the CONFIG.SYS. This may be one of the following formats according to the device driver directions: 5. BASEDEV=XXXXXXXX.YYY (where YYY is SYS, ADD, FLT, or DMD) Add the following statement to CONFIG.SYS to ensure the driver is copied throughout installation: 6. SET COPYFROMFLOPPY=1 Use this modified D1 when prompted by Installation. 7. At the end of Installation your driver statement should be in the CONFIG.SYS with the appropriate path as necessary (BASEDEV statements do not have paths) and your device driver should be copied to the \OS2\BOOT directory. 8. If at anytime during the installation phases and reboots, you seem to have lost connection to your hard disk or CDROM make sure that the CONFIG.SYS line and the device driver are on your hard disk or the drive letters have not been reversed. If the hard disk drive letters are reversed make sure the BASEDEV statement remains as the first line of the CONFIG.SYS. For DEVICE= device drivers , add your device driver to the Install Diskette 2 (D2): 1. Make a backup copy of your D2 diskette. 2. Copy your device driver to the D2 diskette. 3. Edit the CONFIG.SYS file on the D1 diskette to add the device driver statement to the CONFIG.SYS as the FIRST LINE in the CONFIG.SYS. This may be one of the following format according to the device driver directions: 4. DEVICE=XXXXXXXX.SYS Use these modified D1 and D2 diskettes when prompted by Installation. 5. At the end of Installation your driver statement should be in the CONFIG.SYS with the appropriate path as necessary and your device driver should be copied to the \OS2\BOOT directory. DEVICE= statements need drive and path statements. See the following example for the COM.SYS statement in the final CONFIG.SYS: 6. DEVICE=C:\OS2\BOOT\COM.SYS If at anytime during the installation phases and reboots, you seem to have lost connection to your hard disk or CDROM make sure that the CONFIG.SYS line and the device driver are on your hard disk. Installing Display Device Drivers not shipped on the OS/2 Warp Version 4 CD-ROM OS/2 Warp Version 4 ships with a new version of DSPRES.DLL. Display device drivers installed with a version of DSPRES.DLL other than the one shipped on the OS/2 Warp Version 4 CD-ROM may see problems with the system fonts. This includes display drivers provided in the OS/2 Warp Device Driver PAK CD-ROM. If the display driver package does not contain a copy of DSPRES.DLL, there is no need for these special installation instructions to restore DSPRES.DLL. This file is sometimes named DSPRES.DLZ in some display driver packages. The following installation instructions are provided for display device drivers which may overlay the version of DSPRES.DLL shipped on the OS/2 Warp Version 4 CD-ROM. 1. Press Ctrl+Alt+Del to restart the system. 2. When a small white box appears in the upper left-hand corner of your screen, press Alt+F1. 3. At the menu selection press F2. 4. At the command prompt type: 5. UNPACK \OS2\INSTALL\VGA\VGA /N:DSPRES.DLL Press exit and the system will reboot. Installing Display Device Drivers not shipped on the OS/2 Warp Version 4 CD-ROM in a network installation environment If the display driver installation replaces the Warp Version 4 file DSPRES.DLL, replace this DSPRES.DLL file in the "from" installation location of the display drivers with the Warp Version 4 file DSPRES.DLL before installation to assure correct system fonts. Note: The Warp Version 4 version of DSPRES.DLL is compatible with Warp Version 3. One display driver and install process will work for both Warp Version 4 and Warp Version 3 as long as the display driver contains the DSPRES.DLL from Warp Version 4. Problem Reporting Please check the device packages for information concerning product support for device drivers contained on this site. We have included hot links to the WWW and FTP sites of the manufacturer and the e-mail address of their support organization. You will also find the telephone number(s) of their BBS, sales offices, and general inquiries, if available. License Please read the License Agreement. Your use of the DD PAK Online, as well as its contents, is conditional upon your acceptance of the terms. Trademarks The following terms are trademarks of the IBM Corporation in the United States or other countries: * IBM * OS/2 Trademarks of other companies are acknowledged.