     OS/2 DEVICE DRIVER FOR ATI TECHNOLOGIES MACH64


  This package contains the following:

  o   An OS/2* device driver supporting the Mach64 chip
      set from ATI** Technologies, Inc.
  o   This README file,
      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 ATI TECHNOLOGIES
  MACH64 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
      ATI TECHNOLOGIES MACH64 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 ATI TECHNOLOGIES MACH64; HOWEVER, THIS
      DOES NOT EXTEND ANY WARRANTY OUTLINED IN SUCH
      AGREEMENT.


  CONTENTS
  ________


           1.0  Supported Features
           1.1 Supported Resolutions
           1.2 Supported Adapters

           2.0  Compatibility

           3.0  Preliminary Steps

           4.0  Installation from Diskette

           5.0  Installation in a CID Environment

           6.0  Functional Restrictions

           7.0  Functional Restrictions

           8.0  APARs Included in This Driver

           9.0  Trademarks


 1.0  SUPPORTED FEATURES
  __________________

  The ATI Mach64 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 driver under
  the OS/2 32-bit graphics engine.  This driver has
  been enabled for use with the IBM* Distributed Console
  Access Facility (DCAF) product.


 1.1  SUPPORTED RESOLUTIONS

  This video accelerator driver supports these
  resolutions and color depths:

                            Number of    Video Memory
          Resolutions        Colors        Required

           640x480            256           1MB
           800x600            256           1MB
          1024x768            256           1MB
          1280x1024           256           2MB

           640x480           65,536         1MB
           800x600           65,536         1MB
          1024x768           65,536         2MB
          1280x1024          65,536         4MB

           640x480        16,777,216        2MB
           800x600        16,777,216        2MB
          1024x768        16,777,216        4MB
          1280x1024       16,777,216        4MB


  The ATI Technologies BIOS must be configured to
  recognize all of the resolutions supported by your
  display.  If this is not done, the driver might not
  provide all of the resolutions actually supported by
  your display.  For information on how to configure
  the BIOS of your ATI adapter or system, refer to the
  documentation that came with your adapter or system.

 1.2  SUPPORTED ADAPTERS

  IBM has tested display adapters and
  systems containing the Mach64 chip set with the
  specified amount of memory.  IBM is continuing to
  test; therefore, support for additional cards might
  be added over time.

  For a comprehensive listing of all major manufacturing products
  that are OS/2 compatible, refer to the "OS/2 Hardware Compatibility
  List" book.  This book is available electronically on the following
  Bulletin Board Systems:

     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.


 2.0 COMPATIBILITY
  _____________

  This graphics accelerator driver is compatible with
  OS/2 2.1, 2.11, and OS/2 Warp 3.


 3.0 PRELIMINARY STEPS
  _________________

  The following steps prepare your computer for the
  Mach64 device driver:

  1.  You must have OS/2 DOS Support installed in order
      to install this driver.
  2.  If you previously installed SVGA support, return
      to VGA resolution using the procedures in
      "Setting Your Display to VGA Mode" later in this
      README before you install this driver.
  3.  Before you run the BBS install, you must first
      run the Mach64 vendor install utilities.

 4.0  INSTALLATION FROM DISKETTE
  __________________________

  To install the Mach64 device driver from diskette, do
  the following:

  1.  Insert the Mach64 diskette into drive A (or any
      other diskette drive).
  2.  Open an OS/2 full-screen or OS/2 window session.
  3.  At the OS/2 command prompt, type the following
      command to copy all necessary files to the OS/2
      drive:

             A:SETUP A: C:

      (where A: is the diskette drive, and C: is the
      drive where OS/2 is installed.)

      Then press Enter.
  4.  When prompted to do so, remove the diskette from
      drive A, perform a shutdown, and then restart
      your computer.
  5.  Open the OS/2 System folder.
  6.  Open the System Setup folder.
  7.  Open the Display Driver Install object.
      When the Display Driver Install window appears,
      select Primary Display Driver and then select OK.
  8.  When the Display Driver Select window appears,
      select "ATI Mach64 (IBM BBS)"
      to install the BBS video driver.
  9.  When the Monitor Configuration/Selection Utility
      window appears, the "Install Using Defaults for
      Monitor Type" choice is preselected.  You can
      accept this choice or select "Install Using
      Display Adapter Utility Program" to choose a
      different refresh rate.  Then select OK.

      If you select the "Install Using Display Adapter
      Utility Program" choice, you must have a DOS
      monitor utility that came with your display
      adapter.  Contact the display adapter
      manufacturer's technical support for information
      on how to use the monitor utility under OS/2.

      NOTE:  At this point, 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.

  10. When the Source Directory pop-up window appears,
      insert the Mach64 diskette into drive A.  Then
      select Install.

  11. When the installation is complete, do the
      following:
      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.
      e.  Select a resolution.  Then close the
          notebook.
      f.  Perform a shutdown and restart your computer.

  Note that during the installation of this driver,
  DISPLAY.LOG and DSPINSTL.LOG files are created in the
  OS2\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.

 5.0  INSTALLATION IN A CID ENVIRONMENT
  _________________________________

  NOTES:

  1.  The server must contain a directory named
      ATI_DRVS on the same drive where the OS/2
      diskettes reside.  The ATI_DRVS directory must
      contain all of the files from the Mach64 device
      driver diskettes.
  2.  OS/2 must have been successfully installed on the
      client using the CID (Configuration Installation
      Distribution) method.

  To install the Mach64 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.ativideo = 15
    x.15.name='ATI Video'
    x.15.statevar = 'CAS_' || x.15.name
    x.15.instprog = 'x:\img\ati_drvs\SETUP.CMD',
                    ' x:\img\ati_drvs ' || bootdrive || ' CID'
    x.15.rspdir   = ''
    x.15.default  = ''

    x.atidspinstl = 16
    x.16.name='ATI CID Dspinstl'
    x.16.statevar = 'CAS_' || x.16.name
    x.16.instprog = bootdrive || '\os2\install\DSPINSTL.EXE',
                    ' /pd:' || bootdrive || '\os2\install\atim64bb.dsc',
                    ' /s:x:\img\ati_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.ativideo) == BAD_RC then exit
          Call RebootAndGotoState(3)
        end
        when OVERALL_STATE = 3 then do
          if RunInstall(x.atidspinstl) == 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\atim64bb.dsc
    /S:X:\img\ati_drvs /T:C: /res:640x480x256 /u

       /pd:c:\os2\install\atim64bb.dsc
        This is the dsc laid down during setup phase

       /S:X:\img\ati_drvs
        Where X:\img\ati_drvs is the redirected source path.

       /T:C:
        Where C: is the drive where OS/2 is installed.

       /res:640x480x256
        This is a resolution/color depth from
        the list of "Supported Resolutions" that appears earlier
        in this README.

       /u  means Unattended installation.

  NOTES:

  1.  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.
  2.  After the Mach64 device driver has been
      successfully installed on the client machine
      using the CID method and the client machine is
      restarted, the resolution will be as specified by
      command line argument.
  3.  After the CID install, refer the end user to
      4.0 INSTALLATION FROM DISKETTE step 11.


 6.0  FUNCTIONAL RESTRICTIONS
  _______________________

  o   To get full-screen drivers to work on a computer
      that does not have the aperture enabled, do the
      following:
      1.  Edit the WIN.INI file and make the following
          change to the MACH section of the file:

                 VAD=on

      2.  Run the ATI Technologies DOS installation
          program and enable the MACH64 aperture.

      3.  Edit the WIN.INI file and make the following
          change to the MACH section of the file:

                 VAD=off

  o   After Dark** for Windows** images that move from
      left to right do not perform properly at
      640x480x16M resolution.
  o   To avoid a General Protection fault while loading
      Ventura Publisher** for Windows, be sure it is in
      one of the 256 color resolutions.
  o   To avoid a trap in Lotus** 1-2-3** for OS/2, do
      not attempt to run the program at 16.7 million
      colors.
  o   WordPerfect** Versions 5.1 and 5.2 for Windows
      produce a general protection fault when the
      "Print Preview" option is selected while using
      800x600x64K or 600x480x16 million color mode.
  o   Users of the software motion video feature of
      MMPM/2* should expect satisfactory results in
      256-color modes.  However, in 64K-color modes,
      users of the feature will experience unusual
      results.  An OS/2 pervasive fix package will be
      available electronically.  The software motion
      video feature is not supported in 16-million
      color modes.
  o   Icon colors might be incorrect for all
      resolutions in 64K-color modes due to a problem
      in the OS/2 2.1 graphics engine (PMGRE.DLL).
  o   CorelDRAW** 2.0 will not run in a WIN-OS/2*
      window session.  It must be run in a WIN-OS/2
      full-screen session.
  o   Micrografx** Charisma 2.1 will not run in a
      WIN-OS/2 window session.  It must be run in a
      WIN-OS/2 full-screen session.
  o   Distributed Console Access Facility (DCAF) is
      supported in 256-color modes only.
  o   You might experience screen problems when
      installing Ami Pro** in 1024x768 and 1280x1024
      resolutions.  Install Ami Pro in a lower
      resolution; you can then run the application at a
      higher resolution.
  o   OS\2 2.1 users need to upgrade to the OS/2 2.11
      PMGRE.DLL graphics engine to eliminate the problem of
      the page buttons for system icons and others that
      are blacked out in 64K color depths.


 7.0  SETTING YOUR DISPLAY TO VGA MODE
  ________________________________

  Use the following procedures to return to VGA mode.

  o   If you are installing this driver on OS/2 Warp,
      and you do not have a usable OS/2 Desktop, use
      the following procedures to return to VGA mode.
      However, if you have a usable Desktop, it is
      recommended that you use Selective Install to set
      your display to VGA mode.

      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 do not have a
      usable OS/2 Desktop, use the following procedures
      to return to VGA mode.  However, if you have a
      usable Desktop, it is recommended that you use
      the Display Driver Install object to set your
      display to VGA mode.

      -   If you installed OS/2 from diskettes, do the
          following:

          1.  Start OS/2 using the OS/2 Installation
              Diskette.  When prompted, insert Diskette
              1, and then press F3 to display a command
              prompt.
          2.  Be sure RSPDSPI.EXE is in the
              \OS2\INSTALL directory.  If it is, go to
              step 2.  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.)
          3.  Type C: and then press Enter.
          4.  Type CD C:\OS2\INSTALL and then press
              Enter.
          5.  Type the following:

                RSPDSPI /PK:VGA /SK:NONE /S:A:\ /T:C:

              (In /T:C:, C: is the drive where OS/2 is
              installed.  In /S:A:, A: is the diskette
              drive you use to install OS/2.)

              Then press Enter.

          6. After running RSPDSPI and before rebooting the system, remove the
             following lines from CONFIG.SYS.

              DEVICE=[OS/2DRIVE]:\OS2\ATI0.SYS
              DEVICE=[OS/2DRIVE]:\OS2\ATIM64.SYS
              DEVICE=[OS/2DRIVE]:\OS2\VAD64.SYS

  o  For CID users; before running RSPDSPI and restarting the system:

         1. Edit PSVGA32.DSP.  This file is located on DISPLAY DISK 1.

         2. Find the following line:

            :DEL_CONFIG_LINE :MODE=PRIMARY

         3. Add the following lines below the line mentioned in STEP 2:

            DEVICE=%BOOTDRIVE%:\OS2\ATI0.SYS
            DEVICE=%BOOTDRIVE%:\OS2\VAD64.SYS
            DEVICE=%BOOTDRIVE%:\OS2\AITM64.SYS


      -   If you installed OS/2 from CD-ROM or a LAN,
          do the following:

          1.  Start OS/2 using the OS/2 Installation
              Diskette.  When prompted, insert Diskette
              1, and then press F3 to display a command
              prompt.
          2.  Be sure RSPDSPI.EXE is in the
              \OS2\INSTALL directory.  If it is, go to
              step 2.  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.)
          3.  Type C: and then press Enter.
          4.  Type CD C:\OS2\INSTALL and then press
              Enter.
          5.  Type the following:

                RSPDSPI /PK:VGA /SK:NONE /S:E:\OS2SE21\ /T:C:

              (In /T:C:, C: is the drive where OS/2 is
              installed.  In /S:E:, E: is the CD-ROM or
              LAN drive.)

              Then press Enter.

          6. After running RSPDSPI and before rebooting the system, remove the
             following lines from CONFIG.SYS.

              DEVICE=[OS/2DRIVE]:\OS2\ATI0.SYS
              DEVICE=[OS/2DRIVE]:\OS2\ATIM64.SYS
              DEVICE=[OS/2DRIVE]:\OS2\VAD64.SYS

  o  For CID users; before running RSPDSPI and restarting the system:

         1. Edit PSVGA32.DSP.  This file is located on DISPLAY DISK 1.

         2. Find the following line:

            :DEL_CONFIG_LINE :MODE=PRIMARY

         3. Add the following lines below the line mentioned in STEP 2:

            DEVICE=%BOOTDRIVE%:\OS2\ATI0.SYS
            DEVICE=%BOOTDRIVE%:\OS2\VAD64.SYS
            DEVICE=%BOOTDRIVE%:\OS2\AITM64.SYS


 8.0  APARS INCLUDED IN THIS DRIVER
      _____________________________

  Some fixed APARs may not be listed. If you received this
  driver through the IBM OS/2 support channel and your requested
  APAR is not listed, please install the driver, as your
  requested APAR is included.

  APAR= PJ16653
  WITH THE ATI MACH64 IN HIGH RESOLUTION THE TESTCASE DRAWS A LINE
  OUTSIDE THE GIVEN AREA

  APAR= PJ16740
  VIOGETSTATE IN OS/2 FULLSCREEN SESSION RETURNS INCORRECT VALUES.


 9.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.

  Ami Pro                  Lotus Development
                           Corporation

  ATI                      ATI Technologies, Inc.

  CorelDRAW                Corel Corporation

  Lotus                    Lotus Development
                           Corporation

  Micrografx               Micrografx 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)


