Installation and configuration of various pads

Tablet driver installation

Here is a quick overview to install tablets:

• Wacom tablets: Wacom provides driver setups for the tablets. Please note that Wacom requires drivers optimized for the tablet. Always assure that you have the proper driver for your tablet hardware. Wacom drivers are accessed using the Wintab32 interface. Drivers can be downloaded at http://www.wacom.com

• Wacom SignPad tablets: SOFTPRO provides drivers for Wacom SignPad tablets. The latest drivers can be downloaded from the SOFTPRO website at http://www.softpro.de/en/support/download-signpad-driver.aspx
  Please note that SP_WspDrv.dll is not delivered as part of any standard SOFTPRO product. Note for manual installation: the minimum required driver is SP_WspDrv.dll.

• Interlink tablets: Interlink has a 'universal' driver to support most of their tablets. Please note that version 6.4 supports ePadInk, while version 7.1 does not support this type. The SOFTPRO access library for Interlink universal driver is SWILUniv.dll.
  Interlink is working on new drivers that support all different models, however the driver version 7.4 and version 7.5 does not yet support all required features.
  Drivers can be downloaded at http://www.interlinkelectronics.com

• TabletPC: SOFTPRO supports 3 methods to access TabletPC ink
  • HID device, install SWHDrive.dll, SWHHidLk.dll. This driver has the advantage that it is available right after boot time, while MS ink will be available after the user has logged in.
  • Ink-interface, install WTablet.dll to access the MS ink interface. The MS-ink driver has an improved handler for multiple overlaying windows.
  • WinTab, most TabletPC's are based on Wacom technology, which provides for Wintab32 interface. You can download the Wintab driver for TabletPC's from Wacom (www.wacom.com) The ink interface is the preferred method. The HID driver might pass stroke events even if the events actually should be consumed by overlayed windows. The Wacom 'penabled' (WinTab) driver might not handle tablet rotation correctly.

• StepOver tablets: StepOver distributes a dynamic library SOPad.dll with the pads. The SOFTPRO driver for StepOver pads is SP_SoDrv.dll. Please note that you must install the USB to Serial bridge in addition, if you have a StepOver USB pad.
  StepOver driver SoPad.dll must be Version 3.5.0.0 or higher, Version 3.5.1.3 and higher support 'No stroke echo' mode.
  Drivers can be downloaded at http://www.stepover.de

• Topaz tablets: Topaz distributes a COM component SigPlus.ocx with the pads. This COM component uses an ini-file SigPlus.ini, that must be located in the windows directory (typically C:\winnt or C:\Windows). The Topaz installer creates the ini-file and presets most values. The ini-file is ignored when using the SOFTPRO access module SP_TzDrv.dll.
  the SOFTPRO driver module SP_TzDrv version 1.1.0.0 and higher integrates the functionality of SigPlus.ini. Thus there is no need to configure any additional components to access Topaz tablets.
  The SOFTPRO access library for Topaz pads is SP_TZDrv.dll
  Drivers can be downloaded at http://www.topazsystems.com
  Restrictions
  • tablet disconnects cannot be detected accurately

Terminal server environments

Most tablets, namely StepOver BlueM, Topaz SE series and Wacom SignPad devices can be used in a terminal server environment. To date most terminal servers do not support USB interfaces, the devices will thus normally be operated using the serial port. The client (serial) port is typically mapped to a networked com port on the server, the port must not conflict with any physically available ports on the server. e. g. to COM6 on the server.
The network port will not be listed in the COM enumeration list, you will thus have to explicitly add the networked port to the list of checked ports, see Searching for installed tablets.

   # map the client COM port 1 to the server as network port COM 6
   net use COM6: \\Client\COM1:

   # add COM port 6 to the checked pad COM ports,
   # create a file Tablet.ini and in the proper device section
   # insert a line
   PadPorts = 6
   

Softpro also offers USB to Ethernet and USB to COM mappers (software drivers) to redirect a USB tablets to the terminal server, please contact SOFTPRO for more information.

Multimonitor environments

Fullscreen devices such as TabletPCs or Wacom Cintiq pads may be operated in a multiple monitor setup.
The pad may be operated in one of the following modes:

