home 
  products | support | ask for info | about us
 

Installation Frequently Asked Questions  



faq home


general

installation

programming tips

problems

device driver

FAQ installation

Here you can find answers to the most common questions about the installation of the WizzKey software.

WizzKey: The Key To Software And Security

Where should I install the WizzKey DLLs?
There are no special requirements for that. However, in any case you should make sure that Windows is able to find the right DLL. A normal place would be at the same location as where your main application is stored. In this way there is less chance of using the wrong DLL (in case there are multiple in the system).
When do I need a device driver?
In general, Windows (NT/2000/XP) requires any hardware peripheral to be governed by a driver. This implies that in case of WizzKey, a device driver is needed for all applications that use the WizzKey routines running under Windows NT/2000/XP.
Which device driver should I use?
There are different device drivers for the various WizzKey brands. For the WizzKey Red Label and the WizzKey programmer you should apply wkrl.sys, for the WizzKey White Label wkwl.sys.
In case you write 16-bit programs (like DOS), it is not possible to use these device drivers. In that case you should use the generic device driver wkport.sys. It that case you can use the normal routines (provided in .OBJ or a DLL), but the device driver has to be opened once. Please check the documentation on this issue.
How do I install the device driver?
In the software kit with the WizzKey API and the device driver, is a small installation program that can be used to install the driver. Alternatively, you can write your own installation program using the template provided in the documentation, or take a look at the installation program example.
I am trying to install the WizzKey Device Driver on my Windows NT/2000/XP. I get a message saying that I have insufficient privilege to install the driver. What should I do?
Installing any system driver on an NT/W2000 station requires administrative privilege. Therefore, log in as an administrator and try again.
 
products | support | ask for info | about us