Cause: KEYLOK Parallel port dongles communicate using I/O ports 278H, 3BCH and 378H. In order for the Parallel port dongle to be recognized by a PCI parallel port it must have the ability to be set to one of these ports either through hardware switches or software.
Solution: If you are not able to set the I/O Ports then KEYLOK suggests switching to KEYLOK2 USB keys which have the same functionality as the parallel keys but just different form factor.
Install Utility Command Line Arguments
Install.exe Utility
|
Delimiters |
Valid command line delimiters are ‘/’ or ‘\’ or ‘-‘ A space is required before each delimiter and options cannot be combined (i.e. ‘/QN’ is illegal, but ‘/Q /N’ is legal). |
|
/A |
Install both parallel port and USB driver files Note: This option will result in a parclass error 0x37 if a parallel port dongle is not attached during the installation process. |
|
/B |
Install USB driver files only |
|
/C |
Install network Client files and USB drivers Allows local USB dongle or remote USB or parallel port dongle |
|
/F |
Install Fortress files only |
|
/NP |
Install parallel port TCP/IP server networking drivers to allow remote access to a parallel port dongle via a TCP/IP network |
|
/NB |
Install USB TCP/IP server networking drivers to allow remote access to a USB dongle via a TCP/IP network |
|
/NF |
Install Fortress TCP/IP server networking files to allow remote access to a Fortress dongle via a TCP/IP network. |
|
/P |
Install parallel port driver files only |
|
/Q |
Quiet mode install – displays only fatal errors |
|
/S:<IP address> |
Valid only for a network client install. Forces the client to attempt to connect to the dongle server at <IP address>. You may also specify the network name of the server instead of its IP address. |
|
/U |
Uninstall Removes all previously installed files |
Cause: For security reasons some machines are built with no C:\ drive and KEYLOK Installer by default looks for C:\ drive to install the driver, causing the error you're experiencing.
Solution: To install on a machine with no C:\ drive. Copy the USBKey.sys or USBKey64.sys and USBKey.inf or USBKey64.inf, located on KEYLOK SDK “Send to End-Users\Optional Manual Installation Files”, to DriveLetter\Windows\System32. Edit the USBKey.inf or USBKey64.inf so the bottom line reads DISKID1= “Hard Driver YOUR DRIVE LETTER” instead of “DiskID1 = HARD Drive C:” and save the file. Go to the Device Manager, plug in the Key and when it appears in Device Manager Right-Click and select Update Driver and Select Install from specific location then navigate to System 32 and click on Install Driver. This should resolve the issue.
Cause: The issue that you are experiencing can be caused for various reasons. KEYLOK driver is not installed at all or not installed properly. If it’s a network key, an install is required on both Client and Server machines.
Solution: Check to see if the proper driver is installed. Go to the device Manager on your machine by Right-Clicking on “My Computer ->Manage->Device Manager” and if you see an exclamation mark next to USB Dongle – Software Protection Device then right-click on it and “Update Driver”.
If the problem persists, perform the following steps:
This should resolve the issue and the key should show up as follows in your device manager:
In a network environment there can be many reasons the key is not being recognized by the application. To request our Network Troubleshooting Guide, please contact Technical Support.
Quick Start Guide for KEYLOK2 dongle
