This is a program to test the ENDIVE
implementation on OS/2 systems.
It uses only the DevEscape function to
query which functions are supported.
And if supported calls 2 addional ENDIVE query
functions (via DevEscape) to get some more detailed 
information. 

The reason for this program is that the DirectX implementation
in WINE moves all the data in SW (memcpy). While the old
code uses DIVE. When there is no ENDIVE support from the
driver DIVE uses SW itself so there shouldn't be a speed
impact if we/I remove this.
But we could gain some speed if we use ENDIVE directly to
do the blits.

So please run the program on your system and report (via mail)
if ENDIVE is supported and If which card/driver and resolution
you are running in.
Especially users which have a GRADD based driver (SDD/ IBM / NVidea)

This will help determine if I/we should spend some more time
on ENDIVE and/or if we should abandon DIVE totaly (at least for blitting)
as this will make the code more compatible with WINE.

Using the program:
The program comes with a Notebook layout:
on the first 3 pages you will see a button which you have to press to query the values
for the page.
The Button on Page 3 (2nd of ENDIVE) is special as it will only be enabled if the
ENDIVE function DEVESC_QUERYFB is supported but not DEVESC_EXTQUERY.
If DEVESC_EXTQUERY support is reported by the driver the Data will automaticly be
collected when you press the button on the 1st ENDIVE page.

On the Reports page you find a textual version of the report.
use the contextmenu (RMB) to either save/copy the report so you can send it.
If you want to reduce the rainforest and do something for global warming you can
even print the report from the contextmenu ;)

History:
 V 0.97 
   Inital release
 V 0.98 
   Fixed bug if multiple codecs/colors are returned 
   (most cards so like mine only returned 1 so it didn't show up on my system)
   Fixed display problem with lowres fonts

Send Reports to:

mmontkowski@norman.de
subject: ENDIVE-Test


Thanks
Markus