• Clone mode: the screen resolution must equal the native resolution of the pad
• Dual monitor mode: the pad screen resolution must be set equal the native resolution of the pad.
  The assignment (primary / secondary monitor) is detected based on the size of the monitor as reported by the host operating system, which may sometimes fail.
  If the monitor setup cannot be determined automatically then the correct monitor may be entered in the tablet configuration file tablet.ini, set the key MonitorIndex = 0 if the pad is the primary monitor, or MonitorIndex = 1 if the pad is the secondary monitor.

Please note, that multi-monitor setups which are only configurable with proprietary tools of graphics card manufacturers are not supported.

 # Example Tablet.ini
 MonitorIndex = 0
 # Assign the pad as the primary monitor

Searching for installed tablets

The default search sequence for WinTab drivers is:

• WTablet (TabletPC Ink-IF)
• SP_HidDrv (TabletPC HID driver)
• SWILUniv (Interlink Universal driver)
• WinTab32 (Wacom WinTab driver, MotionTouch, TabletPC WinTab)
• SP_WspDrv (SOFTPRO driver for Wacom SignPad)
• SP_SODrv (StepOver driver)
• SP_TZDrv (Topaz driver)

You may override the search order to start with a predefined device. Set FirstWT = drv in Tablet.ini to start searching for drv. Under Linux, only the Wacom SignPad is supported.

 # Example Tablet.ini
 FirstWT = SP_WspDrv
 # Search for Wacom SignPad driver and tablet, resume to normal search order if no
 # SignPad tablet was found on the host.

Configuration of tablets

SOFTPRO driver modules for Wacom SignPad, StepOver and Topaz tablets read the configuration file Tablet.ini to configure the serial port etc. The file Tablet.ini is searched

• in the folder of the executed application
• in the SOFTPRO subfolder of the user profiles folder (environment variable USERPROFILE)
• in the user profiles folder (environment variable USERPROFILE)
• in the SOFTPRO subfolder of the all users profiles folder (environment variable ALLUSERSPROFILE)
• in the all users profiles folder (environment variable ALLUSERSPROFILE)
• in the SOFTPRO subfolder of the application data folder (environment variable APPDATA)
• in the application data folder (environment variable APPDATA)
• in the system directories
• in the systems path (environment variable PATH)

Please note that applications may overrule the contents of the configuration file Tablet.ini.

These configuration options are available:

• the StepOver driver Module reads section [StepOver]:
  • CheckRegistryPad [0 | 1], default 1
    • 1: Read the registry string HKCR\Software\SOFTPRO\Pads\SO_Settings and check searching for devices based on this registry string.
    • 0: skip device detection based on the last found device
  • PadPorts list of ports to check, e. g. 1 2 3 to check COM1, COM2, COM3, pass an empty list to restrict device detection to one port which is read from the registry (if CheckRegistryPad is set). Default: check all ports that are defined in the system if ScanAllPorts is not set, or all possible ports if ScanAllPorts is set.
    Regions are defined with a '-' sign, e.g. enter 3 - 5 to specify ports 3, 4 and 5.
  • ScanAllPorts force a port scan over all ports [ 1 .. 127] rather than the registered ports (in Windows registry). Port scanning is restricted to the ports defined in PadPorts, if the entry exists. Default 0
  
  
• the Topaz driver Modules reads section [Topaz]:
  • CheckRegistryPad [0 | 1], default 1
    • 1: Read the registry string HKCR\Software\SOFTPRO\Pads\TZ_Settings and check searching for devices based on this registry string.
    • 0: skip device detection based on the last found device
  • CheckInstalledPad [0 | 1], default 1
    • 1: Check if a tablet is connected as it was installed using the Topaz setup. The Topaz setup creates a file SigPlus.ini that contains information about the tablet type, port and model, that will be used to identify the tablet.
    • 0: skip checking for a tablet as specified in the SigPlus.ini file
  • USBPad [0 | 1 | 2], default 0
    • 0: Check for serial and USB tablet
    • 1: Check for serial tablet, skip USB device checking
    • 2: Check for USB tablet, skip serial device checking
  • PadPorts list of ports to check, e. g. 1 2 3 to check COM1, COM2, COM3, pass an empty list to restrict device detection to one read from the registry (if CheckRegistryPad is set) or to the installed tablet (if CheckInstalledPad is set). Default check all ports that are defined in the system if ScanAllPorts is not set, or all possible ports if ScanAllPorts is set.
    Regions are defined with a '-' sign, e.g. enter 3 - 5 to specify ports 3, 4 and 5.
  • ScanAllPorts force a port scan over all ports [ 1 .. 127] rather than the registered ports (in Windows registry). Port scanning is restricted to the ports defined in PadPorts, if the entry exists. Default 0
  • AccessMethod [0 | 1 | 2], default 0, defines the interface to the device
    • 0: use the integrated access module, or the Topaz COM if an error occurred with the integrated access module
    • 1: always use the integrated access module. Note: the integrated modules also require the Topaz access module SigPlus.ocx
    • 2: always use the Topaz access module SigPlus.ocx

