600-RN-0012 Windows DDK ReleaseNotes 2 8 120

Release Notes Drivers and DLLs Kit (DDK) Windows
Edition 1 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009

2009 Validity Sensors, Inc. www.validityinc.com

RELEASE NOTES
DRIVERS AND DLLS KIT (DDK)
WINDOWS
EDITION
REVISION 2.8.120
SENSORS SUPPORTED
This release of the Drivers and DLLs Kit (DDK) for Microsoft Windows
supports the following Validity

Sensors models:
VFS201
VFS131
SOFTWARE
This release is compatible with the 32-bit and 64-bit versions of both Windows Vista
and Windows
XP.
The Validity Sensors Add/Remove Programs (ARP) version is 2.8.120
The Validity Sensors software build version is 2.8.1.20
FIRMWARE
The firmware version is hardware dependent.
VFS201
The firmware revision for VFS201 sensors is 3.72. The firmware patch level is H.
For example, a VFS201 ROM sensor with no SPI flash reports VFS201 ver 3.72H vc3.sys.r[0MB]
VFS131
The firmware revision for VFS131 sensors is 3.72. The firmware patch level is H.
For example, a VFS131 Flash sensor with no SPI flash reports VFS ver 3.72H vc1.sys.f-usb[0MB]
DEVICE DRIVER
The device driver is the WHQL-certified WinUSB driver from Microsoft, WinUSB.sys, and is version
2.1.0.2 and is dated 05/04/2009.
This device driver replaces the previous device drivers, including version 2.0.1.1 dated 11/24/2008,
version 2.0.0.1 dated 4/15/2008 and version 1.3.1.183 dated 2/6/2008.

Edition 2 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


WINDOWS_DDK_2_8_120

ENHANCEMENTS
1.
Included the Windows 7 WHQL-approved device driver version 2.1.0.2 and is dated 05/04/2009

ERRATA
This release of the Validity DDK has the following limitations:

1.
After upgrading the software, a manual system restart may be required in order for the fingerprint
sensor to function properly.

WINDOWS_DDK_2_8_117

ENHANCEMENTS
1.
Fixed upgrade issues with factory image on some systems
2.
On installation success, prompt for Reboot in normal mode. No prompt in case of silent installation, but
only after reboot the third party applications will work
3.
Driver installation changes to support multi language and to qualify MS OEM Ready tests

ERRATA

1.

WINDOWS_DDK_2_8_116

ENHANCEMENTS
1.
The installer ValiditySensorsSetup.exe will now upgrade over all previous versions

Edition 3 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


ERRATA

1.

WINDOWS_DDK_2_8_115
ENHANCEMENTS
1. The setup program is now named ValiditySensorsSetup.exe, replacing Setup.exe.
2. Several fixes related to MS OEM Readiness are in this release.
3. A problem where Validity Sensor would appear in the Safely Remove Hardware list has been
fixed. Validity Sensor no longer appears there.
4. The installer ValiditySensorsSetup.exe will now upgrade over all previous versions, including
upgrades on Windows Vista
32 and Windows
XP 32.
5. ValiditySensorsSetup.exe now includes Validity Sensors information such as version number,
company name, build number etc.
6. Dpinst32.exe & Dpinst64.exe are no longer found in \Program Files\Validity Sensors, Inc\ after
installation completes.
7. Obsolete information about installing unsigned drivers has been removed from this document.
ERRATA
1. None.

Edition 4 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


