STU HID Diagnostic Tool
Installation of an STU tablet.
Colour models require the STU driver
Download and unzip the diagnostic to run on 32 or 64 bit Windows.
Download and use the tool according to the directions provided by your support engineer.
Normally you will need to run the following command in a Dos prompt and email the resulting text file:
C:\Test>hidinfo.exe all > hidinfo.txt
Syntax: hidinfo [options]
- filename displays underlying filename
- kernel displays kernel handle
- attr displays HID attributes as reported by HidD
- caps displays the report IDs of the capabilities
- all displays everything
- /? help
Run hidinfo.exe using a Command Prompt:
The STU device report should be similar to one of the following examples:
056a:00a2:0068 [xRW] Manufacturer="Wacom Co.,Ltd." Product="STU-300" SerialNumber="\x0409"
056a:00a1:0101 [xRW] Manufacturer="Wacom Co.,Ltd." Product="STU-500" SerialNumber="\x0409"
056a:00a3:0101 [xRW] Manufacturer="Wacom Co.,Ltd." Product="STU-520A" SerialNumber="\x0409"
In the examples shown, the device accessibility is described as [xRW]
- The first character ('x' or 's') denotes exclusive or shared access.
- The second character ('R') denotes read access.
- The third character ('W') denotes write access.
Note: By default the signature software requires exclusive-read-write access to the device to operate successfully.
In some installations other applications or installed drivers may access the device in shared mode.
In this case, only shared access is possible: [sRW] indicates the device is only available for shared-read-write access.
Note, this will prevent the signature software operating successfully.
If another application has opened the device for exclusive access, then "hidinfo" will be unable to open the device and will report an error.
This is typically:
[Open failed] [system_error: win32api:32 The process cannot access the file because it is being used by another process. ]
"hidinfo" determines the available access by a process of elimination using standard API calls to the Windows CreateFile API.
It will try in sequence:
CreateFile(fileName, GENERIC_READ|GENERIC_WRITE, 0 , ...
CreateFile(fileName, GENERIC_READ , 0 , ...
CreateFile(fileName, 0 , 0 , ...
CreateFile(fileName, GENERIC_READ|GENERIC_WRITE, FILE_SHARE_READ|FILE_SHARE_WRITE, ...
CreateFile(fileName, GENERIC_READ , FILE_SHARE_READ|FILE_SHARE_WRITE, ...
CreateFile(fileName, 0 , FILE_SHARE_READ|FILE_SHARE_WRITE, ...