To test signature capture use any of the following methods:
This test program is installed as part of the Signature SDK and started from the Start menu.
It can also be downloaded here: Capture Analyser
The test is a standalone application which does not use the Signature SDK COM components.
Start...Wacom Signature SDK...Capture Analyser
To test signature capture:
Service...Test Capture...(select the service name to match the capture device)
- signpad connects to an STU devices
- wintab connects to a Wacom tablet through the wintab driver, e.g. Intuos, DTU-1031X
A successful test will display the signature capture window:
Further menu options may be used by technical support for troubleshooting as required.
Run this test to capture a signature: SignHere.exe
The test calls the 32-bit Signature SDK ActiveX components to capture a signature:
The error message: 'Error: Retrieving the COM class factory for component with CLSID ...' indicates that the 32-bit Signature SDK components have not been installed.
Download and unzip the batch files from: Sign.zip The zip file contains:
Sign.bat - 32-bit signature capture derived from the Signature SDK samples Sign-64.bat - 64-bit version of signature capture
Start a Command Prompt (Start...cmd.exe) to run the batch file Sign.bat in a folder:
The test calls the 32-bit version of the Signature SDK ActiveX component, installed as the default in most cases.
The error message 'Microsoft JScript runtime error: Automation server can't create object' indicates that the 32-bit Signature SDK has not been installed.
To test a 64-bit Signature SDK installation use: Sign-64.bat
The batch file uses the 64-bit version of cscript to call the Signature SDK ActiveX component.