ENHANCEMENTS AND ERRATA HISTORY
WINDOWS_DDK_2_8_112
1. Modified Setup.exe to include Validity Sensors information such as version number, company
name, build number etc.
2. Dpinst32.exe & Dpinst64.exe are no longer found in \Program Files\Validity Sensors, Inc\ after
installation completes.
WINDOWS_DDK_2_8_109
1. Modified service to handle S3 resume within 100ms.
2. Installer will now upgrade over all previous versions.
NOTE: You must invoke Setup.exe using as Run as Administrator
3. Validity Sensor will no longer appear in the "Safely Remove Hardware" tray notification list when
Safely Remove Hardware is used.
4. File versions are changed to match installer version instead of using date as version.
5. Fixed service to recover properly from ESD events.
WINDOWS_DDK_2_8_108
1. This version corrects an issue found in ESD testing where the sensor would fail to recover after
reset.
2. The format of the File Version property is changed for built files to use the build version instead of
a timestamp: for example, the file version string on vfsEMPIRE_Sensor.DLL will be 2.8.1.8
instead of 2008.1024.1243.55.
WINDOWS_DDK_2_8_105
1. Fix a C3-SUSPEND-RESUME time issue that occurred with Digital Persona running.
2. Change product codes and WIX script to fix installation upgrade issues.
3. Fix an issue installing drivers on the Windows Vista

64-bit platform.
WINDOWS_DDK_2_8_102
1. This DDK replaces all previous device drivers with the WinUSB device driver from Microsoft to fix
all known blue screen (BSOD) issues on all platforms.
2. The driver reports its version number as 2.0.0.1, and is WHQL-certified.
3. The software has been modified to use the WinUSB device driver by default but is also
compatible with systems where only the older Validity device drivers are installed, such as
1.3.1.183.
WINDOWS_DDK_2_7_503
1. This DDK fixes a calibration issue on some small number of VFS201 units by patching the
firmware to version 3.72H. This firmware patch is primarily a yield improvement, rather than a

Edition 5 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


quality issue. The effect on end-users is negligible, but it does positively affect manufacturing
yield.
2. The DDK package numbering scheme will now reflect the Add/Remove Programs (ARP)
numbering scheme with three (3) numbers instead of four (4).
3. See Windows_DDK_2_7_0_51 below for notes device driver reversion.
WINDOWS_DDK_2_7_0_51
1. There are no changes to the WSDK code, only the device driver.
2. The device driver is reverted to the WHQL-approved version 1.3.1.183 dated 9/3/2008.
3. If installed over older DDKs with newer device drivers (DDK_2_7_0_45 to DDK_2_7_0_50
inclusive) the device driver will not revert.
4. If a newer device driver exists on the system you must remove the device driver from the system
for driver reversion to occur. See Removing Validity Drivers below for instructions on how to do
this before installing this DDK.
WINDOWS_DDK_2_7_0_50
1. The only change is the release of the WHQL-approved device driver version 1.3.2.1 dated
9/3/2008.
2. This new 1.3.2.1 device driver fixes all known blue-screen issues (BSODs) and fixes all known
driver memory leaks.
3. There are no code changes in the DLLs or vfsFPService.exe.
VFS201_DDK_2_7_0_49
1. Validity service (vfsFPService.exe) now creates all threads by inheriting the proper ACL from the
parent process. This fixes a critical security threat and should be deployed on platforms as soon
as practical.
2. Reverts to WHQL driver version 1.3.1.188 - if installed over DDK_2_7_0_47 driver will not revert.
VFS201_DDK_2_7_0_48
1. Avoid delays during system shutdown by modifying vfsEMPIRE_Sensor DLL to avoid API
timeouts when Validity service (vfsFPService) is shut down.
2. Reverts to WHQL driver version 1.3.1.188 - if installed over DDK_2_7_0_47 driver will not revert.
VFS201_DDK_2_7_0_47
1. A new WHQL driver version 1.3.1.190 fixes a BSOD (blue screen)
VFS201_DDK_2_7_0_46
1. A new WHQL driver version 1.3.1.188 fixes a BSOD (blue screen) that occurs when performing
WinPVT tests.
VFS201_DDK_2_7_0_45
1. A new WHQL driver version 1.3.1.186 fixes a BSOD when performing WinPVT tests.

Edition 6 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


