FAQs

FAQs

  • Overview
  • FAQs
  • Support
  • GitHub

›SDK for signature

Introduction

  • Wacom Ink SDK - FAQs

Downloads

  • SDK Downloads
  • Licensing

Request Support

  • Support

STU Tablet

  • STU Installation
  • STU-430V Installation
  • STU-540 Operating Modes
  • STU-540 Serial Installation

STU SDK

  • Installation
  • Programming queries
  • Runtime issues
  • STU SigCaptX

Enterprise Tablet Installation

  • General Installation
  • Driver Installation & Troubleshooting
  • Pen Configuration & Troubleshooting
  • Configuration and customisation

SDK for Ink

  • WILL SDK for ink v2
  • WILL SDK for ink v3

SDK for devices

  • Wacom Ink SDK for devices

SDK for signature

  • Licensing
  • Installation
  • Programming Queries

    • General
    • STU
    • DTU
    • Biometrics
    • Error Messages
  • SigCaptX
  • How to guides

SDK for multi-display

  • Wacom Ink SDK for multi-display

Wacom Applications

  • sign pro PDF - Version 3
  • sign pro PDF - Version 4

    • Contents
    • FAQs
    • User Guides
    • API

    sign pro PDF - Android

    • Contents
    • API
  • Installation Issues
  • Signature Scope
  • plugin for Acrobat Reader

Compatibility tables

  • Overview
  • Compatibility tables

    • Web Browsers
    • SW Compatibility
    • Desktop and mobile
    • Wacom Applications

Installation

Deploying the Signature SDK

  • Installation
    • UI Installation
    • Command Line Installation
    • Examples

Installation

The SDK is installed as a set of ActiveX/COM components in the folder:

     C:\Program Files\Common Files\WacomGSS

When the 32-bit version is installed on 64-bit Windows the components are installed in:

     C:\Program Files (x86)\Common Files\WacomGSS

Language translation files are included with the installation so that the native Windows language is used in the signature capture dialog.

The installation requires COM registration with a number of supporting entries in the Windows registry and this is achieved by running the SDK MSI installer.
Due to the complexity of the installation process it is not practical to mimic the operations with a script but a number of options are provided for automation.

UI Installation

Run the installer to display the options dialog:

Custome setup

Options are included for Java and .Net components.
Following an installation the installed files can be seen in Common Files\WacomGSS folder, for example:

Installed files

.NET ComponentsJava ComponentsActiveX ControlsLanguage Translation FilesSupport Files
Florentis.InteropAxFlSigCOM.dllflsx.dllFlSigCapt.dlldeFlCaptureAnalyzer.exe
Florentis.InteropAxFlWizCOM.dllflsx.jarFlSigCOM.dllenwgssStuImgUploader.exe
Florentis.InteropFlSigCapt.dllwgssLicenceJNI.dllFlWizCOM.dlles
Florentis.InteropFlSigCOM.dllwgssLicenceJNI.jarwgssLicenceClient.dlletc.
Florentis.InteropFlWizCOM.dll

 
To add Java or .NET components after an installation run the installer again and select the Change option in Windows to redisplay the options dialog.
In addition to the creation and registration of component files, items are added to the Windows Start menu: Wacom Signature SDK.

Command Line Installation

Use the command line to tailor the installation by using the standard Windows MSI installation application.
For example to install the minimum components for a Java application with no Start Menu options:
 

 msiexec /q MINIMAL=1 JAVA=1 /i Wacom-Signature-SDK-x86-3.20.4.msi

 

A number of options are available so that specific components can be installed with or without a full SDK installation:

OptionDescription
MINIMAL=1Exclude Windows shortcuts and utilities
JAVA=1Include Java Components
DOTNET=1Include .NET Components
WIN32=0Exclude x86 components from x64 installer (by default the x64 installer will install both 32- and 64-bit components)
ADDPATH=Win32Add 32-bit component folders to system PATH
ADDPATH=Win64Add 64-bit component folders to system PATH
WIZARDSHOWWAIT=0Disable the hourglass icon displayed by the Wizard control on the STU-430 and STU-530
STUSHARED=1Use shared (non-exclusive) access to an STU tablet

