Interlink Electronics ePad v6.24
$Date$
© 2004/2005 Interlink Electronics, Inc.
All Rights Reserved
This file contains late-breaking information about the Interlink Electronics ePad product line applications and hardware.
For the latest information, please visit our web site at:
http://www.interlinkelectronics.com/
Information in this file is organized in the following sections:
This version of PC software requires firmware >= 0.98.
FontDemo is supplied in the installation directory and demonstrates how to use the supplied graphics library directly and indirectly using GDI functions.
First make sure there is no other wintab driver installed. This driver will detect wintab32.dll file and stop the installation.
If you have an older version of ePad driver installed, please uninstall it before you install this driver.
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:
setup /r /f1"response.in"
Configure the installation as you want all targets to be configured. When setup completes successfully it will leave the file "response.in" on your hard-drive.
To run this using the response file (thus avoiding manual input to the setup program), issue the following command on additional client machines (this assumes you've copied setup.exe and the generated response.in file to the client):
setup /s /f1"response.in"
NOTE: Citrix ICA client support is not available for ePad-ID.
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 filenames designated:
| Provider Name | Section Name | File Name |
|---|---|---|
| ePad RS-232 | ePadRS232 | rs232u.dll |
| ePad USB | ePadUSB | epadusb.dll |
| ePad-ink USB | ePadInk | iewedgeu.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 = epadusb.DLL DriverNameWin32 = epadusb.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:
Create the following registry folder:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AddIns\ePad-ink
(type,keyValue,value)
REG_SZ,Name,iewedgeu.dll
REG_DWORD,Type,0x03
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\AddIns\ePad-ink
(type,keyValue,value)
REG_SZ,Name,iewedgeu.dll
Utility application used to load and keep a reference to Wintab so that in the case of RS232 the port is held open by our software.
Usage:
This program is designed to perform most of the functions that can be performed with the ePad-ID device. Prior to its use however, the unit must be powered on via the ePad-ID Test Utility. To perform this power on function, run the test utility and execute the 'tfp' option (Toggle FP power). The test utility will respond with FP power is ON (or OFF) respectively.
The Microsoft Enhanced Cryptographic Provider supports the same capabilities as the Microsoft Base Cryptographic Provider, but provides for stronger security through longer keys and additional algorithms. The Enhanced provider is installed on your machine when you apply the Internet Explorer 128-bit security patch available from http://www.microsoft.com/windows/ie/downloads/recommended/128bit/default.asp.
Although the installer attempts to determine if a wintab stack has already been installed it is a good idea to ensure that no other wintab systems are installed prior to installing this software.
Earlier firmware versions also published a HID-mouse interface. If you are using a serial mouse and have one of these older units, please make sure it is installed correctly *before* attaching the ePad-ink to the USB port. If your system does not show a serial mouse (even though the mouse appears to be working) you must go to through the add new hardware function off of the control panel and complete both PNP and non PNP device detection. This should properly install the serial mouse.
Failure to do so will result in the system "losing" the mouse function off of the serial port.
On some versions of Win98 the dynamic linked library file (dll) "iepadenum.dll" may fail to register. This warning message may be safely ignored.
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
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.
When you are installing the drivers, you might get a message like the following:
Please insert the disk labeled 'Windows [version] CD-ROM', and then click OK.
If this occurs, follow the instructions in the message. In some cases, the file it needs may not be found on the operating system disk; if so, you will get another message, this time asking for a specific file on the disk. You will need to direct the wizard to the appropriate location, per the table below. (Replace the drive letters as appropriate to your system.)
| File name | Copy files from |
|---|---|
| TC_98_ME.cat | C:\Program Files\InterlinkElectronics\ePadID\FPDriver * |
| CODIALOG.DLL | C:\Program Files\InterlinkElectronics\ePadID\FPDriver * |
| usbscan.sys | D:\win98\driver20.cab |
* If you installed the ePad-ID program somewhere other than this default path, modify it accordingly.
TouchChip Sensor drivers have not met Microsoft Digital Signature authentication and have not been WHQL Certified. This means Windows 2000 and XP may give "digital signature not found" messages when installing the drivers. Please ignore the messages and continue driver installation. Please see the Microsoft website for more information.
If the automated execution of the bioAPI (Biometrics Application Interface) installation files fail, you may have to run them manually. In My Computer or Windows Explorer, find the folder where you installed ePad-ID, then open the subfolder named 'stbuild'. Double-click the batch file (.bat) named after your operating system. For example, if your operating system version is Windows 98 or Windows Me, you should double-click the file named install_w98.bat.
CIC-EX has been shown to hold the COM port open, preventing the software from working with it. The supplied "QuickStart" utility can be moved to the startup folder and will hold the COM port open so that CIC-EX can be used with this software.
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:
rs232q "/start=[pathToAcrotrayDir].exe" "/delay=30"
This will cause acrotray to run 30 seconds *after* rs232q has started. Note that during this time publishing (printing) to acrobat will be unavailable.
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. If you are using the wintab emulation layer you can execute the "QuickStart" program -- this will hold connections open to the service providers.
However, when this program is running the VBDemo will be unable to communicate with RS232 epads. Simply close the systray icon (right-click, exit) and continue using VBDemo.
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.)
If QuickStart is running while attempting to shutdown or restart the system the user may be prompted to end an internal process to QuickStart; select "end" to continue. This message may be avoided by closing QuickStart before shutdown or restart.
Questions concerning this product should be addressed to Interlink
Electronics Technical Support at:
Phone:..............................805-484-1331
Toll free in the US:................800-340-1331
Fax:................................805-484-5997
Email:..............................psupport@interlinkelec.com
Technical support hours:............8:00 AM to 5:00 PM US Pacific Time
Corporate Headquarters:
Interlink Electronics
546 Flynn Road
Camarillo, CA 93012 USA
Phone:..............................805-484-1356
Fax:................................805-484-8989
Japan Office:
Interlink Electronics KK
2-5-12 Higashi-Kanda
Chiyoda-Ku Tokyo, 101 Japan
Phone:..............................+81-3-3863-6493
Fax:................................+81-3-3863-6442
----------------------------------------------------------------------
Interlink Electronics acknowledges all tradenames and trademarks used
in this document as the property of their respective owners.