VFS201_DDK_2_7_0_44
1. Fixed the issue of getting a dialog box and disappears in silent mode installation from command
line (setup.exe /s)
VFS201_DDK_2_7_0_43
1. Fixed the isssue(xbootmgr) with delay time in suspend test. Reduced the suspend delay time
from 5 secs to ~1 sec.
2. Fixed the issue with two accounts. Use account A installed the DDK but do not appear in User
Account B's ARP (add/remove program) panel. Both accounts are in administrators group and
install as administrator.
VFS201_DDK_2_7_0_39
1. The default value of fingerPollingPeriod is 50 instead of 10. This is believed to enhance most
systems performance without requiring Registry customization by improving communication
performance between the application and the sensor service to reduce CPU utilization. This
allows the CPU to enter into low power states (C5/C6) more frequently and improves battery life
accordingly.
VFS201_DDK_2_7_0_37
1. Improved communication performance between the application and the sensor service to reduce
CPU utilization. This allows the CPU to enter into low power states (C5/C6) more frequently and
improves battery life accordingly.
2. Improved error handling during reset and abort conditions to prevent sensor from becoming non
responsive during USB enumeration. Under low resource conditions, there were times when the
sensor would not enumerate properly, and the the host PC had to be restarted to get the sensor
reconnected.
3. Added a new event to indicate when a fingerprint capture during a call to vfsGetFingerprint() was
cancelled for some reason. This event, gfpEventPrintCaptureStopped, allows the application to
monitor this event and perform recovery action if necessary.
4. APIs now return disconnected status more quickly when device has been removed or reset. This
helps avoid some race conditions that might occur during standby and resume processing.
5. The software Build Number is now part of the DDK name.
VFS201-DDK1G
1. A deadlock was fixed in vfsFPService that occurred on machines with very heavy CPU loading or
machines that were very slow.
2. flashFromConfig now has a p option and reports success or failure with application Exit Codes:

Added -p option. The command line for flashFromConfig is now:

/* ********************************************************
*
* main
*
* Usage: flashFromConfig [arguments] [optional filename]
*

Edition 7 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


* Arguments
*
* -f : force-flash the firmware even if it is up to date
*
* NOTE: if -f is used it must be BEFORE the filename
*
* [optional filename] load vfs101Config from this file
* instead of the baked-in resource
*
* -n : Force-flash the firmware, and don't pause after reflash
*
* -v : Just display the existing firmware version but don't reflash
*
* -p : no-prompt: Check the version, and if out of date flash the
* firmware and don't pause after reflash
*
* Exit Codes:
*
* Exit codes are returned by flashFromConfig.exe to
* indicate errors or status of the sensor as follows:
*
* Code | Meaning
* -----| ---------------------------------------------------
* 0 | Flash is up to date
* 1 | Invalid command line parameters
* 2 | Configuration file can't be opened
* 3 | Invalid configuration file
* 4 | Sensor/Config file mismatch: Trying to reflash an
* | SPI image into a USB sensor, or vice-versa
* 5 | Sensor has no flash memory
* 6 | Flash failed
* 7 | Can't open sensor
* 8 | Failed to reopen sensor after flash
* 9 | Software exception trapped
* 255 | Flash succeeded
*/
VFS201-DDK1F
1. Improved image handling for people with soft fingers.
VFS201-DDK1E
1. A fix for sensor navigation issues where occasionally reverse scrolling would occur.
2. Very infrequently in specific system configurations dropped data would cause line data
synchronization issues. This would result in unintended reversals of scrolling motion in
unpredictable directions. A fix was applied to detect this condition and resynchronize the data,
eliminating this problem.

Edition 8 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


