Scriptel Wiki - User contributions [en]

Troubleshooting ScripTouch Remote on Windows

2018-10-19T19:21:34Z

Michael Powers: /* Per User Registry Entries */

[[Category:ScripTouch Remote]]
ScripTouch Remote is an installed piece of software that bridges the gap between Citrix and Remote Desktop clients and their associated servers to allow the use of ScripTouch signature digitizers on remote systems transparently. Usually using the software is as simple as installing the software and licensing it, but sometimes things go wrong.

This guide contains a list of things to check to ensure ScripTouch Remote is installed, configured, and working correctly.

==Testing ScripTouch Remote==
The simplest way to test to see if ScripTouch Remote is working is to use Citrix or RDP to connect to a remote server and start [[ScripTouch Sign and Save]] on the server. If everything is working correctly you'll see something like the following:

[[File:ScripTouch_Sign_and_Save_-_ScripTouch_Remote_Example.png]]

Notice the "Connected to ST1550" in the lower left, along with the green indicator. Also in the File -> Connect menu you can see the Citrix Receiver icon next to the device which indicates the device is connected through Citrix.

If the connection indicator in ScripTouch Sign and Save is grey and says "Disconnected" this means that ScripTouch Remote is not working correctly.

==Verify Licensing for ScripTouch Remote==
ScripTouch Remote is a licensed feature. If you need to get a license for ScripTouch Remote you can fill the form on [http://scriptel.com/developers/scriptouch-remote/ this page] and someone will get in contact with you. If you've already acquired licenses you can verify that you're licensed for ScripTouch Remote using the [[ScripTouch Toolbox]]. Once you download and install the software you can verify that you're licensed by navigating to Help -> License Viewer. This should be done on the local machine (the computer with the signature pad plugged into it).

If you're appropriately licensed you'll see the 'enable_citrix' and 'enable_rdp' entitlements in the 'Entitlements granted to this computer' section:

[[File:ScripTouch_Toolbox_License_Viewer.png]]

If you don't see any entitlements in the 'Entitlements granted to this computer' section:
*Verify that the licensed device is plugged in to the computer. If the correct device isn't plugged in you'll see items in the 'Entitlements not granted to this computer (and why)' box indicating which device(s) you're licensed for.
*Verify the license file is installed in one of the following locations (paths are shown in the 'License Files Found' section in the toolbox):
**%APPDATA%\Scriptel\Licenses
**%ProgramFiles%\Scriptel Corporation\Licenses
**%ProgramFiles(x86)%\Scriptel Corporation\Licenses

If you need to download the license file for your organization, you can retrieve it through our [https://scriptel.com/portal Licensing Portal] or you can use the ScripTouch Toolbox to retrieve the license file by doing the following:
*Go to Settings -> Online Settings
*Fill in the E-mail Address and Password sections (if you've forgotten your password you can reset it [https://scriptel.com/portal here]).
*Hit the "Check Credentials" button and wait for confirmation that your credentials are valid.
*Verify the Primary Organization matches the organization you're looking to get a license file for and hit "Save".
*Click the Settings -> Enable Online button.
*Click Settings -> Check for Licenses, this will download the license file for your organization to your user profile.

If you believe you should be licensed but these steps don't resolve licensing issues please contact Scriptel support at +1 (844) 972-7478 or support@my.scriptel.com.

==Check that ScripTouch Remote is Installed==
ScripTouch Remote currently comes in two forms: bundled in the [[ScripTouch Sign and Save]] application as well as in a standalone package available [https://services.scriptel.com/releases/scriptouch-remote/scriptouch-remote-windows here]. Both packages install similar components and either should enable ScripTouch Remote to function.

===Verify Citrix Installation===
In order for the Citrix components to install correctly ScripTouch Remote must be installed after the Citrix Receiver. If the Citrix Receiver is not detected during installation this component is skipped. To verify the installer installed the required components for Citrix please check that the following on the local computer (the computer with the pad plugged into it):

Make sure the following files exist:
*C:\Program Files (x86)\Citrix\ICA Client\scriptel-citrix-virtual-channel-x32.dll

Make sure the following registry items exist (drop the 'WOW6432Node' if you're on a 32-bit Windows installation):
*HKLM\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ICA 3.0
**VirtualDriverEx should be a REG_SZ value and contain 'Scriptel' (it's ok if it contains other items as well, any other items should be separated by a comma).
*HKLM\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Scriptel
**DriverName should be a REG_SZ value and contain 'scriptel-citrix-virtual-channel-x32.dll'.
**DriverNameWin32 should be a REG_SZ value and contain 'scriptel-citrix-virtual-channel-x32.dll'.

===Verify Remote Desktop Installation===
The Remote Desktop component is always installed. Installation is performed as outlined in the [https://msdn.microsoft.com/en-us/library/aa383583(v=vs.85).aspx Microsoft Documentation]. To verify the installer installed the required components for RDP please check the following:

Make sure the following files exist:
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Sign and Save\scriptel-rdp-virtual-channel-static-x32.dll
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Sign and Save\scriptel-rdp-virtual-channel-static-x64.dll
OR
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Remote\scriptel-rdp-virtual-channel-static-x32.dll
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Remote\scriptel-rdp-virtual-channel-static-x64.dll

Make sure the following registry items exist:
*HKCU\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\ScriptelRDP
**Name should be a REG_SZ value and set to the absolute path of one of the items above (scriptel-rdp-virtual-channel-static-x{arch}.dll).

====Check Remote Desktop Server Configuration====
In the case of default installations of Windows Server 2012 and Windows Server 2012 R2 the default policy is to disallow non-trusted virtual channel drivers. You can white-list the ScripTouch Remote RDP virtual channel driver by doing editing the registry on the RDP server as outlined in this [https://msdn.microsoft.com/en-us/library/aa383586(v=vs.85).aspx Microsoft Documentation]:
*Create a key located at HKLM\System\CurrentControlSet\Control\Terminal Server\Addins\Scriptel VC
**Create a REG_SZ valued named 'Name' with a value of 'SCPTLVC'
**Create a REG_DWORD key named 'Type' with a value of 0x00000003 (3).

====Per User Registry Entries====
For Remote Desktop specifically the Virtual Channel driver must be registered per-user. If you're installing ScripTouch Remote as a user other than the user who needs to use the software you'll need one of the below registry files to register the virtual channel with their user account:
*[https://ny.scriptel.com/scriptouch-remote-rdp-fix-x64.reg Registry File for 64-bit Systems]
*[https://ny.scriptel.com/scriptouch-remote-rdp-fix-x32.reg Registry File for 32-bit Systems]

==Turn on Logging==
In the event that you've verified that you are licensed and that ScripTouch Remote is installed correctly and ScripTouch Remote still doesn't appear to be working correctly you can enable debug logging to see what's happening. These logs can be used to communicate with Scriptel support.

To enable debug logging do the following:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart the system.

Now when you use any ScripTouch software a debug log should be generated in your %TEMP% directory (typically 'C:\Users\<username>\AppData\Local\Temp'). The log file names will be in the following format:
*scriptel-debug-{type}-{pid}.log
*scriptel-trace-{type}-{pid}.pcap

The debug logs contain detailed information about what the application is doing relative to ScripTouch Remote and interactions with signature pads. These logs can be quite large but they usually compress well. Since they can get rather large it's recommended that debugging be turned off when no longer required.

Troubleshooting ScripTouch Remote on Windows

2018-10-19T19:06:16Z

Michael Powers: /* Verify Remote Desktop Installation */

[[Category:ScripTouch Remote]]
ScripTouch Remote is an installed piece of software that bridges the gap between Citrix and Remote Desktop clients and their associated servers to allow the use of ScripTouch signature digitizers on remote systems transparently. Usually using the software is as simple as installing the software and licensing it, but sometimes things go wrong.

This guide contains a list of things to check to ensure ScripTouch Remote is installed, configured, and working correctly.

==Testing ScripTouch Remote==
The simplest way to test to see if ScripTouch Remote is working is to use Citrix or RDP to connect to a remote server and start [[ScripTouch Sign and Save]] on the server. If everything is working correctly you'll see something like the following:

[[File:ScripTouch_Sign_and_Save_-_ScripTouch_Remote_Example.png]]

Notice the "Connected to ST1550" in the lower left, along with the green indicator. Also in the File -> Connect menu you can see the Citrix Receiver icon next to the device which indicates the device is connected through Citrix.

If the connection indicator in ScripTouch Sign and Save is grey and says "Disconnected" this means that ScripTouch Remote is not working correctly.

==Verify Licensing for ScripTouch Remote==
ScripTouch Remote is a licensed feature. If you need to get a license for ScripTouch Remote you can fill the form on [http://scriptel.com/developers/scriptouch-remote/ this page] and someone will get in contact with you. If you've already acquired licenses you can verify that you're licensed for ScripTouch Remote using the [[ScripTouch Toolbox]]. Once you download and install the software you can verify that you're licensed by navigating to Help -> License Viewer. This should be done on the local machine (the computer with the signature pad plugged into it).

If you're appropriately licensed you'll see the 'enable_citrix' and 'enable_rdp' entitlements in the 'Entitlements granted to this computer' section:

[[File:ScripTouch_Toolbox_License_Viewer.png]]

If you don't see any entitlements in the 'Entitlements granted to this computer' section:
*Verify that the licensed device is plugged in to the computer. If the correct device isn't plugged in you'll see items in the 'Entitlements not granted to this computer (and why)' box indicating which device(s) you're licensed for.
*Verify the license file is installed in one of the following locations (paths are shown in the 'License Files Found' section in the toolbox):
**%APPDATA%\Scriptel\Licenses
**%ProgramFiles%\Scriptel Corporation\Licenses
**%ProgramFiles(x86)%\Scriptel Corporation\Licenses

If you need to download the license file for your organization, you can retrieve it through our [https://scriptel.com/portal Licensing Portal] or you can use the ScripTouch Toolbox to retrieve the license file by doing the following:
*Go to Settings -> Online Settings
*Fill in the E-mail Address and Password sections (if you've forgotten your password you can reset it [https://scriptel.com/portal here]).
*Hit the "Check Credentials" button and wait for confirmation that your credentials are valid.
*Verify the Primary Organization matches the organization you're looking to get a license file for and hit "Save".
*Click the Settings -> Enable Online button.
*Click Settings -> Check for Licenses, this will download the license file for your organization to your user profile.

If you believe you should be licensed but these steps don't resolve licensing issues please contact Scriptel support at +1 (844) 972-7478 or support@my.scriptel.com.

==Check that ScripTouch Remote is Installed==
ScripTouch Remote currently comes in two forms: bundled in the [[ScripTouch Sign and Save]] application as well as in a standalone package available [https://services.scriptel.com/releases/scriptouch-remote/scriptouch-remote-windows here]. Both packages install similar components and either should enable ScripTouch Remote to function.

===Verify Citrix Installation===
In order for the Citrix components to install correctly ScripTouch Remote must be installed after the Citrix Receiver. If the Citrix Receiver is not detected during installation this component is skipped. To verify the installer installed the required components for Citrix please check that the following on the local computer (the computer with the pad plugged into it):

Make sure the following files exist:
*C:\Program Files (x86)\Citrix\ICA Client\scriptel-citrix-virtual-channel-x32.dll

Make sure the following registry items exist (drop the 'WOW6432Node' if you're on a 32-bit Windows installation):
*HKLM\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\ICA 3.0
**VirtualDriverEx should be a REG_SZ value and contain 'Scriptel' (it's ok if it contains other items as well, any other items should be separated by a comma).
*HKLM\SOFTWARE\WOW6432Node\Citrix\ICA Client\Engine\Configuration\Advanced\Modules\Scriptel
**DriverName should be a REG_SZ value and contain 'scriptel-citrix-virtual-channel-x32.dll'.
**DriverNameWin32 should be a REG_SZ value and contain 'scriptel-citrix-virtual-channel-x32.dll'.

===Verify Remote Desktop Installation===
The Remote Desktop component is always installed. Installation is performed as outlined in the [https://msdn.microsoft.com/en-us/library/aa383583(v=vs.85).aspx Microsoft Documentation]. To verify the installer installed the required components for RDP please check the following:

Make sure the following files exist:
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Sign and Save\scriptel-rdp-virtual-channel-static-x32.dll
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Sign and Save\scriptel-rdp-virtual-channel-static-x64.dll
OR
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Remote\scriptel-rdp-virtual-channel-static-x32.dll
*C:\Program Files (x86)\Scriptel Corporation\ScripTouch Remote\scriptel-rdp-virtual-channel-static-x64.dll

Make sure the following registry items exist:
*HKCU\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\ScriptelRDP
**Name should be a REG_SZ value and set to the absolute path of one of the items above (scriptel-rdp-virtual-channel-static-x{arch}.dll).

====Check Remote Desktop Server Configuration====
In the case of default installations of Windows Server 2012 and Windows Server 2012 R2 the default policy is to disallow non-trusted virtual channel drivers. You can white-list the ScripTouch Remote RDP virtual channel driver by doing editing the registry on the RDP server as outlined in this [https://msdn.microsoft.com/en-us/library/aa383586(v=vs.85).aspx Microsoft Documentation]:
*Create a key located at HKLM\System\CurrentControlSet\Control\Terminal Server\Addins\Scriptel VC
**Create a REG_SZ valued named 'Name' with a value of 'SCPTLVC'
**Create a REG_DWORD key named 'Type' with a value of 0x00000003 (3).

====Per User Registry Entries====
*[https://ny.scriptel.com/scriptouch-remote-rdp-fix-x64.reg Registry File for 64-bit Systems]
*[https://ny.scriptel.com/scriptouch-remote-rdp-fix-x32.reg Registry File for 32-bit Systems]

==Turn on Logging==
In the event that you've verified that you are licensed and that ScripTouch Remote is installed correctly and ScripTouch Remote still doesn't appear to be working correctly you can enable debug logging to see what's happening. These logs can be used to communicate with Scriptel support.

To enable debug logging do the following:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart the system.

Now when you use any ScripTouch software a debug log should be generated in your %TEMP% directory (typically 'C:\Users\<username>\AppData\Local\Temp'). The log file names will be in the following format:
*scriptel-debug-{type}-{pid}.log
*scriptel-trace-{type}-{pid}.pcap

The debug logs contain detailed information about what the application is doing relative to ScripTouch Remote and interactions with signature pads. These logs can be quite large but they usually compress well. Since they can get rather large it's recommended that debugging be turned off when no longer required.

Using Citrix XenApp USB Forwarding

2018-04-25T19:08:27Z

Michael Powers:

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 5.6+
*Citrix Receiver 4.2+
*VDA Running Windows Server 2012 R2 or Higher

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
[https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html Citrix Group Policy Extensions Download]
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

Troubleshooting ScripTouch for Epic

2018-01-23T17:38:32Z

Michael Powers: /* Installation */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server. [https://www.microsoft.com/en-us/download/details.aspx?id=21 Microsoft .NET 3.5] is required and must be installed separately. For Hyperspace versions prior to 2017 you'll need to know the correct ProgId prior to engaging Epic. Hyperspace 2017 and up no longer require the ProgId to be manually entered.

[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace Download Epic Hyperspace plugin]

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| 2012
| ScriptelDevice.0
|-
| 2014
| ScriptelDevice.1
|-
| 2015
| ScriptelDevice.2
|-
| 2016
| ScriptelDevice.3
|-
| 2017
| ScriptelDevice.3(*)
|-
| Post-2017
| ScriptelDevice.5(*)
|}

(*)Typically automatically configured in this version of Epic

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Pad is Disabled After Signing==
A new feature added in ScripTouch for Epic 3.2.47 and higher automatically disables the signature pad, to disable the behavior see [[Prevent Epic from Locking Signature Pad|here]].

Troubleshooting ScripTouch for Epic

2018-01-23T17:35:37Z

Michael Powers: /* Installation */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server. [https://www.microsoft.com/en-us/download/details.aspx?id=21 Microsoft .NET 3.5] is required and must be installed separately. For Hyperspace versions prior to 2017 you'll need to know the correct ProgId prior to engaging Epic. Hyperspace 2017 and up no longer require the ProgId to be manually entered.

[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace Download Epic Hyperspace plugin]

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| 2012
| ScriptelDevice.0
|-
| 2014
| ScriptelDevice.1
|-
| 2015
| ScriptelDevice.2
|-
| 2016
| ScriptelDevice.3
|-
| 2017
| ScriptelDevice.3 (not required)
|-
| Post-2017
| ScriptelDevice.5 (not required)
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Pad is Disabled After Signing==
A new feature added in ScripTouch for Epic 3.2.47 and higher automatically disables the signature pad, to disable the behavior see [[Prevent Epic from Locking Signature Pad|here]].

Troubleshooting ScripTouch for Epic

2017-12-13T19:09:28Z

Michael Powers: /* Beta Features */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server. [https://www.microsoft.com/en-us/download/details.aspx?id=21 Microsoft .NET 3.5] is required and must be installed separately. For Hyperspace versions prior to 2017 you'll need to know the correct ProgId prior to engaging Epic. Hyperspace 2017 and up no longer require the ProgId to be manually entered.

[https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace Download Epic Hyperspace plugin]

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| 2012
| ScriptelDevice.0
|-
| 2014
| ScriptelDevice.1
|-
| 2015
| ScriptelDevice.2
|-
| 2016
| ScriptelDevice.3
|-
| 2017
| ScriptelDevice.3 (not required)
|-
| 2018
| ScriptelDevice.4 (not required)
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Pad is Disabled After Signing==
A new feature added in ScripTouch for Epic 3.2.47 and higher automatically disables the signature pad, to disable the behavior see [[Prevent Epic from Locking Signature Pad|here]].

Prevent Epic from Locking Signature Pad

2017-12-13T19:07:58Z

Michael Powers: Created page with "A new feature added in the ScripTouch for Epic plugin version 3.2.47 and higher automatically locks the signature pad after signing is complete. This is done to prevent user c..."

A new feature added in the ScripTouch for Epic plugin version 3.2.47 and higher automatically locks the signature pad after signing is complete. This is done to prevent user confusion about whether the pad is supposed to be signed yet or not. Since this change may break customer workflows there is a way to disable this new feature.

Navigate to or create the following registry key:
*Windows 32-bit: HKLM\Software\Scriptel Corporation\Epic
*Windows 64-bit: HKLM\Software\WOW3264Node\Scriptel Corporation\Epic

Once you're at the key, create a new DWORD value called PreventScreenLock and set the value to:
*0x01 - Screen lock is disabled, mirroring the old default behavior.
*0x00 - Screen lock is enabled, the new default that locks the pads.

[[File:Epicregedit.png]]

File:Epicregedit.png

2017-12-13T19:07:27Z

Michael Powers:

ProScript Debugging

2017-08-10T13:50:40Z

Michael Powers: Created page with "The ProScript library is capable of producing detailed output logs. The configuration for logging is controlled by the use of environment variables. This is done so that any a..."

The ProScript library is capable of producing detailed output logs. The configuration for logging is controlled by the use of environment variables. This is done so that any application implementing the ProScript library does not need to be aware of the debugging mechanism in order to take advantage of it.

The ProScript library looks at the following environment variables at startup:
{| class="wikitable"
! Environment Variable
! Type
! Default Value
! Description
|-
| SCRIPTEL_DEBUG
| boolean
| false
| Determines whether or not any debug output will be produced.
|-
| SCRIPTEL_DEBUG_LOCATION
| string
| %TEMP%
| Determines the location where debug files will be placed. Environment variables surrounded in %'s will be resolved to their appropriate locations.
|-
| SCRIPTEL_DEBUG_LEVEL
| string
| ALL
| Determines the level of verbosity of the logs produced.
|-
| SCRIPTEL_DEBUG_FILE
| string
| scriptel-debug-${label}-${pid}.log
| Determines the file name pattern of the logging files produced.
|-
| SCRIPTEL_DEBUG_HANDLERS
| string
| file
| Determines the debug handler to use, right now 'file' is the only one that exists.
|-
| SCRIPTEL_TRACE
| boolean
| false
| Determines whether or not ScripTouch Remote trace files will be generated. If unset and SCRIPTEL_DEBUG is true, this will default to true.
|-
| SCRIPTEL_TRACE_FILE
| string
| scriptel-trace-${label}-${pid}.pcap
| Determines the file name pattern for ScripTouch Remote trace files.
|}

Valid boolean 'true' values (everything else resolves to false): true, 1, yes, on.

Valid file substitutions:
*${pid} - Process ID of the process running the library.
*${label} - Label of the debugger defined in scriptel_debug_init()
*${random} - Random 10 digit string consisting of 0-9's.

ScripTouch USB IDs

2017-08-09T21:09:15Z

Michael Powers:

Various different USB utilities will require the appropriate vendor and product ID's for ScripTouch Devices. Below is a table of all ScripTouch devices with their vendor and product ids.

{| class="wikitable"
! Model
! Firmware
! Vendor ID
! Product ID
|-
| [[ST1400]]
| All
| 18fb
| 0204
|-
| [[ST1401-STN]]
| All
| 18fb
| 01c5
|-
| [[ST1475]]
| All
| 18fb
| 0206
|-
| [[ST1476-STN]]
| >= 4.0.0
| 18fb
| 0244
|-
| [[ST1476-STN]]
| < 4.0.0
| 18fb
| 01c9
|-
| [[ST1500]]
| Any
| 18fb
| 0200
|-
| [[ST1500B]]
| Any
| 18fb
| 0208
|-
| [[ST1501-STN]]
| >= 4.0.0
| 18fb
| 0240
|-
| [[ST1501-STN]]
| < 4.0.0
| 18fb
| 01c0
|-
| [[ST1501B-STN]]
| >= 4.0.0
| 18fb
| 0241
|-
| [[ST1525]]
| Any
| 18fb
| 0202
|-
| [[ST1526-STN]]
| >= 4.0.0
| 18fb
| 0242
|-
| [[ST1526-STN]]
| < 4.0.0
| 18fb
| 01c1
|-
| [[ST1550]]
| Any
| 18fb
| 0201
|-
| [[ST1551-STN]]
| >= 4.0.0
| 18fb
| 0243
|-
| [[ST1551-STN]]
| < 4.0.0
| 18fb
| 01c6
|-
| [[ST1570]]
| Any
| 18fb
| 0207
|-
| [[ST1571-STN]]
| >= 4.0.0
| 18fb
| 0245
|-
| [[ST1571-STN]]
| < 4.0.0
| 18fb
| 01cb
|}

Troubleshooting EasyScript Devices

2017-08-03T12:53:24Z

Michael Powers: /* Increasing the size of the Windows Keyboard Buffer */

The ScripTouch EasyScript protocol generally works without requiring driver installation, software installation, or computer configuration. There are some cases however when computer configuration issues or installed software can interfere with the operation of EasyScript devices. This article contains troubleshooting steps designed to help identify and correct issues.

==Testing EasyScript Devices==
Scriptel provides a [https://ny.scriptel.com/easyscript/ diagnostic utility] designed to identify issues with EasyScript signature capture that works with modern browsers. This can be helpful when trying to determine if the issue is with the software or with the EasyScript device. To test your device:
*Go to https://ny.scriptel.com/easyscript.
*Place your cursor in the "Sign Here" box.
*Press "Start" on the signature pad, sign something, and hit "OK" on the signature pad.

After pressing "OK" you should see a series of characters stream into the text box next to "Sign Here" and the decoded signature should appear in the signature box below.

If you see characters in the text box, but the signature box below is empty, incomplete, or garbled:
*Check for [[#Conflicting Software|installed software interfering]] with the operation of the signature pad.
*Try [[#Slowing Down the Signature Pad|slowing down the output rate]] of the signature pad.
*Try [[#Increasing the size of the Windows Keyboard Buffer|increasing the size of your keyboard buffer]].
*Contact [[Scriptel Support]].

If you don't see anything appear:
*Check that your cursor is in the "Sign Here" box.
*Check that the device is plugged directly into the computer and not into an external hub.
*Check that there isn't any damage to the USB cord.
*Contact [[Scriptel Support]].

If the signature appears to decode correctly:
*Contact the software vendor which is not working with the EasyScript device.
*Contact [[Scriptel Support]].

==Conflicting Software==
There are some pieces of software that interfere with EasyScript devices.

===Webroot Security Suite===
This software contains an anti-keylogger component that heavily interferes with the Windows keyboard stack. When this protection component is on EasyScript device output will be garbled and the devices will not be usable. Simply disabling the anti-keylogger protection is enough to fix the issue, the rest of the product can remain installed and enabled. The exact procedure for doing this depends on the version of the suite that is installed.

===Ubuntu Linux Unity Window Manager===
The Unity window manager installed with Ubuntu Linux (tested with Ubuntu 14.04) contains a small event buffer. On faster computers everything works correctly, on slower computers Unity can drop keyboard events which will cause the EasyScript signature to become invalid. If you're experiencing this problem switching to another window manager should fix the issue (tested: Gnome, KDE, Cinnamon). Newer versions of Unity may also fix this issue.

You can also try slowing down signature pad output.

==Slowing Down the Signature Pad==
With newer versions of firmware it's possible with the [[ScripTouch Toolbox]] to slow down the keyboard rate to keep it from overwhelming computers and applications. To do this:
*Download and install the [[ScripTouch Toolbox]].
*Open the ScripTouch Toolbox, go to the "Output" tab.
*Adjust the "Packets per Second" slider to the desired speed, for most purposes 100 should be sufficient.
*Optionally (if your application supports it) checking the "Stream output" and "Compress output" boxes may improve reliability and speed.

==Increasing the size of the Windows Keyboard Buffer==
By default the Windows keyboard buffer is sized at one hundred events. Depending on the computer and the installed applications this may be insufficient. If the keyboard buffer overflows the EasyScript signature stream will corrupt.

This fix requires changing the Windows Registry, please don't attempt this unless you're comfortable making system changes.

To adjust the keyboard buffer size:
*Open the Windows Registry Editor.
*Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass\Parameters.
*Change KeyboardDataQueueSize from 64 to 10000.
*Reboot the computer.

Using Citrix XenApp USB Forwarding

2017-06-23T15:22:23Z

Michael Powers: /* Requirements */

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 7.0+
*Citrix Receiver 3.5+
*VDA Running Windows Server 2012 R2 or Higher

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
[https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html Citrix Group Policy Extensions Download]
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

ST1571-STN

2017-06-14T18:32:37Z

Michael Powers: Redirected page to ScripTouch Slimline LCD Signature Pad

#REDIRECT [[ScripTouch Slimline LCD Signature Pad]]

ST1551-STN

2017-06-14T18:32:23Z

Michael Powers: Redirected page to ScripTouch Compact LCD Signature Pad

#redirect [[ScripTouch Compact LCD Signature Pad]]

ST1526-STN

2017-06-14T18:32:12Z

Michael Powers: Redirected page to ScripTouch Magstripe LCD Signature Pad

#redirect [[ScripTouch Magstripe LCD Signature Pad]]

ST1501B-STN

2017-06-14T18:31:54Z

Michael Powers: Redirected page to ScripTouch Desktop LCD Signature Pad

#redirect [[ScripTouch Desktop LCD Signature Pad]]

ST1501-STN

2017-06-14T18:31:51Z

Michael Powers: Redirected page to ScripTouch Desktop LCD Signature Pad

#redirect [[ScripTouch Desktop LCD Signature Pad]]

ST1476-STN

2017-06-14T18:31:28Z

Michael Powers: Redirected page to ScripTouch Slimline 1×5 Signature Pad

#redirect [[ScripTouch Slimline 1×5 Signature Pad]]

ScripTouch USB IDs

2017-06-14T18:31:13Z

Michael Powers: Created page with "Various different USB utilities will require the appropriate vendor and product ID's for ScripTouch Devices. Below is a table of all ScripTouch devices with their vendor and p..."

Various different USB utilities will require the appropriate vendor and product ID's for ScripTouch Devices. Below is a table of all ScripTouch devices with their vendor and product ids.

{| class="wikitable"
! Model
! Firmware
! Vendor ID
! Product ID
|-
| [[ST1400]]
| All
| 18fb
| 0204
|-
| [[ST1401-STN]]
| All
| 18fb
| 01c5
|-
| [[ST1475]]
| All
| 18fb
| 0206
|-
| [[ST1476-STN]]
| >= 4.0.0
| 18fb
| 0244
|-
| [[ST1476-STN]]
| < 4.0.0
| 18fb
| 01c9
|-
| [[ST1500]]
| Any
| 18fb
| 0200
|-
| [[ST1501-STN]]
| >= 4.0.0
| 18fb
| 0240
|-
| [[ST1501-STN]]
| < 4.0.0
| 18fb
| 01c0
|-
| [[ST1501B-STN]]
| >= 4.0.0
| 18fb
| 0241
|-
| [[ST1525]]
| Any
| 18fb
| 0202
|-
| [[ST1526-STN]]
| >= 4.0.0
| 18fb
| 0242
|-
| [[ST1526-STN]]
| < 4.0.0
| 18fb
| 01c1
|-
| [[ST1550]]
| Any
| 18fb
| 0201
|-
| [[ST1551-STN]]
| >= 4.0.0
| 18fb
| 0243
|-
| [[ST1551-STN]]
| < 4.0.0
| 18fb
| 01c6
|-
| [[ST1570]]
| Any
| 18fb
| 0207
|-
| [[ST1571-STN]]
| >= 4.0.0
| 18fb
| 0245
|-
| [[ST1571-STN]]
| < 4.0.0
| 18fb
| 01cb
|}

ST1401-STN

2017-06-14T18:30:49Z

Michael Powers: Redirected page to ScripTouch Desktop 1×5 Signature Pad

#redirect [[ScripTouch Desktop 1×5 Signature Pad]]

Using Citrix XenApp USB Forwarding

2017-05-31T19:37:28Z

Michael Powers: /* Configuring Automatic Device Forwarding */

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 7.0+
*Citrix Receiver 3.5+

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
[https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html Citrix Group Policy Extensions Download]
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

Using Citrix XenApp USB Forwarding

2017-05-30T19:49:03Z

Michael Powers: /* Requirements */

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 7.0+
*Citrix Receiver 3.5+

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

Using Citrix XenApp USB Forwarding

2017-05-30T19:45:38Z

Michael Powers: /* Using Group Policy */

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 7.0+
*Citrix Receiver 3.5+
*Citrix Active Directory Schema Extensions Installed (required for automatic redirection)

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

Using Citrix XenApp USB Forwarding

2017-05-30T19:41:41Z

Michael Powers:

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 7.0+
*Citrix Receiver 3.5+
*Citrix Active Directory Schema Extensions Installed (required for automatic redirection)

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

Troubleshooting ScripTouch for Epic

2017-03-22T12:17:28Z

Michael Powers:

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016/2017]
| ScriptelDevice.3
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2018 2018]
| ScriptelDevice.4
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has been add as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Epic Hyperspace Plugin

2017-03-22T12:16:29Z

Michael Powers:

{{#get_web_data:
url=https://wiki.scriptel.com/releaseinfo.php?project=scriptouch-epic&files=scriptel-hyperspace-2012,scriptel-hyperspace-2014,scriptel-hyperspace-2015,scriptel-hyperspace-2016,scriptel-hyperspace-2016&labels=Hyperspace 2012,Hyperspace 2014,Hyperspace 2015,Hyperspace 2016,Hyperspace 2017&showVersion&showDate&showFiles&showSizes
|format=CSV
|delimiter=,
|data=versioninfo=1
}}
{{Infobox software
| name = Epic Hyperspace Plugin
| logo =
| logo size = 192px
| screenshot = 
| caption =
| screenshot alt =
| collapsible =
| author =
| developer = [[Scriptel Corporation]]
| released = 
| discontinued =
| latest release version = {{#for_external_table: {{{versioninfo}}}}}
| latest release date = 
| latest preview version =
| latest preview date = 
| status =
| programming language =
| operating system = Windows 7 - 10 Server 2008 - 2012 R2
| platform =
| size =
| language =
| language count = 
| language footnote =
| genre =
| license =
| alexa =
| website = {{URL|scriptel.com/support/plugins/epic-hyperspace/}}
| standard =
| AsOf =
}}
[[Category:Epic Hyperspace]]
Scriptel signature pads are fully compatible with Epic Hyperspace through the use of our ScripTouch for Epic plugin. This plugin uses the standard Epic Hyperspace Signature API to provide support for electronic signatures in Hyperspace. The plugin fully supports [[ScripTouch Remote]] which allows the use of ScripTouch signature pads over Citrix and RDP sessions.

We recommend that users of XenApp 6.5 or Remote Desktop install [[ScripTouch Remote]] in order to fully enable USB forwarding.

==Features==
*Uses standard Epic Hyperspace Signature API to provide Electronic Signature support for Epic Hyperspace
*Compatible with Epic Hyperspace 2012, 2014, 2015, 2016, and 2017
*Works with locally installed clients or remote clients through Citrix, Remote Desktop, or other VDI systems.
*USB forwarding option available through [[ScripTouch Remote]]

==Troubleshooting==
For troubleshooting information please see [[Troubleshooting ScripTouch for Epic]].

==Download==
[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 Download Plugin for version 2016 / 2017]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 Download Plugin for version 2015]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 Download Plugin for version 2014]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 Download Plugin for version 2012]

Epic Hyperspace Plugin

2017-03-22T12:14:28Z

Michael Powers:

{{#get_web_data:
url=https://wiki.scriptel.com/releaseinfo.php?project=scriptouch-epic&files=scriptel-hyperspace-2012,scriptel-hyperspace-2014,scriptel-hyperspace-2015,scriptel-hyperspace-2016&labels=Epic 2012,Epic 2014,Epic 2015,Epic 2016&showVersion&showDate&showFiles&showSizes
|format=CSV
|delimiter=,
|data=versioninfo=1
}}
{{Infobox software
| name = Epic Hyperspace Plugin
| logo =
| logo size = 192px
| screenshot = 
| caption =
| screenshot alt =
| collapsible =
| author =
| developer = [[Scriptel Corporation]]
| released = 
| discontinued =
| latest release version = {{#for_external_table: {{{versioninfo}}}}}
| latest release date = 
| latest preview version =
| latest preview date = 
| status =
| programming language =
| operating system = Windows 7 - 10 Server 2008 - 2012 R2
| platform =
| size =
| language =
| language count = 
| language footnote =
| genre =
| license =
| alexa =
| website = {{URL|scriptel.com/support/plugins/epic-hyperspace/}}
| standard =
| AsOf =
}}
[[Category:Epic Hyperspace]]
Scriptel signature pads are fully compatible with Epic Hyperspace through the use of our ScripTouch for Epic plugin. This plugin uses the standard Epic Hyperspace Signature API to provide support for electronic signatures in Hyperspace. The plugin fully supports [[ScripTouch Remote]] which allows the use of ScripTouch signature pads over Citrix and RDP sessions.

We recommend that users of XenApp 6.5 or Remote Desktop install [[ScripTouch Remote]] in order to fully enable USB forwarding.

==Features==
*Uses standard Epic Hyperspace Signature API to provide Electronic Signature support for Epic Hyperspace
*Compatible with Epic Hyperspace 2012, 2014, 2015, 2016, and 2017
*Works with locally installed clients or remote clients through Citrix, Remote Desktop, or other VDI systems.
*USB forwarding option available through [[ScripTouch Remote]]

==Troubleshooting==
For troubleshooting information please see [[Troubleshooting ScripTouch for Epic]].

==Download==
[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 Download Plugin for version 2016 / 2017]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 Download Plugin for version 2015]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 Download Plugin for version 2014]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 Download Plugin for version 2012]

Epic Hyperspace Plugin

2017-03-22T12:14:18Z

Michael Powers:

{{#get_web_data:
url=https://wiki.scriptel.com/releaseinfo.php?project=scriptouch-epic&files=scriptel-hyperspace-2012,scriptel-hyperspace-2014,scriptel-hyperspace-2015,scriptel-hyperspace-2016&labels=Epic 2012,Epic 2014,Epic 2015,Epic 2016&showVersion&showDate&showFiles&showSizes
|format=CSV
|delimiter=,
|data=versioninfo=1
}}
{{Infobox software
| name = Epic Hyperspace Plugin
| logo =
| logo size = 192px
| screenshot = 
| caption =
| screenshot alt =
| collapsible =
| author =
| developer = [[Scriptel Corporation]]
| released = 
| discontinued =
| latest release version = {{#for_external_table: {{{versioninfo}}}}}
| latest release date = 
| latest preview version =
| latest preview date = 
| status =
| programming language =
| operating system = Windows 7 - 10 Server 2008 - 2012 R2
| platform =
| size =
| language =
| language count = 
| language footnote =
| genre =
| license =
| alexa =
| website = {{URL|scriptel.com/support/plugins/epic-hyperspace/}}
| standard =
| AsOf =
}}
[[Category:Epic Hyperspace]]
Scriptel signature pads are fully compatible with Epic Hyperspace through the use of our ScripTouch for Epic plugin. This plugin uses the standard Epic Hyperspace Signature API to provide support for electronic signatures in Hyperspace. The plugin fully supports [[ScripTouch Remote]] which allows the use of ScripTouch signature pads over Citrix and RDP sessions.

We recommend that users of XenApp 6.5 or Remote Desktop install [[ScripTouch Remote]] in order to fully enable USB forwarding.

==Features==
*Uses standard Epic Hyperspace Signature API to provide Electronic Signature support for Epic Hyperspace
*Compatible with Epic Hyperspace 2012, 2014, 2015, 2016, and 2017
*Works with locally installed clients or remote clients through Citrix, Remote Desktop, or other VDI systems.
*USB forwarding option available through [[ScripTouch Remote]]

==Troubleshooting==
For troubleshooting information please see [[Troubleshooting ScripTouch for Epic]].

==Download==
[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 Download Plugin for version 2016]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 Download Plugin for version 2015]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 Download Plugin for version 2014]

[http://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 Download Plugin for version 2012]

Epic Hyperspace

2017-03-22T12:13:58Z

Michael Powers:

[[Category:ISV Partners]]
[[Category:Epic Hyperspace]]
Scriptel signature pads are fully compatible with Hyperspace, through the use of the standard Epic API. Scriptel incorporates the API through the Hyperspace plugin, that is available in ScripTouch Sign and Save. The Scriptel solution is Citrix Ready and works with full client or VDI installations with such products as Citrix XenApp 6.5 and 7.6, or other products such as Microsoft Remote Desktop.

We recommend that users of XenApp 6.5 or Remote Desktop install [[ScripTouch Remote]], in order to fully enable USB forwarding.

==Features==
*Uses standard Epic API
*Compatible with Epic Hyperspace 2012, 2014, 2015, 2016, and 2017
*Works with client or VDI installations
*USB forwarding option available through ScripTouch Remote
*'''Windows Support'''

==Supported Models==
[[ScripTouch Desktop LCD Signature Pad]] with [[ProScript]]

[[ScripTouch Magstripe LCD Signature Pad]] with [[ProScript]]

[[ScripTouch Compact LCD Signature Pad]] with [[ProScript]]

[[ScripTouch Slimline LCD Signature Pad]] with [[ProScript]]

Troubleshooting ScripTouch for Epic

2017-03-21T19:55:08Z

Michael Powers: /* VMware Horizon View */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2018 2018]
| ScriptelDevice.4
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has been add as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

ScripTouch Compact LCD Signature Pad

2017-03-21T19:38:47Z

Michael Powers:

{{Infobox computer hardware
| name = ScripTouch Compact LCD Signature Pad
| logo =
| logo-size =
| logo_caption =
| image = Scriptel-ScripTouch-Compact-LCD_1.jpg
| image-size =
| caption =
| invent-date =
| invent-name =
| conn1 = USB 2.0 (standard A-type connector)
| via1_1 =
| class-name = Interfaces
| class1 = [[ProScript]] (ST1550)
| class2 = [[EasyScript]] (ST1551)
| manuf1 =
| designfirm =
| manufacturer = [[Scriptel Corporation]]
| introduced =
| discontinued =
| cost = $199
| type = Electronic signature pad, compact with integrated display and removable cables
| processor =
| frequency =
| memory =
| slots =
| rom =
| coprocessor =
| connection =
| ports =
| power = USB bus-powered, no separate external power supply needed
| color = Black
| dpi =
| speed =
| language =
| weight =
| dimensions = 5.2" x 3.2" x 0.68" (132.1 x 81.3 x 17.3mm)
}}
[[Category:ScripTouch Signature Pads]]

The ScripTouch Compact LCD has a rugged design and a scratch-resistant backlit LCD meant for capturing signatures on the go. Like all ScripTouch pads, it comes with an active battery-less tethered pen.

[[File:Scriptel-ScripTouch-Compact-LCD_1.jpg|300px]]
[[File:Scriptel-ScripTouch-Compact-LCD_2.jpg|300px]]
[[File:Scriptel-ScripTouch-Compact-LCD 3.jpg|300px]]
[[File:Scriptel-ScripTouch-Compact-LCD 4.jpg|300px]]

==Features==
*Compact design
*Backlit LCD
*Scratch-resistant glass signing surface
*[[StaticCap_Touch_System#Active_Digital_Pen|Active battery-less tethered pen]]
*Durable plastic case construction with replaceable cables
*Bottom-side rubber feet
*3 year warranty with RapidCare overnight exchange
*[[ProScript]] (ST1550) or [[EasyScript]] (ST1551) device interface

==Technical Specifications==

{| class="wikitable"
|Weight
|1 lbs
|-
|Dimensions
|5.2 x 3.2 x .68 in
|-
|Manufacturer
|[[Scriptel Corporation]]
|-
|Interface
|[[ProScript]], [[EasyScript]]
|-
|Product Type
|Electronic signature pad, compact with integrated display and removable cables
|-
|Active Signing Area
|4.25” x 1.2” (107.9 x 30.5 mm)
|-
|Signature Display
|Backlit Monochrome LCD (240×64 pixels)
|-
|Pen Type
|[[StaticCap_Touch_System#Active_Digital_Pen|Active battery-less tethered pen]]
|-
|Sensing Technology
|[[StaticCap_Touch_System|Scriptel StaticCap® capacitive sensing]]
|-
|Min. Signature Resolution
|500ppi
|-
|Min. Signature Sample Rate
|120pps
|-
|Product Dimensions
|5.2” x 3.2” x 0.68” (132.1 x 81.3 x 17.3mm)
|-
|Power Supply
|USB bus-powered, no separate external power supply needed.
|-
|Thin Client / RDP
|[[Citrix Ready]] and [[ScripTouch Remote]] (USB virtualization tool) available.
|-
|Operating Systems
|Support available for Windows, Mac OS and Linux.
|-
|Warranty
|3 Year
|-
|Product Webpage
|[http://scriptel.com/products/compact-lcd-signature-pad/ ScripTouch Compact LCD product page] on scriptel.com
|-
|Model Numbers
|ST1550 ProScript, ST1551 EasyScript
|-
|Technical Specs
|[http://scriptel.com/datasheets/Scriptel-Compact-LCD-USB-ST1550-ST1551-DataSheet.pdf ScripTouch Compact LCD Data Sheet] on scriptel.com (PDF Download)
|-
|Levels of Pressure
|2
|}

==Software and Support==

===Available Software and Integration Support for ProScript===
*Microsoft [[ScripTouch_Word_Plugin|Word]] and [[ScripTouch Excel Plugin|Excel]] plugins
*[[ScripTouch Adobe Plugin|Adobe Acrobat and Reader]] plugins
*[[ScripTouch TWAIN Plugin|TWAIN]] and OPOS drivers
*[[ScripTouch Sign and Save]] signature image and data capture application
*Supports [[OmniScript]] universal signature integration platform
*Extensive APIs and software libraries in .NET (C++, VB, C# and F#)
*Windows COM also supported

===Available Software and Integration Support for EasyScript===
*Microsoft [[ScripTouch_Word_Plugin|Word]] and [[ScripTouch Excel Plugin|Excel]] plugins
*[[ScripTouch Adobe Plugin|Adobe Acrobat and Reader]] plugins
*[[ScripTouch TWAIN Plugin|TWAIN]] driver
*[[ScripTouch Sign and Save]] signature image and data capture application
*Software libraries and examples in Java, JavaScript, PHP, ASP.NET, C, C++ and Objective C
*APIs and software libraries also available for .NET (C++, VB, C# and F#)

==Interfaces==
*Model ST1550 has a [[ProScript]] interface
*Model ST1551 has an [[EasyScript]] interface

==Extenal References==
*[http://scriptel.com/products/compact-lcd-signature-pad/ ScripTouch Compact LCD product page] on scriptel.com
*[https://escriptel.com/product/scriptouch-compact-lcd-signature-pad/ ScripTouch Compact LCD retail page] on escriptel.com
*[http://scriptel.com/datasheets/Scriptel-Compact-LCD-USB-ST1550-ST1551-DataSheet.pdf ScripTouch Compact LCD Data Sheet] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Compact-LCD-USB-ST1550-ST1551-Quick-Start-Guide.pdf ScripTouch Compact LCD Quick Start Guide] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Compact-LCD-USB-ST1550-ST1551-Dimensional-Drawing.pdf ScripTouch Compact LCD Dimensional Drawing] on scriptel.com (PDF Download)

Troubleshooting ScripTouch Remote

2017-03-17T12:35:51Z

Michael Powers: Created page with "Troubleshooting instructions for: *Windows *Mac"

Troubleshooting instructions for:
*[[Troubleshooting ScripTouch Remote on Windows|Windows]]
*[[Troubleshooting ScripTouch Remote on Mac|Mac]]

Getting the MAC Address of a Computer

2017-03-16T20:22:47Z

Michael Powers: Created page with "Some licensing activities may require you to get the MAC address of your computer. This can by done by doing the following: *Press and hold the "Windows" key and press the "R..."

Some licensing activities may require you to get the MAC address of your computer.

This can by done by doing the following:
*Press and hold the "Windows" key and press the "R" key.
*In the "Run" window that appears, type "cmd" and hit "OK".
*In the black window that appears type "ipconfig /all" and hit enter.
*You will see a list of one or more network adapters. The "Physical Address" items are your MAC address.
[[File:Macaddress.png]]

File:Macaddress.png

2017-03-16T20:22:21Z

Michael Powers:

Getting the UUID of a ScripTouch Device

2017-03-16T20:06:02Z

Michael Powers: Created page with "Some software and support activities will require you to retrieve the UUID of a ScripTouch Device. Getting the UUID is a simple procedure. *Download and install the ScripTou..."

Some software and support activities will require you to retrieve the UUID of a ScripTouch Device. Getting the UUID is a simple procedure.
*Download and install the [[ScripTouch Toolbox]].
*Plug in the ScripTouch device you'd like to get the UUID for.
*Start the ScripTouch Toolbox.
*On the "Information" tab the UUID is shown. Click "Copy UUID" to copy the UUID to the clipboard.
[[File:ScripTouch_Toolbox_Screenshot.png]]

EasyScript

2017-02-22T16:29:51Z

Michael Powers:

EasyScript was built from the ground up to enable a simple and convenient way to capture electronic signatures and magnetic card swipe data (on supported devices) from a wide variety of usages including web-based and traditional applications.

This interface excels at providing an extremely simple and portable integration that does not require any software or drivers to be installed to run your application.

====Simple Integration====
Traditionally communicating with attached peripherals from applications (particularly web applications) is problematic. Many web based solutions use Java applets or ActiveX controls that allow a web application to access an attached signature digitizer. This approach creates work for individuals maintaining this type of software because these plugins require constant security and compatibility updates. Failure to apply these updates can leave systems with these plugins installed insecure which potentially compromises the security of the network. On the other hand, applying these updates occasionally will break software requiring updates to the application to fix new incompatibilities.

The EasyScript interface mitigates this problem by communicating with the computer as if it were a keyboard. Nearly any application implemented on most platforms can communicate with keyboards without plugins. [[Scriptel]] provides API’s and documentation for capturing the keyboard data from a wide variety of different programming languages in order to simplify application development.

====Simple Portability====
A common issue with application development is the problem of how to deploy the application when it’s done and how to update it once it’s installed on the end user’s machine. Today’s application ecosystem includes many operating systems, architectures, platforms, devices, and web browsers. In order to support these different technologies developers take advantage of cross platform languages and interfaces to reduce the cost to support the diverse devices their application needs to run on.

To this end [[Scriptel Corporation| Scriptel's]] EasyScript again takes advantage of the fact nearly all devices support USB keyboards. Software written for EasyScript ScripTouch devices can be easily integrated into platform independent applications.

==Changes with version 2.0==
*Compression
*More resolution can be transmitted (now matching our ProScript interface at 500 dpi and 120 samples per second) using similar number of keystrokes
*Signature data streaming
*Data is now sent out as soon as signing starts, OK and Cancel buttons now explicitly detected
*Automatic adapt to keyboard layout
*Signature preamble provides minimum number of keystrokes for the API to adapt to whatever keyboard layout is the current setting in the OS
*Toolbox settings for compression and keystroke packet transmission rate
*Signature data buffer in pad automatically resets after 30 seconds of inactivity
*Signature data streaming (for “real-time signature rendering”)
*Higher resolution signature data (for “biometrics” or “forensics” capability)
*Automatic international keyboard support
*Explicitly detect OK and Cancel

==Models with EasyScript==

*[[ScripTouch Slimline 1×5 Signature Pad|ScripTouch Slimline 1×5 ST1476]]

*[[ScripTouch Compact LCD Signature Pad|ScripTouch Compact LCD ST1551]]

*[[ScripTouch Magstripe LCD Signature Pad|ScripTouch Magstripe LCD ST1526]]

*[[ScripTouch Desktop LCD Signature Pad|ScripTouch Desktop LCD ST1501]]

*[[ScripTouch Desktop 1×5 Signature Pad|ScripTouch Desktop 1×5 ST1401]]

*[[ScripTouch Slimline LCD Signature Pad|ScripTouch Slimline LCD ST1571]]

==Troubleshooting==

*[[Troubleshooting EasyScript Devices]]
*[[Using EasyScript Devices with Remote Desktop]]

Troubleshooting EasyScript Devices

2017-02-22T16:29:33Z

Michael Powers: Created page with "The ScripTouch EasyScript protocol generally works without requiring driver installation, software installation, or computer configuration. There are some cases however when c..."

EasyScript

2017-02-22T15:45:37Z

Michael Powers:

Using EasyScript Devices with Remote Desktop

2017-02-22T15:43:40Z

Michael Powers: Created page with "ScripTouch devices using the EasyScript protocol can be used with Microsoft Remote Desktop (also known as Terminal Services) without the need for any USB redirection software...."

ScripTouch devices using the EasyScript protocol can be used with Microsoft Remote Desktop (also known as Terminal Services) without the need for any USB redirection software. Depending on your environment there are some considerations that may need to be made in order for EasyScript to work reliably.

You can always test EasyScript devices by going to our [https://ny.scriptel.com/easyscript/ diagnostic utility].

==Slowing Down Keyboard Output==
Some environments will require you to slow down the keyboard output speed of your ScripTouch device. This can be done by using the [[ScripTouch Toolbox]]:
*Open the ScripTouch Toolbox, go to the "Output" tab.
*Move the "Packets per Second" slider between 100-250 packets per second (exact value may depend on your environment).
*Optionally (if your application supports it) checking the "Stream output" and "Compress output" boxes should improve reliability and speed.

After adjusting the slider test the signature pad again using the [https://ny.scriptel.com/easyscript/ diagnostic utility]. This setting will persist even if the device is powered off or unplugged. You only need to do this once per ScripTouch device.

==Configuring Remote Desktop to use Local Key Combinations==
Certain versions of the official Microsoft RDP client [https://superuser.com/questions/219461/shift-and-control-keys-out-of-sync-with-normal-keys-over-rdp don't correctly send keyboard control codes]. This can result in EasyScript not working at all, or not working reliably. To fix this:
*Open the Microsoft RDP Client
*Go to the "Local Resources" tab.
*Change "Apply Windows key combinations" setting to "On this computer".
*Connect to the remote computer as normal.

After connecting to the remote computer, test again with the [https://ny.scriptel.com/easyscript/ diagnostic utility].

Troubleshooting ScripTouch for Epic

2016-11-29T15:18:32Z

Michael Powers:

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2018 2018]
| ScriptelDevice.4
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has been add as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Change ScripTouch Remote License Path

2016-08-26T14:28:33Z

Michael Powers:

[[Category:ScripTouch Remote]]
By default ScripTouch Remote looks in the following location for licenses:
*%APPDATA%\Scriptel\Licenses
*%ProgramFiles%\Scriptel Corporation\Licenses
*%ProgramFiles(x86)%\Scriptel Corporation\Licenses

It's possible to change the default search path to allow network locations or different directories to be used as license repositories.

To change the path System Wide:
*Create a registry key at: HKLM\SOFTWARE\Scriptel Corporation\Licenses
**Create a REG_SZ (String) value named 'LicensePath' that contains a semicolon (;) delimited list of paths to search.

To change the path as a per-User Setting:
*Create a registry key at: HKCU\SOFTWARE\Scriptel Corporation\Licenses
**Create a REG_SZ (String) value named 'LicensePath' that contains a semicolon (;) delimited list of paths to search.

Network paths can be used but the computer or user trust relationship must exist prior to launching any ScripTouch Remote enabled software. If the path asks for a user name or password it will not work until after the credentials have been entered.

Troubleshooting ScripTouch for Epic

2016-08-18T12:20:27Z

Michael Powers: /* Creating Debug Logs */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

Using Citrix XenApp USB Forwarding

2016-08-11T19:55:59Z

Michael Powers: Created page with "{{#ev:youtube|DidB8d1_LxQ}}"

ScripTouch for Epic

2016-08-11T19:52:22Z

Michael Powers: Redirected page to Epic Hyperspace Plugin

#REDIRECT [[Epic Hyperspace Plugin]]
[[Category:Epic Hyperspace]]

Category:Epic Hyperspace

2016-08-11T19:52:00Z

Michael Powers: Created page with "This category contains articles related to the ScripTouch for Epic plugin."

This category contains articles related to the [[ScripTouch for Epic]] plugin.

Category:ScripTouch Toolbox

2016-08-11T19:51:17Z

Michael Powers: Created page with "This category contains articles related to the ScripTouch Toolbox."

This category contains articles related to the [[ScripTouch Toolbox]].

Category:ScripTouch Signature Pads

2016-08-11T19:50:44Z

Michael Powers: Created page with "This category contains a list of all of the ScripTouch series of signature digitizers."

This category contains a list of all of the ScripTouch series of signature digitizers.

Products

2016-08-11T19:49:24Z

Michael Powers:

[[Category:ScripTouch Signature Pads]]
Get away from the time-consuming and error-prone print/sign/scan step in your operation just to get a good-quality customer signature. Go paperless!

You may well have an application that already uses signature pads, but did you know that this same signature pad can be used to sign PDFs? And with a full digital signature, any changes to that PDF after the signature will be detected?

If you have a [[Scriptel]] signature pad, you can do this for free as often as you want. Download the free Adobe Reader (XI and DC versions) and our free ScripTouch Sign and Save software and get fully secure PDF signing.

But, that’s not all, Sign and Save also provides plugins for capturing signatures in other popular applications such as:

Microsoft Word
Microsoft Excel
OpenOffice Write and Calc
Adobe Acrobat and Reader
And it doesn’t stop there, Sign and Save can also be used as a standalone product to get signatures as high-quality image files, or can provide a signature to applications that accept scanned input via TWAIN, or can be called with its Command Line Interface (CLI) to work in a workflow automation platform. All of this is free if you have one of our pads.

==Hardware==

==== [[ScripTouch Compact LCD Signature Pad]] ====

==== [[ScripTouch Desktop 1×5 Signature Pad]] ====

==== [[ScripTouch Desktop LCD Signature Pad]] ====

==== [[ScripTouch Slimline 1×5 Signature Pad]] ====

==== [[ScripTouch Magstripe LCD Signature Pad]] ====

==Software==

====[[OmniScript| ScripTouch OmniScript]]====

====[[ScripTouch Remote]]====

====[[ScripTouch Toolbox]]====

====[[ScripTouch Sign and Save]]====

ScripTouch Magstripe LCD Signature Pad

2016-08-11T19:49:11Z

Michael Powers:

{{Infobox computer hardware
| name = ScripTouch Magstripe LCD Signature Pad
| logo =
| logo-size =
| logo_caption =
| image = Scriptel-ScripTouch-Magstripe-LCD 1.jpg
| image-size =
| caption =
| invent-date =
| invent-name =
| conn1 = USB 2.0 (standard A-type connector)
| via1_1 =
| class-name = Interfaces
| class1 = [[ProScript]] (ST1525)
| class2 = [[EasyScript]] (ST1526)
| manuf1 =
| designfirm =
| manufacturer = [[Scriptel Corporation]]
| introduced =
| discontinued =
| cost = $290
| type = Electronic signature pad with integrated display and magstripe card reader
| processor =
| frequency =
| memory =
| slots =
| rom =
| coprocessor =
| connection =
| ports =
| power = USB bus-powered, no separate external power supply needed
| color = Black
| dpi =
| speed =
| language =
| weight =
| dimensions = 6.25" x 5.2" x 1.6" (158.7 x 132.1 x 406mm)
}}
[[Category:ScripTouch Signature Pads]]

The first signature pad on the market for less than US$300 that features an integrated 3-track magnetic stripe reader in a rugged design that will stand up under heavy transaction volumes. In a single compact device, payment, loyalty, ID and other information found on standard magnetic stripe cards can be captured together with signatures that are rendered immediately on the backlit LCD display. Like all ScripTouch pads, it comes with an active battery-less tethered pen.

[[File:Scriptel-ScripTouch-Magstripe-LCD 1.jpg|300px]]
[[File:Scriptel-ScripTouch-Magstripe-LCD 2.jpg|300px]]
[[File:Scriptel-ScripTouch-Magstripe-LCD 3.jpg|300px]]
[[File:Scriptel-ScripTouch-Magstripe-LCD 4.jpg|300px]]

==Features==
*Integrated 3-track magnetic stripe reader
*Backlit LCD
*Scratch-resistant glass signing surface
*Active battery-less tethered pen
*Durable plastic case construction with replaceable cables
*Bottom-side rubber feet and mounting holes
*3 year warranty with RapidCare overnight exchange
*[[ProScript]] (ST1525) or [[EasyScript]] (ST1526) device interface

==Technical Specifications==

{| class="wikitable"
|Weight
|1 lbs
|-
|Dimensions
|6.25 x 5.2 x 1.6 in
|-
|Manufacturer
|[[Scriptel Corporation]]
|-
|Interface
|[[ProScript]], [[EasyScript]]
|-
|Product Type
|Electronic signature pad with integrated display and magstripe card reader
|-
|Active Signing Area
|4.25” x 1.15” (107.9 x 29.2 mm)
|-
|Signature Display
|Backlit Monochrome LCD (240×64 pixels)
|-
|Pen Type
|Active battery-less tethered pen
|-
|Sensing Technology
|Scriptel StaticCap® capacitive sensing
|-
|Min. Signature Resolution
|500ppi
|-
|Min. Signature Sample Rate
|120pps
|-
|Product Dimensions
|6.25” x 5.2” x 1.6” (158.7 x 132.1 x 406mm)
|-
|Power Supply
|USB bus-powered, no separate external power supply needed.
|-
|Thin Client / RDP
|[[Citrix Ready]] and [[ScripTouch Remote]] (USB virtualization tool) available.
|-
|Operating Systems
|Support available for Windows, Mac OS and Linux.
|-
|Warranty
|3 Year
|-
|Product Webpage
|[http://scriptel.com/products/magstripe-lcd-signature-pad/ ScripTouch Magstripe LCD product page] on scriptel.com
|-
|Model Numbers
|ST1525 ProScript, ST1526 EasyScript
|-
|Technical Specs
|[http://scriptel.com/datasheets/Scriptel-Magstripe-LCD-USB-ST1525-ST1526-DataSheet.pdf ScripTouch Magstripe LCD Data Sheet] on scriptel.com (PDF Download)
|-
|Levels of Pressure
|2
|-
|Magnetic Stripe Reader
|3-track bi-directional
|-
|Readable Card Standards
|ANSI / ISO / AAMVA
|-
|Additional Functionality
|Magnetic stripe reader
|}

==Software and Support==

===Available Software and Integration Support for ProScript===
*Microsoft Word and Excel plugins
*Adobe Acrobat and Reader plugins
*TWAIN and OPOS drivers
*ScripTouch Sign and Save signature image and data capture application
*Supports OmniScript universal signature integration platform
*Extensive APIs and software libraries in .NET (C++, VB, C# and F#)
*Windows COM also supported

===Available Software and Integration Support for EasyScript===
*Microsoft Word and Excel plugins
*Adobe Acrobat and Reader plugins
*TWAIN driver
*ScripTouch Sign and Save signature image and data capture application
*Software libraries and examples in Java, JavaScript, PHP, ASP.NET, C, C++ and Objective C
*APIs and software libraries also available for .NET (C++, VB, C# and F#)

==Interfaces==
*Model ST1525 has a [[ProScript]] interface
*Model ST1526 has an [[EasyScript]] interface

==External References==
*[http://scriptel.com/products/magstripe-lcd-signature-pad/ ScripTouch Magstripe LCD product page] on scriptel.com
*[https://escriptel.com/product/scriptouch-magstripe-lcd-signature-pad/ ScripTouch Magstripe LCD retail page] on escriptel.com
*[http://scriptel.com/datasheets/Scriptel-Magstripe-LCD-USB-ST1525-ST1526-DataSheet.pdf ScripTouch Magstripe LCD Data Sheet] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Magstripe-LCD-USB-ST1525-ST1526-Quick-Start-Guide.pdf ScripTouch Magstripe LCD Quick Start Guide] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Magstripe-LCD-USB-ST1525-ST1526-Dimensional-Drawing.pdf ScripTouch Magstripe LCD Dimensional Drawing] on scriptel.com (PDF Download)

ScripTouch Slimline 1×5 Signature Pad

2016-08-11T19:49:04Z

Michael Powers:

{{Infobox computer hardware
| name = ScripTouch Slimline 1×5 Signature Pad
| logo =
| logo-size =
| logo_caption =
| image = Slimline Image 1.jpg
| image-size =
| caption =
| invent-date =
| invent-name =
| conn1 = USB 2.0 (standard A-type connector)
| via1_1 =
| class-name = Interfaces
| class1 = [[ProScript]] (ST1475)
| class2 = [[EasyScript]] (ST1476)
| manuf1 =
| designfirm =
| manufacturer = [[Scriptel Corporation]]
| introduced =
| discontinued =
| cost = $98
| type = Electronic signature pad, slim profile without integrated display
| processor =
| frequency =
| memory =
| slots =
| rom =
| coprocessor =
| connection =
| ports =
| power = USB bus-powered, no separate external power supply needed
| color = Black
| dpi =
| speed =
| language =
| weight =
| dimensions = 6" x 5.375" x 0.95" (152.4 x 136.5 x 24.1mm)
}}
[[Category:ScripTouch Signature Pads]]

The most cost-effective ScripTouch signature pad, it has no display but it does have a low profile height, horizontal pen tray and vertical pen mount, easy-to-use mounting holes and an ergonomic palm rest for a more comfortable signing experience. Like all ScripTouch pads, it comes with an active battery-less tethered pen.

[[File:Slimline Image 1.jpg|300px]]
[[File:Slimline Image 2.jpg|300px]]
[[File:Slimline Image 3.jpg|300px]]
[[File:Slimline Image 4.jpg|300px]]

==Features==
*Slim design with wide palm rest
*Active battery-less tethered pen
*Durable plastic case construction with heavy-duty cable attachments
*Horizontal snap-in and vertical mounts
*Bottom-side rubber feet and mounting holes
*2 year warranty with RapidCare overnight exchange
*[[ProScript]] (ST1475) or [[EasyScript]] (ST1476) device interface

==Technical Specifications==
{| class="wikitable"
|Weight
|1 lbs
|-
|Dimensions
|6 x 5.375 x .95 in
|-
|Manufacturer
|[[Scriptel Corporation]]
|-
|Interface
|[[ProScript]], [[EasyScript]]
|-
|Product Type
|Electronic signature pad, slim profile without integrated display
|-
|Active Signing Area
|4.25” x 1.13” (108 x 28.7 mm)
|-
|Signature Display
|None, signature rendered on host computer.
|-
|Pen Type
|Active battery-less tethered pen
|-
|Sensing Technology
|Scriptel StaticCap® capacitive sensing
|-
|Min. Signature Resolution
|500ppi
|-
|Min. Signature Sample Rate
|120pps
|-
|Product Dimensions
|6” x 5.375” x 0.95” (152.4 x 136.5 x 24.1mm)
|-
|Power Supply
|USB bus-powered, no separate external power supply needed.
|-
|Thin Client / RDP
|[[Citrix Ready]] and [[ScripTouch Remote]] (USB virtualization tool) available.
|-
|Operating Systems
|Support available for Windows, Mac OS and Linux.
|-
|Warranty
|2 Year
|-
|Product Webpage
|[http://scriptel.com/products/slimline-1x5-signature-pad/ ScripTouch Slimline 1×5 product page] on scriptel.com
|-
|Model Numbers
|ST1475 ProScript, ST1476 EasyScript
|-
|Technical Specs
|[http://scriptel.com/datasheets/Scriptel-Slimline-1X5-USB-ST1475-ST1476-DataSheet.pdf ScripTouch Slimline 1×5 Data Sheet] on scriptel.com (PDF Download)
|-
|Levels of Pressure
|2
|}

==Software and Support==

===Available Software and Integration Support for ProScript===
*Microsoft Word and Excel plugins
*Adobe Acrobat and Reader plugins
*TWAIN and OPOS drivers
*ScripTouch Sign and Save signature image and data capture application
*Supports OmniScript universal signature integration platform
*Extensive APIs and software libraries in .NET (C++, VB, C# and F#)
*Windows COM also supported

===Available Software and Integration Support for EasyScript===
*Microsoft Word and Excel plugins
*Adobe Acrobat and Reader plugins
*TWAIN driver
*ScripTouch Sign and Save signature image and data capture application
*Software libraries and examples in Java, JavaScript, PHP, ASP.NET, C, C++ and Objective C
*APIs and software libraries also available for .NET (C++, VB, C# and F#)

==Interfaces==
*Model ST1475 has a [[ProScript]] interface
*Model ST1476 has an [[EasyScript]] interface

==Extenal References==
*[http://scriptel.com/products/slimline-1x5-signature-pad/ ScripTouch Slimline 1×5 product page] on scriptel.com
*[https://escriptel.com/product/scriptouch-slimline-1x5-signature-pad/ ScripTouch Slimline 1×5 retail page] on escriptel.com
*[http://scriptel.com/datasheets/Scriptel-Slimline-1X5-USB-ST1475-ST1476-DataSheet.pdf ScripTouch Slimline 1×5 Data Sheet] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Slimline-1X5-USB-ST1475-ST1476-Quick-Start-Guide.pdf ScripTouch Slimline 1×5 Quick Start Guide] on scriptel.com (PDF Download)
*[http://scriptel.com/datasheets/Scriptel-Slimline-1X5-USB-ST1475-ST1476-Dimensional-Drawing.pdf ScripTouch Slimline 1×5 Dimensional Drawing] on scriptel.com (PDF Download)