• the SOFTPRO driver Module for SignPad devices reads section [WSIGNPAD]:
  • CheckRegistryPad [0 | 1], default 1
    • 1: Read the registry string HKCR\Software\SOFTPRO\Pads\WSP_Settings and check searching for devices based on the contents of this registry string.
    • 0: skip device detection based on the last found device
    This option is ignored under Linux.
  • PadPorts: a list of ports to check, e. g. 1 2 3 to check COM1, COM2, COM3, pass an empty list to restrict device detection to one port which read from the registry (if CheckRegistryPad is set). Default: check all ports that are defined in the system if ScanAllPorts is not set, or all possible ports if ScanAllPorts is set.
    negative port numbers indicate the enumerated USB device, e. g. -2 uses the second USB device in the USB device table.
    Regions are defined with a '-' sign (preceded and followed by blank spaces), e.g. enter 3 - 5 to specify ports 3, 4 and 5.
  • PadHosts: a list of TCP addresses to search for tablets which are connected via a USB to TCP adapter from AK-Nord.
    Each entry contains the hostname or TCP address and the port number that must be separated by a colon (':').
    • IP V4 adresses are specified as 4 decimal coded octets, separated by dots ('.'). Example: 192.168.27.100:1002
    • IP V6 adresses are specified as 8 hexadecimal coded octets, separated by colons (':'). IP V6 adresses are enclosed by square brackets ('[', ']'). Example: [1:aabb::0]:1002
  • PadSocket: The TCP port number for USB to TCP adapters in a terminal server environment, see USBPad, value 8. This option is ignored under Linux.
  • ScanAllPorts: force a port scan over all ports [ 1 .. 127] rather than the registered ports (in Windows registry). Port scanning is restricted to the ports defined in PadPorts, if the entry exists. Default 0 This option is ignored under Linux.
  • SignPadTimeout: connection timeout in milliseconds, default 200 msec
  • USBPad [0 .. 15], 0 or a combination of 1, 2, 4, 8, and 16; default 0
    • 0: Check for Virtual channel, serial and USB tablet (Linux: USB only)
    • 1: Check for serial tablet (Linux: ignored)
    • 2: Check for USB tablet
    • 4: Check for tablets that are connected via a USB to TCP adapter from AK-Nord
      Note: TCP adapter connections must be explicitly enabled while the default setting (USBPad = 0) always searches for devices that are directly connected via serial or USB interface
      If you enable TCP search without specifying a host address then a broadcast message will be sent to discover devices within the local network. You will have to open port 1002 in your firewall settings for device discovery. Outgoing connections (connections during 'normal' operation) are not blocked by the standard firewall
    • 8: Check for tablets that are connected via a USB to TCP adapter in a terminal server environment, the adapter must run on the connected client, i. e. must be addressable with the clients IP address. The TCP port is set with the entry PadSocket. Not supported under Linux.
    • 16: check for tablets connected over a Virtual Channel (ICA or RDP). This requires installation of spvc32.dll or spvc64.dll on the client. The Virtual Channel will be checked first. Not supported under Linux.

    Note:

    SignPad enumeration lists devices connected to a COM port only if bit 0 in USBPad is set ((USBPad & 1) != 0).

  • InkThreshold [0 ... 1000]: Inking threshold, pressure value when the device draws a stroke in thousands of the maximum pressure
  • IdleImageFile_[Width]x[Height] IdleImageFile: File name of an image that will be displayed when the tablet is idle.
    you may specify different images for each device
    • STU300 reads the entry IdleImageFile_396x100
    • STU500 reads the entry IdleImageFile_640x480
    • STU520 reads the entry IdleImageFile_800x480
    All devices also read the entry IdleImageFile if no image was specified in the device specific configuration
    The image must be a monochrome Windows Bitmap (.bmp) with a size of 640 * 480 pixel for STU-500, or 396 * 100 pixel for STU-300, or 800 * 480 pixel for STU-520. Images for STU-520 may also be color images, 24 or 32 bit per pixel.
    The image will be displayed whenever an application disconnects.
    The image is located in the current folder, the application folder, the %APPDATA% folder, the %USERPROFILE% folder, the %ALLUSERSPROFILE% folder and in all folders listed in the %PATH% environment variable, or in the fully qualified path.
    This option is ignored under Linux.
  • STU-300, STU-500, STU-520 (DH-AES-128)
    • EncryptData: turn data encryption on or off, default: off. Setting up encryption mode takes approximately 1 second to calculate the keys. Encryption is not supported in standard SignPad devices. This parameter is ignored on standard SignPad devices.
      • 0: turn data encryption off
      • 1: turn data encryption on
    • CreateKeyTime: maximum time to create the encryption keys, default 0 (unlimited), recommended value > 600 [msecs]. The tablet will be reset if this time is exceeded. Encryption will be turned off after four retries.
      The key will be ignored if encryption is not used
    • CalcKeyTime: maximum timeto calculate the excryption keys, default 0 (unlimited), recommended value > 300 [msecs]. The tablet will be reset if this time is exceeded. Encryption will be turned off after four retries.
      The key will be ignored if encryption is not used
  • STU-430, STU-530 (RSA-2048-AES-256)
    • EncryptData: turn data encryption on or off, default: off.
      • 0: turn data encryption off
      • 1: turn data encryption on
    • RSAKeyEphemeral: controls whether keys are saved persistently or are regenerated for each process instance. Default: off.
      • 0: turn key persistence on
      • 1: turn key persistence off
  • USBMap: define the USB Mapping table source, default: use the USB enumeration list. This option is ignored under Linux.
    • registry; HKey\path
      read the mapping table from the registry, HKey may be HKLM (HKEY_LOCAL_MACHINE), HKCR (HKEY_CLASSES_ROOT), HKCU (HKEY_CURRENT_USER), HKU (HKEY_USERS) or HKCC (HKEY_CURRENT_CONFIG), the table is read from the key in successive values, 0 = FileName0, 1 = FileName1, where FileName{i} must be a valid file name for the desired SignPad device.
    • cfgfile; cfg_filename
      read the mapping table from a config file, cfg_filename equals the file name of the config file. The table is read from the file in successive keys, 0 = FileName0, 1 = FileName1, where FileName{i} must be a valid file name for the desired SignPad device.
    This option is normally set by the application, because the filenames are not really user readable names
    The device names are listed in the Device Manager
    • STU-500: Device Manager -> USB Human Interface Devices -> Details, Device Instance Id
    • STU-520: Device Manager -> Universal Serial Bus Controllers -> USB Composite Device -> Details, Device Instance Id

     USBMap = registry; HKU\Software\Softpro\SignPad
     the registry contains these values:
     HKU\Software\Softpro\SignPad\0 = USB\VID_056A&PID_00A1\5&28C564E5&0&3
     HKU\Software\Softpro\SignPad\1 = USB\VID_056A&PID_00A3\5&28C564E5&0&4
     will map the devices PadPorts = -1 to the file defined by HKU\Software\Softpro\SignPad\0
     and the device PadPorts = -2 to the file defined by HKU\Software\Softpro\SignPad\1
    

  • LcdBrighness: Set the brightness of the background illumination.
    The range is 1 (minimum light) to 255 (maximum light), default 255.
    Note: LcdBrightness is only supported on STU-520 devices, other devices ignore the entry. STU-520 & -530 can set the brightness in 4 steps, the equivalent thresholds are 0 .. 43, 44 .. 127, 128 .. 212, 213 .. 255.
    STU-520 saves the brightness in non volatile memory.
    It is recommended to use the SPWspChk.exe utility to set the contrast once, rather than setting the brightness in the configuration file.
  • ForegroundColor: Set the foreground color. Pen strokes will be drawn in a color ranging from BackgroundColor to Foreground color, depending on the pressure.
    Default: 0 (black), format 0xrrggbb, rr: red, gg: green, bb: blue
    Note: This feature is only supported on STU-520.
    The foreground color may be overruled by the application, the ini-file setting is provided to set the foreground color for 'older' applications.
  • BackgroundColor: Set the background color. Pen strokes will be drawn in a color ranging from BackgroundColor to Foreground color, depending on the pressure.
    Default: 0xFFFFFF (white), format 0xrrggbb, rr: red, gg: green, bb: blue
    Note: This feature is only supported on STU-520.
    The background color may be overruled by the application, the ini-file setting is provided to set background color for 'older' applications.
  • PenThickness: Set the pen thickness when drawing strokes on the display.
    Default: 85, range 1 ... 255, 1: thin, 85: medium, 170 bold
    Note: This feature is only supported on STU-520.
    The pen thickness may be overruled by the application, the ini-file setting is provided to set the pen thickness for 'older' applications.
  • IdleBackgroundColor: Set the background color when the tablet is idle. The idle background color will only be active when no idle image is loaded, else the idle image will overrule the idle color.
    Default: 0xFFFFFF (white), format 0xrrggbb, rr: red, gg: green, bb: blue
    Note: This feature is only supported on STU-520.
  The SOFTPRO driver Module for SignPad devices also reads the entries 'IdleImageFile_[Width]x[Height]', 'IdleImageFile', 'SignPadTimeout', 'EncryptData', 'CreateKeyTime' and 'CalcKeyTime' from the registry, if the entry is not defined in the configuration file. The settings are searched in the registry paths (in this order) HKEY_LOCAL_MACHINE\Software\SOFTPRO\Pads\SignPad\{port|host} and in HKEY_LOCAL_MACHINE\Software\SOFTPRO\Pads\SignPad. {port} expands to the port number which addresses the device, e. g. 1 for COM1, or -1 for the first USB enumerated device, host expands to the host name of the TCP adapter.