Examples

DescriptionCommand
Install the SDKmsiexec /i Wacom-Signature-SDK-x86-3.20.4.msi
Install the SDK with no UImsiexec /q /i Wacom-Signature-SDK-x86-3.20.4.msi
Install the SDK with Java componentsmsiexec JAVA=1 /i Wacom-Signature-SDK-x86-3.20.4.msi
Install components for an IE HTML applicationmsiexec /q MINIMAL=1 /i Wacom-Signature-SDK-x86-3.20.4.msi
Install components for a Java applicationmsiexec /q MINIMAL=1 JAVA=1 /i Wacom-Signature-SDK-x86-3.20.4.msi
Create a log filemsiexec /q /l*v log.txt /i Wacom-Signature-SDK-x86-3.20.4.msi
Uninstallmsiexec /x Wacom-Signature-SDK-x86-3.20.4.msi

Can I install the Signature SDK without user input?

Installer options are listed above.

To summarise:

The quiet option allows a UI free installation as illustrated below.
 

msiexec /q /i Wacom-Signature-SDK.msi 

The signature of installer.msi is corrupt or invalid

This is a known issue when downloading our installers on Windows 10. You should find that the files have in fact been downloaded and that you can still execute them.

If needed the following workarounds may help:

  1. Turn off the SmartScreen filter temporarily in Control Panel under Security as described here.
  2. Add https://gsdt.wacom.eu as a trusted site in your internet options (assuming you downloaded the installers from there)

If none of the above helps please raise a Support Ticket.


Windows 7 cannot verify the digital certificate

Having installed our STU or Signature SDK you may encounter the following error message when trying to run an application which has been built with them:
 

    Windows cannot verify the digital certificate for this file. A recent hardware or software change
    might have installed a file that is signed incorrectly or damaged, or that might be malicious
    software from an unknown source.

 
This situation was first encountered after applying a stricter digital signing method to Wacom executables and DLLs and is mainly found on Windows 7.
The additional protection was applied to prevent the possibility of files being modified.

The error message will not be reported if Windows has been fully updated using Windows Update.
If it is not possible to apply the full Windows Update, this specific update will usually resolve the issue: KB 3153171

The update can be downloaded from Microsoft.com:

  • KB 3153171 - 32-bit
  • KB 3153171 - 64-bit

What options are there for silent installation, repair or uninstallation of the SDKs and STU driver?

STU SDK + SIGNATURE SDK

SilentCreate log fileRepairUninstallPrevent restart
Use /q, e.g. msiexec /q /i Wacom-STU-SDK-2.13.6.msiAdd: /l*v logfile.txtReplace /i with /fReplace /i with /x/norestart

STU DRIVER

Silent without the "plugged in" checkCreate log fileRepairUninstallPrevent restart
wacom-stu-driver-5.4.2.exe NO_STU_CHECK=1 /install /quiet/log log.txtReplace /install with /repairReplace /install with /uninstall/norestart

 

Log files are created by default in %TEMP%.

If you run the STU Driver installer while an STU is connected to the PC there is a possibility that certain registry settings may not be updated.

For this reason it would be safest to restart the PC afterwards.


← LicensingGeneral →
  • Deploying the Signature SDK
  • Can I install the Signature SDK without user input?
  • The signature of installer.msi is corrupt or invalid
  • Windows 7 cannot verify the digital certificate
  • What options are there for silent installation, repair or uninstallation of the SDKs and STU driver?
FAQs
DOCS
IntroductionLicensingWacom Applications
COMMUNITY
TwitterLinkedInGitHub
ABOUT
Terms of UsePrivacyCookies
Wacom Developer Relations
Copyright © 2023 Wacom. All Rights Reserved. All other trademarks are the property of their respective owners and are used with their permission.