VFS201-DDK1D
1. A new WHQL driver version 1.3.1.183 fixes a timing bug in the driver that caused BSOD during
power stress testing. This only showed up on one system, but we feel it is something that could
show up elsewhere. The report from WHQL can be found here:
https://winqual.microsoft.com/LogoVerificationReport.aspx?sid=1280670
2. A modification to the finger polling frequency allows the CPU to enter into the C4 power state
more often. This improves notebook battery life by as much as 10 minutes on a 3 hour battery.
3. vfsEMPIRE_Sensor API now checks for an invalid sensor handle being passed in by client
applications. This prevents stale or invalid handles from being passed in by an improperly coded
application.
4. Fixed a USB enumeration problem that caused the sensor to remain disconnected until reboot.
This sometimes shows up in ESD test and rapid USB enumeration scenarios.
5. A fix is included for potential long delays that could occur before the software "sees" the sensor
as available after suspend and resume.

Edition 9 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


INSTALLING DRIVERS AT THE COMMAND PROMPT
Rather then launching the update programs through hyperlinks in this web page, the file
ValiditySensorsSetup.exe and/or the .MSI files can be run from the Windows
command prompt.
Command prompt installation allows options, such as silent install or log file creation, to be selected. To
install the drivers and DLLs from the command prompt, first ensure you are running as an administrator or
the command prompt window has administrator rights. A command window can then be open. In
Windows
XP, use Start > Run.

"ValiditySensorsSetup.exe /s" will install in silent mode either 32 or 64 bit depending on
platform.
If this is a clean install, you can run the MSI instead of the EXE and create a log file.
32-bit OS example:

"ValiditySensors_x86.msi /qn /l* c:\validity_install.log /i"

64-bit OS example:

"ValiditySensors_x64.msi /qn /l* c:\validity_install.log /i"
You can uninstall the software and create a log file using MSI instead of EXE:
32-bit OS example:

"ValiditySensors_x86.msi /qn /l* c:\validity_uninstall.log /x"

64-bit OS example:

"ValiditySensors_x64.msi /qn /l* c:\validity_uninstall.log /x"
MSI command line switches:
/q quiet mode - no prompts (same as /s with ValiditySensorsSetup.exe)
/n no UI
/l* log MSI actions to the specified file
/i install the MSI package
/x uninstall the MSI package

Edition 10 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


USING "RUN AS ADMINISTRATOR" IN WINDOWS
VISTA

When updating Validity drivers in Windows Vista
Command Prompt window, the "Run as

administrator" option must be chosen. To do this:
1) Left Click on the Windows
logo on the lower left of the screen:

2) Left Click on 'All Programs':

3) Left Click on 'Accessories':

4) Right Click on 'Command Prompt' and select 'Run as Administrator':

5) Change to the folder with the ValiditySensors_x86.msi and then run the commands as
shown above:
Example: "ValiditySensors_x86.msi /qn /l* c:\validity_install.log /i"

Edition 11 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


REMOVING VALIDITY DEVICE DRIVERS
Normally the device drivers installed by this DDK will not need to be removed. Updated
device drivers may be installed without first removing the older device drivers. If, for some
reason, it is required to remove the device drivers, the following command can be executed
in a DOS window:
for /f %f in ('dir /s /b /x %windir%\system32\DRVSTORE\vfs101* ^| findstr
.inf') do DPInst32 /U %f /D /Q
for /f %f in ('dir /s /b /x %windir%\system32\DRVSTORE\vfs201* ^| findstr
.inf') do DPInst32 /U %f /D /Q

Edition 12 of 12

600-RN-0012 Rev 2.8.120
June 4, 2009


FURTHER SUPPORT
If you need further assistance or clarification about anything in this document, please contact an
applications engineer at Validity Sensors.
Email: support@validityinc.com
United States toll-free: (877)733-8833
International customers: Please contact your area representative.

600-RN-0012 Windows DDK ReleaseNotes 2 8 120

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

600-RN-0012 Windows DDK ReleaseNotes 2 8 120

Cargado por

Copyright:

Formatos disponibles

Release Notes Drivers and DLLs Kit (DDK) Windows

supports the following Validity

XP, use Start > Run.

Command Prompt window, the "Run as

logo on the lower left of the screen:

También podría gustarte