Note:

The majority of installations will not require a Tablet.ini file. The default configuration will be correct in most cases. However you will have to create a tablet configuration file e. g. if you want to access a Wacom SignPad device on a tablet PC, or if the tablet is connected via a redirected port e. g. in a terminal server environment (the redirected port is not entered in the registered COM interfaces).
Tablets connected via an AK-NORD adapter will in most cases require a tablet.ini file, at minimum to allow for TCP device discovery, however it is recommended to enter the hosts to search for a tablet.

Configuration examples

 # Example Tablet.ini configuration
 # StepOver section
 [StepOver]
 # Search for tablets connected to serial ports COM1, COM2, COM3 and COM4
 PadPorts = 1 - 4

 # Topaz section
 [Topaz]
 # Search for tablets connected to serial ports COM1, COM2, COM3 and COM4
 PadPorts = 1 2 3 4

 # Wacom SignPad section
 [WSIGNPAD]
 # Search for tablets connected to serial ports COM1, COM2, COM3 and COM4, and for the first USB device
 PadPorts = 1 - 4 -1
 # Set the connection timeout to 200 msec
 SignPadTimeout = 200

Utilities

SOFTPRO provides some utility applications for selected tablets on request.

• StepOver tablets
  The program SP_SoChk.exe may be used to check if a supported StepOver tablet is connected to the computer at the port as defined / specified in the configuration file Tablet.ini.
  SP_SoChk returns an errorcode 0 if a tablet was located
  SP_SoChk evaluates these command line parameters:
  • -delkey remove any registry settings that were created by the driver
  
  
