Results of DOS VESA driver tests
		   ================================

The majority of the tests were performed on a Swan 486DB (66Mhz 486DX2
VLB). C was in an Olympic 486DX2 66Mhz. B was on a Dell Dimension XPS
P60 (PCI Bus). A was on a Toshiba 4400SXC (ISA bus). D was in a GateWay
2000 P60.


A Western Digital VESA 1.1 (Paradise SuperVGA WD90C31 1Mb)
B ATI SuperVGA (28800-5)
C Genoa Systems (1MB SuperVGA Model 7000 V1.2, 988 Tseng Lab)
D 86C801 ISA SuperVGA (S3 86C801/805)
E Trident 8900C
F Cirrus Logix 5422 ISA
G Award (NCR SuperVGA 77C22E)
H Ahead SuperVGA Wizard Deluxe V5.0
I TSeng Labs ET-4000
J VRAM II Ergo Bios V8.81 (Video7 HT209)
K Award OVGA Bios VN2.6 (77C22E)
L Oak SuperVGA Bios V1.05 (Chip 77) (OTI-077)
M Stealth VRAM v3.33 (S3)
N Viper VL 1.0 2Mb (UNIVBE- Weitck SuperVGA P9000+5182)
O Stealth 24 1Mb VLB
P Matrox Vision

Key

AU BU etc...

A,B,C etc are the adapter types as listed above
The U column is for the adapter with UNIVBE installed.

Mode                                 Adpaters

		  AU BU CU DU EU FU GU HU IU JU KU LU MU NU OU PU
320x200x8         ** ** *8 ** ** ** ** ** ** ** ** ** ** ** ** **
320x200x15         *
320x200x16                       **

640x400x8         **  *  8    **     *  *  *  *  *  *          7
640x400x15         1
640x400x16

640x480x8         **  *  8  * ** **  *  *  *  *  *  5 **  5 66 7
640x480x15         *        * 4  **  5           5     *    66
640x480x16                  *    **                         66

800x600x8         **  *  8  * ** **  *  *  *  *  *  * **  5 66 7
800x600x15         *          4  **  5           5
800x600x16                  * 4  **                         66

1024x768x8        22  *     * ** **  *  *  *  *  *  * **    66 7
1024x768x15                                      5
1024x768x16                 2                               6

1280x1024x8                 2                               2
1280x1024x15
1280x1024x16


1 Could not access mode because uses a mode number different from VESA
standard mode number.

2 Mode unavailable (presumably memory shortage/wrong monitor type).

3 Machine crashed when installing univbe.

4 Colors on the display were incorrect - unusable.

5 Crashed machine.

6 Glitch could occur depending on the mouse position. Consists of a
small block on the right hand side of the screen. Screen updates must
be the whole screen, mouse can only be in certain positions.

7 Used with Matrox's own VESA driver - UNIVBE does not function
correctly.

8 UniVBE crashed on installation. The vesa Window A is write only - so 
the cursors background is incorrect. Can cause screen corruption on areas
where RenderWare is not updating the screen.