products | support | ask for info | about us

Frequently Asked Questions programming issues  

faq home



programming tips


device driver

FAQ programming issues

Here you can find some tips and answers to the most common questions about the programming with the WizzKey API software.

WizzKey: The Key To Software And Security

How does the WizzKey protect the application?
When a protected application calls a routine from the WizzKey API, it will search the computer's I/O ports for a WizzKey. If the key is attached it will communicate to the software, and performing the required functionality. Without the key, the software application would receive an error. It is primarily up to the developer to determine what sort of action to take when this error occurs (i.e. the software will not run at all, or the software runs in a limited mode).
How much work will it require for me to implement a good protection for my product?
A fairly good security can already be achieved with very little effort. All you need to do is to put some software locks on appropriate places in your software. You can find in the manual some tips and guidelines on how to implement a good protection of your software with the WizzKey protection system. As a general rule you can say that a first step in software protection is reached within half an hour.
The WizzKey API contains a lot of routines. Which routines should I use?
That all depends on the level of security you intend to reach. The best would be to use as much as possible routines, spread around your program. To make it a possible hacker more difficult, you could postpone your reaction to a possible negative result some time. In this way it will be much harder to find out where the original test has been called.
Which DLL should I use?
The software kit provides basically two kinds of DLLs for 32-bit programs. They are almost equal, except that one DLL does not require that the keycode and codeword are applied by the application program, whereas the other one (wkdll32.dll) is more generic, and does require that the application program provides the keycode and codeword (using the routine OpenWK). The first one is the most simple, but the second one is more generic.
Where can I find the latest software?
A unique feature of the WizzKey family is that every user of the WizzKey family receives its own set of software, the WizzKey dongles, and possibly a programmer with programming software. However, some software is general applicable for all WizzKeys. This software can be downloaded from this site free of charge.
Do I need to know on which port the WizzKey is connected?
No, the software will search for a WizzKey on all ports the first time any routine from the API is called. This implies that the ports will have signals on their lines that are needed to detect a WizzKey. In some situations this can lead to undesired effects, since some printers might interpret the same signals as control-signalling. Although this is out of the specs of a parallel port, it happens. If this is the case, then you might use a special routine from the API (InitKey), in which you can assign one port that should be searched for a WizzKey the first time. When no WizzKey will be found on this port, the others will be searched, just as normal.
How much time does it take before the software has detected a WizzKey on the PC?
This mainly depends on the speed of the computer and the port to which the WizzKey is attached to. The software will scan all ports of the PC it is running on, and will determine the required timing to communicate with the dongle. In general a WizzKey can be found within several milliseconds.
Can I make my software and security unique?
Yes, this is quite well possible for all kinds of WizzKey. Each WizzKey has a unique ID-number that can be read with a routine from the WizzKey API. The WizzKey Red Label provides even more personalization possibilities since it has an internal memory of 100 bytes. This WizzKey also allows you to change the encryption-keys and algorithms. The encryption and decryption of data is thus become dependent on the key attached to the computer.
products | support | ask for info | about us