***************************************
*     PCAM R2.19a README.TXT FILE     *
***************************************

Copyright (c) 1999-2000 Divio Inc. All rights reserved.

Note  : Before you do the installation please change pcam2.inf in your working directory the correct 
        "CCDType" and "CDSType" values and the correct R/G/B values (RedHue_Office, GreenHue_Office,
        BlueHue_Office, RedHue_Home, GreenHue_Home, and BlueHue_Home) to the corresponding CCD.

        For CCDType: 0 - Sharp CCD
	             1 - Sony CCD
		     2 - Panasonic CCD
		     3 - Fuji CCD
        For CDSType: 0 - Sharp CDS
	  	     1 - Hitachi CDS (HD49322)
		     2 - Panasonic CDS
                     3 - Fuji CDS
                     4 - Hitachi CDS (HD49323AF or HD49323F)
                     5 - TasCorp CMOS sensor (Special)

A. What's new in this release after R2.18e:

1.  Added RGB 555 / RGB 565 (16-bit) video format support.  In Windows registry, under
    HKEY_LOCAL_MACHINE/Software/Divio Inc/Pcam directory, a key "SupportRGB565" is added.
    Set "SupportRGB565" to 0, the minidriver will support RGB 555.  Set this key to 1, the
    minidriver will support RGB 565.  Either RGB 555 or RGB 565 can be supported at one time.
    In order to show the right video, the color depth of the system need to be set to 
    High Color (16 bit).  The 24 bit color depth setting will cause color effect.
    Due to RGB 555 is more popular than RGB 565 in graphic card manufactures, the default
    value of SupportRGB565 will be set to 0 (RGB 555).  Some graphic cards support both 
    RGB 555 and RGB 565, by using this graphic card both RGB 555 and RGB 565 setting work
    o.k. in the minidriver.  However, if your graphic card only support RGB 555, the setting
    of RGB 565 will cause color effect.  The driver can not automatically detect the graphic
    card capability at this time.

2. Fixed Auto Exposure hunting of TASC sensor in some light conditions.  The AE hunting
   is caused by the auto frame rate slow down function.

3. Fixed a bug of RGB-16 video format in VideoForWindows applications (e.g. VidCap32.exe).
   The VfW interface does not support RGB-16 subformat as WDM architecture does and this
   causes VfW pops up error message "Video format does not support" while the user selects
   RGB-555 video format.
