Here's how I installed the Trident 32-bit drivers:

1.  You must go back to the standard 32 bit 640x480x16 drivers that are
    installed after the service pack.  This is required!  You can do this
    by using Selective Install (or Device Driver Install if you backed up
    your original driver and stored it in a safe location.)  Be sure to get
    the standard VGA drivers working beforing you attempt to install the
    Trident drivers.

2.  Backup the following files:
    \OS2\SVGA.EXE
    \OS2\DLL\BVHSVGA.DLL
    \OS2\DLL\IBMDEV32.DLL
    \OS2\DLL\IBMVGA32.DLL
    \OS2\DLL\*.FON

3.  Replace \OS2\MDOS\SVGA.EXE with the one included in the archive.  Run
    SVGA ON DOS.  This will create a file called SVGADATA.DOS.  Note that
    the old SVGADATA.PMI and this SVGADATA.DOS are in fact different, so
    you will have to replace it.  (Don't do any copying yet, just follow
    the rest of these instructions.)

4.  Boot from a floppy.  (If you are running FAT, a DOS boot disk is fine,
    or if you have HPFS on your C partition, you must use an OS/2 boot
    diskette.  If you haven't created an OS/2 boot diskette, use the first
    two diskettes from the original install diskettes.  When the IBM OS/2
    white screen appears, press ESC, which will give you an OS/2 full screen
    session.

    Once you are at a DOS or OS/2 prompt, continue with these instructions:

5.  Replace \OS2\DLL\BVHSVGA.DLL with the one in this archive.

6.  Replace \OS2\DLL\IBMDEV32.DLL with one of the Trident 32-bit drivers.
    In this archive, they are named the following:
      640DEV32.DLL    640x480x256 32-bit Trident driver
      800DEV32.DLL    800x600x256 32-bit Trident driver
      1KDEV32.DLL     1024x768x256 32-bit Trident driver

    Be sure to rename the appropriate driver of your choice to IBMDEV32.DLL
    and place it in the \os2\dll directory.

7.  Replace \OS2\DLL\IBMVGA32.DLL with the one in this archive.

8.  Type INSTALL.  (This runs INSTALL.BAT or INSTALL.CMD depending if you are
    in a DOS or OS/2 session.)  This replaces your existing .FON files
    (fonts) with the ones included in this archive.

9.  Backup \OS2\SVGADATA.PMI (you couldn't do this until you had booted from
    a floppy.)

10. Replace \OS2\SVGADATA.PMI with the \OS2\SVGADATA.DOS created in step 3.

11. Reboot.  You should have the 32-bit drivers working.

NOTES:

1.  This installation doesn't even touch DISPLAY.DLL.  You must keep the
original DISPLAY.DLL there, as it does NOT control the display in the SP.
Read \README for more details. (It acts as a passthrough to IBMDEV32.DLL)


Installing the Windows drivers:
---------- --- ------- --------

Modifications necessary to run the combined windows drivers:
Edit SYSTEM.INI in your Win-OS/2 directory and add:

In the [boot.description] entry:
display.drv=<resolution> <font size> <memory> <chip type>
sdisplay.drv=<resolution> <font size> <memory> <chip type>

Where <resolution> can be: 1024x768x256
                           800x600x256
                           640x480x256

Where <font size> can be: Large fonts
                          Small fonts

NOTE: Use Large fonts for 1024x768x256  FS (WSPDBF.DRV) Seamless (WSPDSBF.DRV)
      Use Small fonts for 800x600x256   FS (WSPDSF.DRV) Seamless (WSPDSSF.DRV)
                          640x480x256   FS (WSPDSF.DRV) Seamless (WSPDSSF.DRV)

Where <memory> can be: 1M
                       512K

Where <chip type> can be: ET4000
                          ATI
                          IBMVGA256c
                          Paradise
                          Video7
                          Trident

Example of 1024x768x256 for Trident with 1 Meg:

[boot]
sdisplay.drv=wspdsbf.drv
display.drv=wspdbf.drv

[boot.description]
display.drv=1024x768x256 Large fonts 1M Trident
sdisplay.drv=1024x768x256 Large fonts 1M Trident

...

display.drv=640x480x256 Small fonts 1M ET4000
sdisplay.drv=640x480x256 Small fonts 1M ET4000

display.drv=800x600x256 Small fonts 1M ET4000
sdisplay.drv=800x600x256 Small fonts 1M ET4000

NOTES ON THE WIN-OS/2 DRIVERS:

1.  If you run a Win-OS/2 application seemlessly, and your palette
    gets altered, go to Control Panel and remove any background
    .BMP, and just use a solid color.  While it may not be as pretty
    for your Win-OS/2 full screen sessions, it usually eliminates
    the palette problems.