Category:UniKey FAQ

UniKey Frequently Asked Questions Category

Yes, we can provide cross-compilation for the UniKey Library. Please contact our support team at support@esecutech.com along with the cross compilation tool chain. We will be able to reply you with the the cross-compiled library as soon as possible.

Yes. Please contact SecuTech Solution Inc at sales@esecutech.com or our distributor in your local area.

Yes. UniKey STD/PRO/Time and UniKey Drive support DotNet applications.

UniKey STD/PRO/Time SDK has native UniKey Win32_64.DotNetDll library support. These libraries support .net versions 2.0, 3.0, 3.5, 4.0. UniKey Drive also includes DLL libraries which can be used for integration with DotNet projects.

Please note UniKey Drive's DLL libraries is built from C, and UniKey STD/PRO/Time's DotNet Libraries are built from DotNet project.

For UniKey STD/PRO/Time, you only need to use one version of the UniKey DotNet library for both 32-bit and 64-bit systems.

For UniKey Drive, you need to use the two versions of the DLL libraries - One for 32-bit systems and the other for 64-bit systems.

All the DLL libraries should be imported into the working directory of your project. For example, the DLL libraries can be imported into the same directory as the executable file(s).

Yes. Please use the UniKey DotNet libraries. Samples are provided to illustrate how to use the UniKey APIs.

Yes. Please use the UniKey DotNet libraries. Samples are provided to illustrate how to use the UniKey APIs.

Please use administrator permissions to enable the system to recognize UniKey Drive under a Windows XP non-administrator user account.

UniKey devices is driverless, meaning usage of UniKey requires no installation of drivers or additional software. Supported operating systems already possess drivers needed by UniKey to operate and are automatically installed upon the first connection of the UniKey device, significantly reducing the problems associated with driver-dependent devices.

If the LED light on the UniKey device is continually on, it is recognised by the computer and should be functioning correctly. If the LED light on the UniKey device is flashing, the UniKey device is not recognised by the computer. If this is the case, reconnect the UniKey device to the computer, otherwise contact SecuTech Technical Support at http://www.eSecuTech.com/support or support@eSecuTech.com.

Under normal circumstances, the LED light should not be flashing when used under Windows, Mac OS, MinGW, MIPS, ARM, FreeBSD and Linux in general.

A situation where the LED light on the device may be flashing is if you are using UniKey on a Virtual Machine. Please check if you have mounted the UniKey Device into the system. After mounting then device, don't remove the dongle and restart the system under the Virtual Machine. The device should now be recognized by the system.

Please follow the UniKey Hardware Troubleshooting guide.

Yes. UniKey is compatible with USB 3.0 ports.

The ten digit number engraved on the USB head of UniKey devices is not the hardware ID number, but the product's serial number. It is for internal use only, and, as such, additional information cannot be provided if requested.

Error 117 indicates that the UniKey Network Service isn't started on the machine. Please install the UniKey Network Server Service before using client to connect to the server. The UniKey Network Server can be found in \UniKey SDK\Network\Server\Network.Server.ia32.

Error 105 indicates that UniKey client-side and server-side communication is blocked. This will occur when a firewall at either end is blocking communication. Please close firewall for both server side and client side while you are testing UniKey Network Feature.

Yes. Please use UniKey Console Tool or the UniKey_Generate_New_Password API function for setting a new password for the UniKey dongle.

For reasons of security, each UniKey device can only generate a new password twice.

No. The UniKey device can't be duplicated.

Yes. If you wish to use the same password for all or a set of UniKey devices, use the same seed value for generating the same password for your UniKey STD/PRO/Time/Drive device. Please note that UniKey STD/PRO/Time's password system is different from UniKey Drive, as UniKey Drive implements eight digit password length.

You may be able to resolve this with the following code:

short[] p1 = new short[1];

short[] p2 = new short[1];

short[] p3 = new short[1];

short[] p4 = new short[1];

int IntPW1 = 17530;

int IntPW2 = 15802;

int IntPW3 = 42116;

int IntPW4 = 26965;

p1[0] = (short)IntPW1;

p2[0] = (short)IntPW2;

p3[0] = (short)IntPW3;

p4[0] = (short)IntPW4;

long retval = mUniKey.UniKey_Vender_Logon(handle,p1,p2,p3,p4);

A tool for generating small value passwords for UniKey Drive with VB6 can be provided upon request. Please contact support@esecutech.com.

There isn't any limit on the number of login attempts after the password is set on UniKey devices, however the password can only be changed twice.

There isn't any limit for the vendors to log on to the dongle. After binding the dongle with your software, the end user only need to insert the correct dongle in order to run your software. There isn't a chance for the end users to try to input password to log on the dongle.

No, UniKey is driver-independent and will work under Windows 8.

Please refer to the UniKey Real Time Clock Protection Solution from

SecuTech Wiki -> Software Protection -> UniKey Application Solution

This article will guide you on how to use UniKey RTC Protection Solution from the beginning.

Each UniKey Time dongle has 16 time modules.

Each time module adds certain functionality. For example, the software expiry date can be set with a time module. A start time and an end time for Time Module No. 1, for example, can be set and then bound to with your software.

Currently, the UniKey Envelop Tool can only set time modules, but not read the time modules. Please note this, as even if you have saved the Envelop Project, it will not be able to read back the time module you have set.

UniKey_Check_Time_Module references a given time.

UniKey_Check_Time_Module_Now references the time from the inbuilt clock within the dongle.

UniKey_Check_Time_Module_Now_PC references the time from the host machine's system.

Yes. Libraries and associated samples are provided for using UniKey STD/PRO/Time with SUSE10. Please be sure to use su permissions.

During normal operation, the UniKey Time device draws power from the machine when in use, and uses its inbuilt battery when not plugged in. On battery alone, a typical UniKey device lasts for 3 years.

When the battery within the device runs out, the dongle will revert that to a UniKey PRO dongle, so as to function as and encompass all of the features of a UniKey PRO device.

This will allow the device to continue to protect your software, however the real time clock feature will cease to function, requiring the end user to contact you to replace the device if necessary.