This file contains instructions and known issues related to the Interlink Electronics ePad product line applications and hardware.
For the latest information, please refer to the file 'errata.txt' on your installation CD and/or visit our web site at:
Information in this file is organized in the following sections:
Wintab / Wintab emulation is no longer supported.
This version of PC software requires firmware >= 0.98.
If you have a previous version of software installed for any Interlink ePad, you must uninstall the previous version before installing this version.
To remove an older version of ePad software from your system:
To install this ePad System Software, insert the setup CD into your computer's CD-ROM drive and follow the instructions to complete the installation of the ePad software. If the autorun does not automatically start, run setup.exe from the CD-ROM.
Installation can be automated by using response files. To generate a response file, run setup.exe on a typical target machine as follows:
** These commands should be typed into a command prompt window or the Windows Run dialog (accessible by clicking Start --> Run). Replace <full_path_to_setup> with the fully qualified path and file name where setup.exe is located (ie: d:\setup.exe). Replace <full_path_to_response_file> with the fully qualified path and file name where the response file is to be created/read from (ie: c:\response.in).
<full_path_to_setup> /r /f1"<full_path_to_response_file>"
Configure the installation as you want all targets to be configured. When setup completes successfully it will create the response file at the location specified.
To run the installer silently, issue the following command on the client machine(s) (this assumes you've copied setup.exe and the generated response file to the client):
<full_path_to_setup> /s /f1"<full_path_to_response_file>"
NOTE: Citrix ICA client support is not available for ePad-i.d. or ePad-i.d. Pro.
When the Citrix ICA Client feature is selected in the installer, every effort is made to locate the module.ini file. This file is a by-product of the Citrix ICA client installation. The module.ini file is a text file, which can be edited via Notepad (or similar text editor). Like all INI files, module.ini contains sections and identifiers.
If the Installer cannot find the module.ini file, then the instructions contained in the remainder of this section can be used to manually configure the module.ini file for ePad support.
Citrix ICA client support is provided for the following ePad products by using the file names designated:
| Provider Name | Section Name | File Name |
|---|---|---|
| ePad RS-232 | ePadRS232 | rs232u.dll |
| ePad USB | ePadUSB | ieusbioc.dll |
| ePad-ink USB | ePadInk | ieusbioc.dll |
| ePad II USB | ePadII | ieusbioc.dll |
| ePad-ink Pro | ePad-inkPro | ieusbioc.dll |
| ePad LS | ePadLS | ieusbioc.dll |
In order to install Citrix ICA client support, one must know the folder where the Citrix ICA client is installed. This folder will be referred to as the "Citrix-folder" in the following discussion. One must also know which ePad products are to be installed.
The first step is to copy the appropriate provider files to the Citrix-folder. The ePad Provider file is simply copied to the Citrix-folder using Windows Explorer or a similar tool.
The second step is to update the module.ini file; for this step, some definitions are noteworthy. Within an INI file, a section name is a tag enclosed in brackets, like this: [VirtualDriver]. An identifier is a name followed by an equal sign; the text to the right of an equal sign is the value (in the line, Driver=test, "Driver" is the identifier and "test" is the value).
The module.ini file resides in the Citrix-folder. There should already be a section named "ICA 3.0"; within this section is an identifier named "VirtualDriver". The value field must be modified to contain a comma-separated list of ePad provider names. Use the section names introduced previously for values:
As an example, if both ePad USB and ePad RS-232 are to be installed, then the text ",ePadRS232,ePadUSB" would be appended to the end of the value for the VirtualDriver identifier.
Next, add an "empty" identifier for each provider in the existing [VirtualDriver] section. Using the above example, the new identifiers would look like this:
|
[VirtualDriver] . . . ePadRS232 = ePadUSB = |
The final step is to add sections and values for each of the ePad providers to be installed. There should be a one-to-one correspondence for each item added to the value for the VirtualDriver identifier in the "ICA 3.0" section. Using the preceding example, both "ePadRS232" and "ePadUSB" must be added as sections.
The sections to be added may be simply appended to the end of the file. There are two identifiers to be added to each section, "DriverName" and "DriverNameWin32", both of which have as values the corresponding filenames.
Again, using the example above, the following sections and identifier/value name pairs would appear in module.ini:
| [ePadRS232] DriverName = rs232u.DLL DriverNameWin32 = rs232u.DLL [ePadUSB] DriverName = ieusbioc.DLL DriverNameWin32 = ieusbioc.DLL |
The liberal use of spaces can be included to improve overall readability, but their use is strictly optional.
To manually uninstall the Citrix ICA Client feature, simply remove the entries made in the module.ini file during the installation process. Then remove the ePad support files from the Citrix-folder.
Automatic installation is available in the installer. In the event you wish to manually enable support for Terminal Services, the following procedures can be used:
Terminal Services may be manually configured for the following ePad products by using the file names designated:
| Provider Name | Folder Name | File Name |
|---|---|---|
| ePad RS-232 | ePadRS232 | rs232u.dll |
| ePad USB | ePadUSB | ieusbioc.dll |
| ePad-ink USB | ePadInk | ieusbioc.dll |
| ePad II USB | ePadII | ieusbioc.dll |
| ePad-ink Pro | ePadInkPro | ieusbioc.dll |
| ePad LS | ePadLS | ieusbioc.dll |
Create the following registry folder:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\<Folder Name>
(type,keyValue,value)
REG_SZ,Name,<File Name>
REG_DWORD,Type,0x03
Create the following registry folder:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\AddIns\<Folder Name>
(type,keyValue,value)
REG_SZ,Name,<File Name>
Must have Administrator access
Thin clients are typically configured with a limited user account (User)
and an Administrator account. To log on as Administrator, hold down the
shift key and log-off User.
Installation package must be accessible via network
Since the Wyse thin client has no CD drive, the only means for obtaining the Universal
Installer is via a drive mapping on the network. Therefore, the installer should be placed
in a folder accessible by the thin client.
Temp directory must have sufficient free space
Since the installation package is unpacked to the Temp directory, the Temp directory must
have enough space for the intermediate files. The Temp folder is oftentimes drive Z:, which
is a small RAMDisk. To ensure that the Temp folder is large enough, create a new Temp
directory on the C: drive (C:\Temp) and change the 'TEMP' environment variable to point to
the new directory. To change the environment variable:
The Enhanced Write Filter should be disabled
There is an Enhanced Write Filter Control utility as part of the Wyse thin clients. This
program monitors system resources and when a threshold is reached, automatically reboots the
system. After rebooting, all the changes that had taken place since the last logon are
rolled back. Therefore, if the software installation is to be permanent, the EWF must be
disabled before running the ePad software installer.
During installation, select the Custom setup. Select the appropriate ePad devices as well as MS Terminal Services and/or Citrix client options as necessary.
This option will result in data only being reported within the specified inking region of the device. The data is rescaled so that unity is within this region. Note that no data reports will occur outside this region when this option is enabled.
In firmware versions 1.00 and earlier contact with the touchscreen while performing I/O to the device (such as transferring a background image) may result in the device failing to respond over the USB bus. The end result is that device functionality will be lost. To recover:
OR
If the computer is shut down or restarted while an application is using an ePad-ink unit, the display may not be cleared. The display should be refreshed the next time an application initializes it or it can be manually cleared by unplugging the unit and then plugging it back in.
On at least some HP / Compaq PC's we have observed that the process EAUSBKBD.EXE will open the ePad-ink preventing our system software from using our own pad. The solution to this is to:
The ePad-ink Pro can be used as a replacement for the ePad-ink in applications that were coded for the ePad-ink specifically. To use the ePad-ink Pro in this scenario (referred to as compatibility mode), it is necessary to install the ePad software for both ePad-ink and ePad-ink Pro.
It is important to note that while every attempt was made to implement the exact same interface, there are some limitations when using the ePad-ink Pro in a native ePad-ink application.
If light pressure is used when signing with an ePad-i.d. unit, sporadic lines ("lightning bolts") may be inserted into the signature field. To ensure this does not happen, be sure to use firm pressure when signing.
Acrobat by default wants to execute acrotray.exe on startup. This appears to pre-load the CIC-EX program causing the RS232 COM port to become locked so our software cannot access the rs232 ePad. The solution is as follows:
The screensaver option fails when attempting to set it while initializing the pad. To change the default screensaver behavior, set the option after the pad has been initialized.
In some cases applications attempt to access the COM port preventing the "just in time" connection to the RS232 port. If you are writing your own software to our COM API you must deal with this yourself.
Auto-scan is the default setting and is the most robust at device detection. However it can cause delays when preparing to use the ePad as it must attempt to locate the device on all com ports. If this is an issue, go into the control panel and select the specific port that you know the pad is connected to.
Additionally the software will attempt to scan the specific port (or all ports if in "auto-scan" mode) to count the number of devices if client software requests the # of devices. This also can be a slow process. This process may be disabled by writing a 0 value to the following registry key:
Software\InterlinkElectronics\RS232ePad\detectPasses
(The default value for this field is 10, even if it is not listed in the registry.)
Some models of Compaq computers running Windows 2000 may stop responding upon shut down or restart when an ePad-i.d. Pro, ePad-ink Pro or ePad LS device is attached. If this problem is encountered, configure the BIOS of the computer such that booting from a USB device is not allowed. Consult the computer manufacturer's documentation for instructions on modifying the BIOS settings.
The inking width for signing is not adjustable. This feature is expected in an upcoming maintenance release.
When programming for the ePad LS, the inking region must be disabled before the command to clear the inking region can be processed. If the inking region is not disabled, the clear ink command will fail.
When using the ePadLSu_test.exe CLI test tool, some commands may return "Msg: access is denied" when the ePad is in inking mode, because many commands are not available when the ePad is in inking mode (showink 1). This message should be more meaningful and indicate that "The command is valid, but not allowed when inking mode is ON."
If you have changed the default bitmap for the device and would like to reset it to the factory default image, you may do so by using the Configuration applet found in the Windows Control Panel. The factory default background image can be found in your ePad software installation directory (C:\Program Files\InterlinkElectronics\ePad\LSdefaultBackground.jpg).
Some of the text window formatting tags may not display as expected.
Text files for the ePad Demo Builder should not exceed 8192 characters. Unexpected behavior can result when using text files beyond this limit.
When calling the scriptiface USB OpenConnection function, the handle counter increases and does not decrease until the calling application ends. Depending on the memory size of the host computer, long term use of the ePad XL - such as three years without rebooting - may exhaust all the host PC resources eventually causing a system halt.
The included ePad XL demos require IntegriSign Desktop to be installed before they can be run.
Questions concerning this product should be addressed to Interlink
Electronics Technical Support at:
Phone:..............................800-340-1331
Fax:................................805-484-8380
Email:..............................psupport@interlinkelec.com
FAQ's and Live Chat:................http://www.interlinkelectronics.com/support/
Technical support hours:............7:00 AM to 5:00 PM US Pacific Time
Corporate Headquarters:
Interlink Electronics
546 Flynn Road
Camarillo, CA 93012 USA
Phone:..............................805-484-8855
Fax:................................805-484-8989
----------------------------------------------------------------------
Interlink Electronics acknowledges all tradenames and trademarks used
in this document as the property of their respective owners.