OS/2 DEVICE DRIVER FOR THE S3 Trio32/Trio64/64+/V2 CHIP SETS This package contains the following: o An OS/2* graphics video driver supporting the Trio32(732), Trio64(764), Trio64V+(765) and Trio64V2 DX/GX(775/785) chip sets from S3** Incorporated. o This README file, which is formatted for viewing on your screen. You can: - Use the Table of Contents to help you locate specific topics. - Use the Find option in the Edit menu of the OS/2 System Editor to help you locate specific information. - Print the file. IMPORTANT PLEASE READ THE FOLLOWING TERMS AND CONDITIONS. YOUR USE OF THE OS/2 DEVICE DRIVER FOR THE S3 TRIO32/TRIO64/64+/V2 INDICATES YOUR ACCEPTANCE OF THE FOLLOWING TERMS AND CONDITIONS: o YOU MUST BE, AND YOU AGREE THAT YOU ARE, A PRIOR LICENSEE OF OS/2. o YOU MAY MAKE COPIES OF THE OS/2 DEVICE DRIVER FOR THE S3 TRIO32/TRIO64/64+/V2 EQUAL TO THE NUMBER OF LICENSED COPIES OF OS/2 YOU POSSESS. o ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2 LICENSE AGREEMENT APPLY TO THIS OS/2 DEVICE DRIVER FOR THE S3 TRIO32/TRIO64/64+/V2; HOWEVER, THIS DOES NOT EXTEND ANY WARRANTY OUTLINED IN SUCH AGREEMENT. o READ THIS ENTIRE DOCUMENT BEFORE BEGINNING THE VIDEO DEVICE DRIVER INSTALLATION. o THE INSTALLATION PROCEDURE IN THIS DOCUMENT MUST BE USED TO INSTALL THIS DEVICE DRIVER. DO NOT USE OS/2 SELECTIVE INSTALL TO INSTALL THIS DEVICE DRIVER. o THE DEVICE DRIVER INSTALLATION DISKETTES MUST CONTAIN DISKETTE VOLUME LABELS OF "S3 DRV1" AND "S3 DRV2". INSTALLATION WILL FAIL IF THE INSTALLATION DISKETTES DO NOT HAVE THESE LABELS. THE DISKETTE VOLUME LABEL MAY BE VIEWED BY USING THE DOS OR OS/2; DIR OR LABEL COMMAND. THE VOLUME LABEL MAY BE APPLIED BY USING THE LABEL COMMAND. CONTENTS ________ 1.0 Supported Features 1.1 Supported Resolutions 1.2 Supported Adapters 1.3 Supported Columns and Rows 2.0 Compatibility 3.0 DDC Monitor Support 4.0 Preliminary Steps 5.0 Setting Your Display to VGA Mode 6.0 Installation from Diskette 7.0 Installation in a CID Environment 8.0 Selecting Small or Large Fonts for Windows 9.0 Features and Fixes Included in this Driver 10.0 Limitations 11.0 Trademarks 1.0 SUPPORTED FEATURES _______________________ This graphics-accelerator device driver provides seamless support for accelerated display graphics and advanced color resolutions when used with the minimum required video memory. It conforms to the OS/2 32-bit, flat memory model and is designed to function as a 32-bit Presentation Manager graphics-display device driver under the OS/2 32-bit graphics engine. This device driver supports setting the refresh rate using the System - Settings notebook (page 2 of the Screen tab) in the OS/2 System Setup folder, and monitor detection using Display Data Channel (DDC) protocols. 1.1 Supported Resolutions |===================================================| | Mode | Resolution | Memory | Trio | | | | Required| Family | |------|--------------|---------|-------------------| | | | | 764/765 | 775/785 | | | | | 732 | | |------|--------------|---------|---------|---------| | 101 | 640x480x8 | 1 MB | Y | Y | |------|--------------|---------|---------|---------| | 103 | 800x600x8 | 1 MB | Y | Y | |------|--------------|---------|---------|---------| | 105 | 1024x768x8 | 1 MB | Y | Y | |------|--------------|---------|---------|---------| | 107 | 1280x1024x8 | 2 MB | Y | Y | |------|--------------|---------|---------|---------| | 111 | 640x480x16 | 1 MB | Y | Y | |------|--------------|---------|---------|---------| | 114 | 800x600x16 | 2 MB | Y | Y | |------|--------------|---------|---------|---------| | 116 | 1024x768x16 | 2 MB | Y | Y | |------|--------------|---------|---------|---------| | 212 | 640x480x24 | 1 MB | N/S | N/S | |------|--------------|---------|---------|---------| | 112 | 640x480x32 | 2 MB | Y | Y | |------|--------------|---------|---------|---------| | 115 | 800x600x32 | 4 MB | N/A | Y | |------|--------------|---------|---------|---------| | 118 | 1024x768x32 | 4 MB | N/A | Y | |------|--------------|---------|---------|---------| | 11A | 1280x1024x16 | 4 MB | N/A | Y | |------|--------------|---------|---------|---------| | 120 | 1600X1200x8 | 4 MB | N/A | Y | |===================================================| NOTES: o BPP = Bits Per Pixel (color depth); 8 = 256 colors, 16 = 65,536 colors, 24 = 16,777,216 colors & 32 = 16,777,216 colors. o Y = Supported; N/S = Not Supported. o 1 MB only - 640x480x24 is supported for 1 MB memory configuration only; for 2 MB and above, 32 bits per pixel (BPP) is supported. o S3 BIOS supports 1600x1200x8 with 2 MB; S3 OS/2 device driver needs 4 MB of memory. o S3 BIOS supports 800x600x16 with 1 MB; S3 OS/2 device driver needs 2 MB of memory. o S3 BIOS supports 1280x1024x16 with 3 MB; S3 OS/2 device driver needs 4 MB of memory. o S3 BIOS supports 800x600x32 with 2 MB; S3 OS/2 device driver needs 4 MB of memory The 32 bpp device driver might need a large swap space on the hard disk, for example, 15 MB. 1.2 Supported Adapters For a comprehensive list of products that have been tested by IBM and are OS/2 compatible, refer to the "OS/2 Hardware Compatibility List" book. This book is available electronically in the following locations: http://www.austin.ibm.com/pspinfo/os2hw.html IBM National Support Center BBS (data connection: 919-517-0001) CompuServe (IBM OS/2 Support Forum \Library\IBMFiles\PCMTABLE.ZIP) PRODIGY LAN Server & OS/2 BBS -Sydney Australia IBM Austria BBS - Vienna, Austria IBM BBS - Vancouver, BC, Canada IBM PS BBS - Hong Kong IBM OS/2 BBS & IBM AP OS/2 BBS - Singapore IBM BBS - Belgium IBM BBS - England IBM BBS - Spain OS2BBS - Denmark Hitline BBS- Switzerland DAP & PSP BBS - Italy IBM BBS - Jakarta IBM BBS - Thailand NOTE: The compatibility hardware test information supplied is provided for information purposes. IBM makes no warranty, express or implied, with respect to the operation of OS/2 on the personal computers listed. 1.3 SUPPORTED COLUMNS AND ROWS This S3 Trio32/Trio64/64+/V2 graphics video driver supports the following number of columns and rows in an OS/2 full-screen session: Columns Rows 132 25 132 43 2.0 COMPATIBILITY __________________ This graphics-accelerator device driver is compatible with OS/2 Warp 3.0 and OS/2 Warp 4.0. 3.0 DDC MOMITOR SUPPORT ________________________ VESA Display Data Channel (DDC) 1 and 2B protocols are supported, allowing similarly enabled computers and operating system software to identify the monitor and its capabilities. This device driver automatically detects DDC monitor capabilities and sets the display to the maximum refresh rate supported by the monitor. If, after installing this device driver, you switch from a non-DDC monitor to a DDC monitor or switch to a different DDC monitor, you must run the DDC Display Setup program in the System Setup folder. Use the following procedures when installing a DDC monitor. 1. Reset the display to the lowest refresh rate available. This will prevent the system from setting a refresh rate higher than that supported by the new monitor. 2. Shut down your system and install the new monitor. 3. Restart your system. 4. Select the "DDC Display Setup" icon in the OS/2 System Folder. 5. When you are instructed to do so, shut down your system and restart it. 4.0 PRELIMINARY STEPS ______________________ The following steps must be performed before you install the graphics- accelerator device driver: 1. You must have OS/2 DOS Support installed. 2. If you previously installed SVGA support, you must reset the resolution to VGA mode, using the procedures in "Setting Your Display to VGA mode" (section 5.0 in this README). 3. The device driver diskettes must be labeled "S3 DRV1" and "S3 DRV2." 4. After driver installation, the OS/2 SYSLEVEL command may be used to confirm the new driver version level. It may also be used prior to installation to verify the current driver version, however, some previous device drivers did not provide this information. Following execution of the SYSLEVEL command look for the following information: C:\OS2\INSTALLATION\SYSLEVEL.VID Vision864/964/868/968/Trio32/64/64V+/64V2 Version 2.81 Component ID 562107701 Current CSD level: S330302 Prior CSD level: S328414 In this case the current version level is S3 3.03.02. 5. In some situations, installing this driver over 2.80.xx and 2.81.xx versions of the driver can result in duplicated icons. To prevent this problem, you should delete the "S3 Windows Font Size" and "DDC Display Setup" icons from the System Setup Folder prior to installing this driver. 5.0 SETTING YOUR DISPLAY TO VGA MODE _____________________________________ Use the following procedures to reset to VGA mode. NOTE: If your display is out of sync, start OS/2 using the OS/2 Installation Diskette. Insert Diskette 1 when prompted, press F3 to display a command prompt, and then use the following instructions to reset your display mode. o If you are installing this driver on OS/2 Warp, do the following: 1. Turn on your computer. If your computer is already on, press Ctrl+Alt+Del to restart it. 2. When a small white box appears in the upper left-hand corner of your screen, press Alt+F1. 3. When the Recovery Choices screen appears, press V. Your display adapter is restored and can work in VGA mode. If you want to install a new display adapter or video device driver, refer to Chapter 16, "Video Procedures," in the User's Guide to OS/2 Warp. o If you are installing this driver on OS/2 2.1, 2.11 or OS/2 for Windows, and you installed from diskettes, do the following: 1. Under OS/2 2.1, before running RSPDSPI, delete the following file: [OS2 DRIVE]:\OS2\INSTALL\00S3.DSC 2. Under OS/2 2.11, bfore running RSPDSPI, delete the following file: [OS2 DRIVE]:\OS2\INSTALL\00S3.DSC 3. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If it is, go to step 6. If it is not, insert Diskette 8 into drive A and unpack RSPDSPI.EXE with the following command: C:\OS2\UNPACK A:\INSTAID C: /N:RSPDSPI.EXE where A: is the drive containing Diskette 8, and C: is the drive where OS/2 is installed. 4. Type C: and then press Enter. 5. Type CD C:\OS2\INSTALL and then press Enter. 6. Type the following: RSPDSPI /PK:VGA /SK:NONE /S:A:\ /T:C: In /T:C:, C: is the target drive where OS/2 is installed. In /S:A:, A: is the source diskette drive for installing the device driver. Then press Enter. 7. In some cases you will get screen instructions telling you to "Insert the diskette with the following label into drive A: Display Driver Diskette 1. Then press Enter". Please follow these instructions. 8. Perform a shutdown and restart your computer. o If you are installing this driver on OS/2 2.1, 2.11 or OS/2 for Windows, and you installed from CD-ROM or a LAN, do the following: 1. Under OS/2 2.1, before running RSPDSPI, delete the following file: [OS2 DRIVE]:\OS2\INSTALL\00S3.DSC 2. Under OS/2 2.11, before running RSPDSPI, delete the following file: [OS2 DRIVE]:\OS2\INSTALL\00S3.DSC 3. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If it is, go to step 6. If it is not, unpack RSPDSPI.EXE with the following command: C:\OS2\UNPACK E:\DISK_8\INSTAID C: /N:RSPDSPI.EXE where C: is the drive where OS/2 is installed, and E: is the CD-ROM or LAN drive. 4. Type C: and then press Enter. 5. Type CD C:\OS2\INSTALL and then press Enter. 6. Type the following: RSPDSPI /PK:VGA /SK:NONE /S:E:\OS2SE21\ /T:C: In /T:C:, C: is the target drive where OS/2 is installed. In /S:E:, E: is the source CD-ROM or LAN drive. Then press Enter. 7. Perform a shutdown and restart your computer. 6.0 INSTALLING FROM DISKETTE _____________________________ To install the graphics-accelerated device driver from diskette, do the following: 1. If system is not in VGA mode, select VGA mode. 2. Insert the Vision864/964/868/968/Trio32/64/64V+/64V2 diskette into drive A (or any other diskette drive). Note: "S3 DRV1" must be the volume label of this diskette. To verify the label, use "Label A:". 3. Open an OS/2 full-screen or OS/2 window session. 4. At the OS/2 command prompt, type the following command to copy all necessary files to the OS/2 drive: A:SETUP where A: is the diskette drive. Then press Enter. Setup will then identify your chipset. When prompted to do so, press Enter to continue. Due to the limitations with a single pass installation. A dialog box may come up during installation with the message, "The installed adapter does not support the selected display driver. Do you wish to continue?". Please continue the installation by selecting the Yes button. 5. When the Monitor Configuration/Selection Utility window appears, the "Install Using Defaults for Monitor Type" choice is preselected. Select OK. Do not select "Install Using Display Adapter Utility Program" since this method of setting refresh rates is not supported anymore. NOTE: DSPINSTL determines the hardware configuration by creating the \OS2\SVGADATA.PMI file. If the \OS2\SVGADATA.PMI file has not been created, the adapter will not be supported. This process can take several seconds and will black-out the screen. 6. When the Source Directory pop-up window requests the Vision868/968/Trio32/64/64V+/64V2 diskette insert the diskette labelled "S3 DRV1". If the Source Directory pop-up window requests the -CHIPDESC2- diskette insert the diskette labelled "S3 DRV2". Then select Install. 7. When prompted to do so, select OK to perform a shutdown, and then restart your computer. Make sure the diskette has been removed from the install drive. 8. When the system has restarted: a. Open the OS/2 System folder. b. Open the System Setup folder. c. Open the System object. d. When the Settings notebook appears, select the Screen tab. If your monitor has been detected as Plug and-Play (DDC) compatible, go to step 10. 9. On Screen page 2, select your display from the display list. If your display does not appear in the list, select Default. It might be necessary to restart your computer to have all refresh rate options available. 10. When the system has restarted: a. Open the System object and select Screen page 1, as in step 8. b. Select a screen resolution and a screen refresh rate. c. Close the Settings notebook. d. Perform a shutdown and restart your computer. NOTES: o If the selected vertical refresh rate is not supported by your monitor, delete \OS2\VIDEO.CFG file and reboot. This will set the refresh rate to the default value. A new refresh rate can now be selected using the procedure described above. o During the installation of this driver, DISPLAY.LOG and DSPINSTL.LOG files are created in the OS/2\INSTALL directory. These files identify the OS/2 system files that were updated and indicate whether the installation was successful. The contents of these files might be useful if you need to report an installation problem to IBM. o If the video memory size is changed after the device driver is installed, the device driver must be reinstalled in order for the system to recognize the change. Not reinstalling the driver might result in serious system problems. o When starting a WIN-OS/2 session it is recommended that the user launch the session via one of the WIN-OS/2 icons located in the "Command Prompts" folder within the "OS/2 System" icon. For additional information see section 10.0 Limitations. 7.0 INSTALLING IN A CID ENVIRONMENT ____________________________________ NOTES: o The server must contain a directory named S3_DRVS on the same drive where the OS/2 diskettes reside. The S3_DRVS directory must contain all of the files from the graphics-accelerator device driver installation diskette. o OS/2 must have been successfully installed on the client using the CID (Configuration Installation Distribution) method. o To configure resolution, monitor selection and refresh rate, refer to the file "README.CFG" in this package. To install the graphics-accelerator device driver using CID, use the following information to modify your LCU command file. NOTE: The following information is meant as a guide. Your LCU command file might be different. /*****************************************************/ /* LCU PRODUCT DATA SECTION */ /*****************************************************/ . . . x.s3video = 15 x.15.name='S3 Video' x.15.statevar = 'CAS_' || x.15.name x.15.instprog = 'x:\img\s3_drvs\SETUP.CMD', ' x:\img\s3_drvs ' || bootdrive || ' CID' x.15.rspdir = '' x.15.default = '' x.s3dspinstl = 16 x.16.name='S3 CID Dspinstl' x.16.statevar = 'CAS_' || x.16.name x.16.instprog = bootdrive || '\os2\install\DSPINSTL.EXE', ' /pd:' || bootdrive || '\os2\install\00S3.DSC', ' /s:x:\img\s3_drvs', ' /t:' || bootdrive, ' /res:640x480x256', ' /u' x.16.rspdir = '' x.16.default = '' /*---------------------------------------------------*/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*---------------------------------------------------*/ NUM_INSTALL_PROGS = 16 /*****************************************************/ /* INSTALLATION SECTION */ /*****************************************************/ . . . when OVERALL_STATE = 2 then do if RunInstall(x.s3video) == BAD_RC then exit Call RebootAndGotoState(3) end when OVERALL_STATE = 3 then do if RunInstall(x.s3dspinstl) == BAD_RC then exit Call CheckBoot end . . . /******************************************************/ /* ROUTINE SECTION */ /* The following information should already exist in */ /* the LCU command file. */ /******************************************************/ . . . RebootAndGotoState: parse arg new_state, other rc2 = SetState(new_state, 'RebootAndGotoState', 1) /* Set the state */ /* to go to in */ /* OVERALL_STATE */ Call SaveStates /* Save the environment vars */ Call Reboot /* Reboot the machine */ return . . . /*****************************************************/ END OF LCU INFORMATION TO BE ADDED /*****************************************************/ Following is an explanation of the line that is executed in the LCU command file: C:\OS2\INSTALL\DSPINSTL /pd:c:\os2\install\00S3.DSC /S:X:\img\s3_drvs /T:C: /res:640x480x256 /u /pd:c:\os2\install\00S3.DSC is the dsc laid down during setup phase. /S:X:\img\s3_drvs where X:\img\s3_drvs is the redirected source path. /T:C: where C: is the drive where OS/2 is installed. /res:640x480x256 is a resolution/color depth from the list of "Supported Resolutions" that appears earlier in this README. In this example 256 colors is specified. Enter "64K" to specify 65,536 colors or "16M" to specify 16,777,216 colors. /u means Unattended installation. NOTES: o Be sure you have the stated video memory required, as listed in "Supported Resolutions" earlier in this README. A safe choice is 640x480x256. Any of the listed resolutions can be selected, but your display might be damaged if you select a resolution that your display does not support. o After the graphics-accelerator device driver has been successfully installed the client machine using the CID method and the client machine is restarted, the resolution will be as specified by command line argument. o After the CID installation, refer the end user to section 6.0 "Installation from Diskette," step 12. 8.0 SELECTING SMALL OR LARGE FONTS FOR WINDOWS _______________________________________________ The default font sizes for Windows sessions are listed below. Resolution Default Font Size ---------- ----------------- 640x480 Small 800x600 Small 1024x768 Large 1280x1024 Large 1600x1200 Large NOTE: Large fonts are not available for the 640x480 resolution. Use the following procedures to select small or large fonts for Windows sessions. 1. Select the "S3 Windows Font Size" object in the OS/2 System Setup Folder. 2. Click on the radio button next to the font size you wish to select. 3. Click on the OK button. 4. A message will display saying that the new settings will take effect the next time you restart your Windows session. Currently open sessions will not be affected by the new settings. 5. Click on the OK button. 6. Start any WIN-OS/2 window or full-screen session. The setting you select will remain in effect until you explicitly change it, you change your display resolution, or you install a new display driver. 9.0 FEATURES AND FIXES INCLUDED IN THIS DRIVER _______________________________________________ - "System - Settings" notebook support for setting refresh rate - Capabilities button of page 1 of the "System - Settings" notebook for large/small/automatic resource size selection (changes WIN-OS/2) font sizes as well - DDC monitor detection support - Windows "Large font" and "Small font" support in high resolutions - WIN-OS/2 based on latest S3 Windows 3.1 drivers - Two-diskette package - One boot install - EnDIVE support for Trio64V+ and Trio64V2 on certain video modes - CID install allow preselected refresh rate 10.0 LIMITATIONS ________________ 1. CID install pauses due to SVGA.EXE loading in the background. Workaround: In the CID install script, do not initiate any other processes until DISPINSTL completes execution. Ensure that no other processes are running during CID install. This can be accomplished by adding the following line to the CONFIGSYSLINE keyword of the CID response file: SET RESTARTOBJECTS=STARTUPFOLDERSONLY 2. During CID install of IBM AntiVirus when using NetView DM/2, the OS/2 full screen is displayed as a black screen. Workaround: Perform CID install under VGA. 3. DISPINSTL does not allow CID selection of monitor and refresh rate. The workaround is as follows: Requirements: * A system with the same graphics card and monitor configured with the S3 driver version 2.81.05, the correct display type, the desired resolution, and the desired refresh rate. Step 1: Copy Configured Video/Display Data Files * copy the video and display data files containing information about the display type, resolution and refresh rate to the CID server (\img\svgadata). > copy \os2\svgadata.pmi x:\img\svgadata > copy \os2\video.cfg x:\img\svgadata Step 2: Create CID Command File * create a command file to copy svgadata.pmi and video.cfg to the client system's \os2 directory via CID. * reboot the client system. * the client system will be configured with the correct driver, display type, resolution and refresh rate. Another work around is to delete \OS2\VIDEO.CFG and to execute SVGA.EXE again after DSPINSTL completes. Example: SVGA ON INIT 1024 75 to set 75Hz as the default refresh rate at 1024x768. 4. In all modes, video corruption or out-of-sync screen is displayed when using Alt+Esc to switch between WIN-OS/2, OS/2, and DOS window and full-screen sessions started from the Startup folder. To avoid this situation, do not start sessions from the Startup folder or press Alt+Esc several times to restore. 5. Some programs, such as WINBENCH95, WINBENCH96, and After Dark 3.0, were written specifically for the Windows environment. In the Windows environment, these programs prevent any keystrokes from interfering with their proper execution. However, in the OS/2 environment, it is possible to switch context away from the Windows session without notifying these programs. General Protection Faults (GPFs) may result. Therefore, context switching during the execution of WINBENCH95 and WINBENCH96 tests is not recommended. Also, context switching during the execution of the After Dark 3.0 demo is not recommended. 6. When attempting to start a WIN-OS/2 session from an OS/2 Full Screen session by typing "WIN" or "WINOS2" at the command prompt, it will not execute with the settings needed to support WIN-OS/2, and will result in video corruption and/or a system lockup. It is recommended that the user launch all Windows sessions via one of the WIN-OS/2 icons located in the "Command Prompts" folder within the "OS/2 System" icon. 7. When attempting to start a WIN-OS/2 session from a DOS Full screen or DOS Window by typing the "WIN" or WINOS2" command, the user must first be sure that the video settings of the session are changed to enable this feature. These settings can be changed using the following procedure: a) Place mouse pointer over the DOS Full Screen icon (or any DOS session icon you want to alter). Press mouse button 2 (MB2), the right button, to bring up a context sensitive menu. b) Place mouse pointer over "Setting" and press MB1. Next, place mouse pointer over the tab labeled "Session" and press MB1 again. c) Use MB1 to chose the "DOS Setting" button. d) Use MB1 to chose the "DOS video settings" option, and then click OK. e) From the list of settings which appear ensure that "VIDEO_8514A_XGA_IOTRAP" is switched OFF, AND "VIDEO_SWITCH_NOTIFICATION" is switched to ON, then "save" these settings using MB1. 11.0 TRADEMARKS ________________ The following terms, denoted by an asterisk (*) in this file, are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries: IBM MMPM/2 OS/2 Presentation Manager PS/ValuePoint WIN-OS/2 The following terms, denoted by a double asterisk (**) in this file, are trademarks or registered trademarks of other companies as follows: TRADEMARK OWNER After Dark Berkely Systems, Inc. CorelDRAW Corel Corporation Lotus Lotus Development Corporation Micrografx Micrografx Incorporated S3 S3 Incorporated Ventura Publisher Ventura Software, Inc. Windows Microsoft Corporation WordPerfect WordPerfect Corporation 1-2-3 Lotus Development Corporation IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS 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 RELATED PATENTS OR COPYRIGHTS. THIS DRIVER IS COPYRIGHTED BY INTERNATIONAL BUSINESS MACHINES CORPORATION. ALL APPROPRIATE RESTRICTIONS APPLY. (End of Document)