• Topaz tablets
  The program SP_TzChk.exe may be used to check if a supported Topaz tablet is connected to the computer at the port as defined / specified in the configuration file Tablet.ini.
  SP_TzChk returns an errorcode 0 if a tablet was located
  SP_TzChk evaluates these command line parameters:
  • -delkey remove any registry settings that were created by the driver
  
  
• Wacom SignPad tablets
  The program SP_WspChk.exe may be used to check if a Wacom SignPad tablet is connected to the computer at the port as defined / specified in the configuration file Tablet.ini.
  SP_WspChk returns an errorcode 0 if a tablet was located
  SP_WspChk evaluates these command line parameters:
  • -brightness {n} set the display brightness, range 0 ... 255
  • -delkey remove any registry settings that were created by the driver
  • -echomode {0|off,1|on} turn stroke echo off or on
  • -idleimage {imagefile} load the image 'imagefile', or the default idle image as defined in the configuration file Tablet.ini if 'imagefile' is omitted.
  • -find {STU-300|STU-500|STU-520} find only STU-300 or STU-500 or STU520 devices
  • -init initialize the specified device, or all devices if not specified. Initialisation will turn off echomode and load the idle image if specified.
  • -port {nn} select the device connected to port nn for the action specified. nn defines a COM port if positive (e. g. 2 --> COM2) or a USB device if negative (e. g. -2 --> second enumerated USB device) (see Tablet.ini PadPorts parameter)..
  • -host {adress} select the device connected at host adress (see Tablet.ini PadHosts parameter).
  • -setUID {nn} Set the device unit identifier to nn, nn must be a number
  • -getUID Query the device identifier, the default is 0.
  
  SP_WspInit.exe calls SP_WspChk.exe -init to initialize all tablets. SP_WspInit.exe is invoked invisibly (no command prompt or any other visible window). SP_WspInit.exe must be located in the same folder as SP_WspChk.exe.
  SP_WspCpl.cpl will be installed in the control panel to configure Wacom SignPad devices. Please download and install the SOFTPRO SignPad driver to configure SignPad devices using SP_WspCpl.cpl.

