1. xvl322cdinst.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (xvl322cdinst.zip)

==============================================================================
PCDirect samples for Auto RT Window:		          September 11, 1997

	RTAUTO32.EXE (for Win32 (Windows NT 4.0 and Windows 95))

==============================================================================

GENERAL DESCRIPTION:
====================

This sample demonstrates how to use an Automatic DIPIX created RT Window (Real-Time 
Display Window) which is a new addition to the XVL Library.  This window is a separate
child window from the main application window that makes use of Win32 multi-threading 
and Direct Draw v2.0 functionality to display camera image data real-time.  The Auto RT 
Window demonstrates the use of real-time scrolling and resizing capabilities (with 
sizeable border). 


SYSTEM REQUIREMENTS:
====================

OS: 		Windows 95 or Windows NT 4.0
MEMORY:		Minimum 8 Megs RAM, Suggested 16 Megs RAM
Video Card:     Direct Draw supported PCI Video Card
XVL Release:	3.20
OTHER:		Direct Draw v2.0
     

SOURCE CODE DESCRIPTION:
========================

The source code within the RTAUTO samples is structured as follows:

RTCOMMON.C	 Common Initialization code used by all PCDirect Aplication Samples.
RTSAMP.RC	 Common resource file used by all PCDirect Application Samples.	
RTAUTO.C         This is where the PCDirect Auto RT Window Library Calls are used.
RTAUTWIN.C       Message Processing Loop for Auto RT Window.
CMNDLG.C         Common File Dialog.


Upgrade Notes from 3.01 to 3.11:
================================

If the Windows 95 Auto RT Window from w32demo (release 3.01) is being
used with Release 3.10 DLL and OUT files, the following fixes needs to 
be performed in wdemo.c in order for the Auto RT Window to be operational 
with w32demo from release 3.01:

1)   Bus mastering option must be activated using DPK_UseBusMasteringMode
     function call prior to calling DPW_RTCreateDisplay.

2)   Handle of Parent Application Window (hDisplayWnd) needs to be 
     set in the calling sequence of DPW_RTCreateDisplay (In Release 
     3.01 it was set to NULL).

3)   In order for errors to be asynchronously communicated back to the 
     application from the XVL Library, the WM_XVLERROR windows message 
     needs to be added within the message processing loop in wdemo.c .  
     Secondly, WM_XVL_RTGRABCOMPLETE needs to be added to notify
     when the Single Image Grab or Multi Image Grab is complete.  Also, 
     WM_XVL_RTAUTODESTROY windows message is required when the Auto RT Window
     is destroyed using the System Menu Box located in the title bar. This
     message notifies the main application window that the Auto RT Window
     has been destroyed and as a result the appropriate menu options are 
     enabled.  Please refer to RTAUTWIN.C for sample code.
	
4)   Add in DPW_RTDestroyDisplay() call after DPW_RTKill() in wdemo.c .


Hints and Restrictions:
=======================
    
1)   In order to execute these samples make sure Direct Draw is installed.
     Direct Draw is already integrated within Windows NT 4.0.  For Windows 95,
     it must manually be installed using the DXSETUP.EXE located in \DIRECTX directory.

2)   The performance of PCDirect can be affected by other
     processes running in the NT and 95 OS environments. Both the disk
     drivers and mouse drivers on these platforms have high enough
     priorities to affect PCDirect's operation.

3)   Currently in this release the following Direct Draw anomaly exists: 
     If other application windows overlaps the RT Window, the live grab
     portion of the RT Window will draw on the overlapping window.  If the
     overlapping window is dragged away image data artifacts will remain.

4)   Only function calls labelled DPW_RT* may be called while using the
     PC Direct functionality.

5)   If the Error Occurs: "Critical Real Time Transfer Error: -200553XXXX" 
     where XXXX is a value between 1992 and 2667 then it is a Direct Draw Error.
     In order to determine which Direct Draw Error is occurring, the error needs 
     to be converted to hexadecimal value.  The least significant 4 HEX digits
     indicates the error code.  The decimal value of those 4 HEX digits is the 
     DDRAW Error Code.  This Error Code can be looked up in the DDRAW.H include 
     file in PC\INCLUDE.  There you will find a brief description for all of the
     exsiting Direct Draw Error Codes.  For example -2005532237 is equivalent to 
     0xFF887601B3.  The error code 0x01B3 is equivalent to 435 decimal which 
     indicates that it's the DDERR_CANTLOCKSURFACE DDRAW Error.

6)   It is not suggested to use ISA Video Cards with PC Direct.  There's been numerous
     problems reported using the PC Direct Application Samples with ISA Video Cards.

Known PCDirect Bugs:
====================

1)   Moving/scrolling window with XPG with 1 memory bank will
     occasionally cause frames to shift horizontally and vertically.

PCDirect Camera Restrictions:
=============================

1)  A maximum of 2 com ports are supported for grab transfers on any
    camera type (LinePair not supported in PC Direct).  The majority 
    of testing in this release was performed with single com port 
    using RS170 and CCIR cameras.

2)  The maximum camera bandwidth tested for FPG and LPG is:
        17 million bytes per second using 2 XDC com ports
        15 million bytes per second using 1 XDC com port
    Test performed on a Pentium 133MHz with Windows NT, Windows 95 
    performance was in the 13-14 Mb/s range. 2 com port does not 
    apply to the FPG analog.

3)  The maximum camera bandwidth tested for XPG populated with 
    memory on both buses. 
    global and local bus and using 2 XDC com ports for transfers.
        15 million bytes per second to VGA
        12.5 million bytes per second to memory.
    Test performed on a Pentium 133MHz with WindowsNT, Windows 95 
    measurement was not performed.

4)  The following grab features have been tested with PC direct, 
    Frame Holdoff and Frame Skip. Triggering, Exposure, LineSyncOut 
    and Reset have had minimal testing.

     
==============================================================================