---------------- INSTALLING VESA BIOS EXTENSION DRIVERS ---------------

DRIVERS2.EXE is a self extracting archive file which contains the 
VESA BIOS Extensions.  When executed, it will create subdirectories for 
each of the video adapter manufacturers.  Within each subdirectory, it
will place the respective VESA driver.  To execute:

      1. Get into the directory where you want the subdirectories 
         to be created.
      
      2. Copy the file DRIVERS2.EXE into this directory.
      
      3. type drivers2 -d  (the -d tells it to create subdirectories).
      
----------------        WHATS NEW IN DRIVERS2.EXE       ---------------

The DRIVERS2.EXE archive has new VESA BIOS drivers for Western Digital, 
Tseng, Trident, ATI, Orchid, Video7, and Paradise products.  These new
drivers solve many problems. Specifically, the VSA256 Graphics Library 
was written for the VESA BIOS Standard version 1.1 and up.  Many of the
old drivers were written for VESA BIOS Standard version 1.0.  The new 
drivers either support version 1.1 or 1.2 (both okay for us). 

-------------- WHATS NEW IN VSA256 GRAPHICS LIBRARY V1.1b -------------

1.) Corrected a bug which caused it to improperly write to graphics memory
    (ie. not work) on Paradise cards (and any card which provides window 
    resolution not equal to 64k).  All the data used to pile up at the top 
    part of the screen.  Now it works correctly.

2.) Put in detection for VESA BIOS EXTENSION TSRs which do not support
    Text I/O in SVGA modes.  In these cases (such as ATI driver) Graphics 
    will still work but vsa_set_text_cursor, vsa_write_char, 
    vsa_write_string, and vsa_write_string_alt now will do nothing (instead 
    of trying to write and thus mucking up the display). 

3.) Put in better exception handling to detect no VESA BIOS loaded, un-
    supported video modes, etc.

--------------------------- Trouble Shooting --------------------------
    
1.) If Text seems to be readable but goes in wrong locations on screen,
    try manually changing the YCharResolution and YCharSize parameters
    after running vsa_init.  Some of the older VESA BIOS TSRs report the
    wrong YCharsize value (ie. 8 pixels when really 16 ... Trident in 
    mode 103  ... Paradise )

2.) Borland C version 2.0 always seems to give a stack overflow error 
    when code is compiled in small memory model.  Use large memory model 
    if you get this until I can figure out problem.  Microsoft doesn't 
    have this problem.