Linux

The Wacom SignPad tablet is supported under Linux if connected via USB or TCP/IP.

To initialize the Wacom SignPad tablet (so that the USB tablet won't fill the message log with connect/disconnect messages), run

   SignPadInit default
   

(TODO: Describe how to use the quirks parameter of the usbhid kernel module.) (TODO: Document libspusb-1.0.so.0.)

Known issues

Microsoft reported in its knowlege base that serial to usb converters might slow down the serial communication speed under Windows XP. MS has published a fix, see details at Update for Windows XP (KB943198)

Unsupported Pads

SOFTPRO rejects all pads that are not explicitly supported and that are not produced by Wacom. The reason for this behaviour is that some clones on the market do not fulfill the requirements to verify a signature that was captured with that device.

Unknown Wacom devices without LCD screen will be treated like a Intuos, unknown Wacom devices with LCD will be treated as a PL 400.

These Wintab devices are defined in the tablet database:

• Wacom
  • PL 400
  • PL 510
  • PL 550
  • PL 720
  • DTU-1031
  • DTU-1631
  • Cintiq 12 WX
  • Cintiq 21 UX
  • Intuos (A6)
  • Intuos 3 (A6 W)
  • Intuos 3 PTZ 630
  • Intuos 3 PTZ 930
  • Intuos 3 PTZ 1230
  • Intuos 3 PTZ 1231W
  • Intuos 4 PTK 440
  • Intuos 4 PTK 640
  • Intuos 4 PTK 840
  • Intuos 4 PTK 1240
  • Volito (A6)
  • Graphire (A6)
  • Graphire 3
  • PenPartner (A6)
  • Bamboo (XP), (A6)
  • Bamboo (Vista +), (A6)
  • Bamboo One
  • Bamboo Fun, CTE-650
• MotionTouch
  • Digitizer LCD
  • Digitizer Non LCD
• Desko
  • SP 500

However pad manufacturers might offer newer models that could not (yet) be integrated in the SOFTPRO product suite. You may add the device into the tablet ini file (Tablet.ini) which will be read by SOFTPRO products and append any devices found in the ini-file to the list of supported devices.

The Device entries must be located in section WINTABPROPS, there must be one line per device. The Key must be named WTDevice_[n], where n is a sequential number, starting with 0.

The value is a semicolon (;) separated list, quote the semicolon (\;) to include it in the name if applicable. The list includes all of these values (in this order):

• Width the width of the tablet as reported by the driver [in mm]
• Height the height of the tablet as reported by the driver [in mm]
• SampleRate the sample rate of the tablet, typically set to -1 to read the sample rate from the driver
• Resolution the resolution of the tablet, typically set to -1 to read the resilution from the driver
• DeviceId the device id of the tablet, typically one of the predefined constants
  • PAD_PL400_DEV
  • PAD_INTUOS_DEV
  • PAD_GRAPHIRE_DEV
  • PAD_PENPARTNER_DEV
  • PAD_BAMBOO_DEV
• LcdType the type of LCD for the device, either one of:
  • 0: noLCD
  • 1: LCD is integrated in the pad, such as WTU-500
  • 2: PC screen is used, such as Wacom Cintiq 21UX
• Name the name of the device, should include the manufacturer and model, e. g. Wacom Bamboo One

Note:

Width and height are essential as these values are used to identify the device.

Examples:

 PAD_INTUOS_DEV = 1
 PAD_GRAPHIRE_DEV = 3
 PAD_PL400_DEV = 5
 PAD_PENPARTNER_DEV = 9
 PAD_BAMBOO_DEV = 23
 [WINTABPROPS]
 WTDevice_0  = 271; 204;  -1; -1; PAD_PL400_DEV;      2; Wacom PL400
 WTDevice_1  = 314; 238;  -1; -1; PAD_PL400_DEV;      2; Wacom PL510
 WTDevice_2  = 307; 230;  -1; -1; PAD_PL400_DEV;      2; Wacom PL550
 WTDevice_3  = 435; 327;  -1; -1; PAD_PL400_DEV;      2; Wacom Cintiq 21UX
 WTDevice_4  = 342; 275;  -1; -1; PAD_PL400_DEV;      2; Wacom PL 720
 WTDevice_5  = 220; 139;  -1; -1; PAD_PL400_DEV;      2; Wacom DTU-1031
 WTDevice_6  = 226; 129;  -1; -1; PAD_PL400_DEV;      2; Wacom DTU-1031X
 WTDevice_7  = 236; 134;  -1; -1; PAD_PL400_DEV;      2; Wacom DTU-1141
 WTDevice_8  = 346; 195;  -1; -1; PAD_PL400_DEV;      2; Wacom DTU-1631
 WTDevice_9  = 126;  96; 200; -1; PAD_INTUOS_DEV;     0; Wacom Intuos
 WTDevice_10  = 127;  92;  -1; -1; PAD_GRAPHIRE_DEV;   0; Wacom Volito
 WTDevice_11  = 129;  94;  -1; -1; PAD_GRAPHIRE_DEV;   0; Wacom Graphire
 WTDevice_12 =  81;  57;  -1; -1; PAD_PENPARTNER_DEV; 0; Wacom Penpartner
 WTDevice_13 = 147;  92;  -1; -1; PAD_BAMBOO_DEV;     0; Wacom Bamboo
 WTDevice_14 = 128;  93;  -1; -1; PAD_BAMBOO_DEV;     0; Wacom Bamboo One
 WTDevice_15 = 216; 135;  -1; -1; PAD_BAMBOO_DEV;     0; Wacom Bamboo Fun CTE-650
 WTDevice_16 = 208; 150;  -1; -1; PAD_GRAPHIRE_DEV;   0; Wacom Graphire 3

Known Limitations

A few limitation apply:

• Background images may not always be deleted on some StepOver LCD tablets after signature capture.
• Interlink driver 7.5.x does not save all persistent settings with ePad Ink USB.
• Wacom penabled driver for Tablet PC is not supported. Please use SOFTPRO Tablet PC drivers (WTablet.dll, TabletPC Ink-IF).
• Multi monitor support for Wacom full screen pads (such as Wacom Cintiq):
  • Clone mode is supported.
  • Dual view mode is supported.
    The screen resolution of the pad must equal the monitors native resolution.
  It may happen that the tablet monitor is not correctly detected. Add and entry in the configuration file (tablet.ini) to define the tablet monitor:
  MonitorIndex = iIndex
  where iIndex equals the (zero based) number of of the tablet monitor.
• Do not install a Wacom tablet driver (e. g. for an Intuos or any other Wacom Tablet) on a TabletPC. Most Tablet PCs use Wacom sensitizers with the according Wacom driver, but Wacom drivers do not support multiple devices.