| Home | Installation | Local | Printer | WkLAN | WkNet | Encrypt | FAQ | Imprint | | German | English |

Tips: Installation of WIBU-KEY drivers

When installing the WIBU-KEY drivers always use the current version, which you can download from our homepage. driver download


Operating System Description Files
DOS Normally no special driver is required for DOS applications. But if you are running a DOS application in a DOS box of Windows 95/98 or Windows NT the program WKDOS.EXE is required. This tool maps the WIBU-KEY API calls to the WIBU-KEY kernel driver that is required for these operating systems.
NOTE: Even though WIBU-KEY protected DOS applications may run on Windows 95/98 with direct hardware access it is strongly recommended that you install the normal WIBU-KEY drivers for Windows 95/98 and use WKDOS.EXE

Is not supported anymore

WKDOS.EXE
Windows 3.x For Windows 3.x the following two files are required. Both of them are located in the System folder of Windows 3.x.
WKWIN.DLL - WIBU-KEY kernel driver for Windows 3.x
WIBUKEY.CPL - WIBU-KEY Control Panel Applet.

Is not supported anymore

WKWIN.DLL
WIBUKEY.CPL
Windows 95 For Windows 95 the following files are required. All of them are located in the System folder of Windows 95.
WIBUKEY.VXD - Kernel driver for WIBU-KEY on Windows 95
WIBUKE32.CPL - WIBU-KEY Control Panel Applet
WKWIN.DLL - Calling driver for 16 bit applications (if required)
WKDOS.EXE - Driver for DOS applications (if required)
WIBUKEY.INF - Support for Windows 95/98-Plug&PlayNote: Only the 32 bit control panel applet
Important:Some system DLLs must be reinstalled or updated in order to run WIBU-KEY on W95.
Please, use the Microsoft Installation Programm msaardk.exe which you will find on the WIBU-KEY CDROM in the directory \Tools\Microsoft or which you can download msaardk.exe.

Note: Only the 32 bit control panel applet WIBUKE32.CPL is designed for using it on Windows 95. The 16 bit version WIBUKEY.CPL can be installed but it cannot change the driver settings for the kernel driver.

Is not supported anymore

WIBUKEY.VXD
WKWIN32.DLL
WIBUKE32.CPL
WKWIN.DLL
WKDOS.EXE
WIBUKEY.INF
Windows 98/ME For Windows 98/ME the following files are required. Most of them are located in the System folder of Windows 98/ME. The only exception is WIBUKEY2.SYS which is located in the SYSTEM32/DRIVERS folder.
WIBUKEY.VXD - Kernel driver for WIBU-KEY on Windows 98/ME
WIBUKEY2.SYS - Kernel driver for WIBU-KEY on Windows 95/98/ME
WKWIN32.DLL - Calling driver for WIBU-KEY on 32-Bit-Windows
WIBUKE32.CPL - WIBU-KEY Control Panel Applet
WKWIN.DLL - Calling driver for 16 bit applications (if required)
WKDOS.EXE - Driver for DOS applications (if required)
WIBUKEY.INF - Support for Windows 95/98-Plug&Play
WIBUKEY.VXD
WIBUKEY2.SYS
WKWIN32.DLL
WIBUKE32.CPL
WKWIN.DLL
WKDOS.EXE
WIBUKEY.INF
Win 2000/XP/ Vista/ 7/ Server 2003/ Server 2008 For Win 2000/XP/ Vista/ 7/ Server 2003/ Server 2008 the following files are required. Most of them are located in the System folder or Driver folder (WIBUKEY.SYS & WIBUKEY2.SYS) of Windows.
WIBUKEY.SYS - Kernel driver for WIBU-KEY on Windows NT-based OS
WIBUKEY2.SYS - Kernel driver for WIBU-KEY on Windows for USB (PnP)
WKWIN32.DLL - Calling driver for WIBU-KEY on 32-Bit-Windows
WIBUKE32.CPL - WIBU-KEY Control Panel Applet
WKWIN.DLL - Calling driver for 16 bit applications
WKDOS.EXE - Driver for DOS applications
WIBUKEY.SYS
WIBUKEY2.SYS
WKWIN32.DLL
WIBUKE32.CPL
WKWIN.DLL
WKDOS.EXE
Win 2000/XP/ Vista/ 7/ Server 2003/ Server 2008
64 Bit
For Win 2000/XP/ Vista/ 7/ Server 2003/ Server 2008 the following files are required. Most of them are located in the System folder or Driver folder (WIBUKEY.SYS & WIBUKEY2.SYS) of Windows.
WIBUKEY64.SYS - Kernel driver for WIBU-KEY on Windows NT-based 64 OS
WIBUKEY2_64.SYS - Kernel driver for WIBU-KEY on Windows for USB (PnP)
WKWIN64.DLL - Calling driver for WIBU-KEY on 64-Bit-Windows
WIBUKE64.CPL - WIBU-KEY Control Panel Applet
WIBUKEY.SYS
WIBUKEY2_64.SYS
WKWIN64.DLL
WIBUKE64.CPL
Windows NT For Windows NT (3.51 and 4.0) the following files are required. Most of them are located in the System folder of Windows NT. The only exception is WIBUKEY.SYS which is located in the Driver folder.
WIBUKEY.SYS - Kernel driver for WIBU-KEY on Windows NT
WKWIN32.DLL - Calling driver for WIBU-KEY on 32-Bit-Windows
WIBUKE32.CPL - WIBU-KEY Control Panel Applet
WKWIN.DLL - Calling driver for 16 bit applications (if required)
WKDOS.EXE - Driver for DOS applications (if required)

Important: The system DLL shlwapi.dll must be installed on NT4. This is guaranteed if a Microsoft Internet Explorer version 4.0 or higher is installed.
Alternatively you can download the shlwapi.dll and copy it into the directory [..\System32 ].
WIBUKEY.SYS
WKWIN32.DLL
WIBUKE32.CPL
WKWIN.DLL
WKDOS.EXE
Mac OS 8 & 9 WkMAC.LIB - This is the main Shared Library, which contains the whole WIBU-KEY API. The WkMAC.LIB will be loaded in the process space of each programm needing this library.
WkMACHandle - This is also a Shared Library, which is accessed only by the WkMAC.LIB. The WkMacHandle will be loaded only once per system.
USBWibuKeyDriver - Plug&Play-Manager of the WIBU-BOX/U (USB).
USBWibuKeyDriver2 - Plug&Play-Manager of the WIBU-BOX/RU (USB).
WkMAC.LIB
WkMACHandle
USBWibuKeyDriver
USBWibuKeyDriver2
Mac OS X WkMAC.LIB - Stub Shared Library, which is included by a CFM-Carbon compiled application to call the WIBU-KEY API routines. This file can be stored in the same directory as the protected aplication or (the recommended case) in the directory /System/Library/CFMSupport. Make sure that the WkMAC.LIB will be copied with its whole Resource Fork to this directory. (This will not be done by the comandline coman cp!!) To copy something in the /System/Library/CFMSupport directory you need root rights!
WkMACLibX.framework - Framework Bundle, which must be copied in the /System/Library/Frameworks directory.For this you need super user (root) rigths! Remember that frameworks are directories and that you have to copy all subfiles and sublinks. Here you can use the comandline comand "cp -r".
WkMAC.LIB
WkMACLibX.framework
Linux The Access and the Plug&Play functionality of
a WIBU-BOX/U is managed by a the Hotplug Script wibu_usb.sh and usb.usermap(/etc/hotplug) under Linux. So "Hotplug or Udev" system has to be installed on the Linux PC.
wibu_usb.sh
usb.usermap



Questions about the Installation process

The program will not run on Windows 2000/XP/ Vista/ 7/ Server 2003/ Server 2008.
On Windows 2000/XP/ Vista/ 7/ Server 2003/ Server 2008 the kernel driver WIBUKEY(64).SYS is required because it is not possible for a normal program to access the hardware. After the installation of the kernel driver the application should run properly.

The kernel driver cannot be installed on Windows 2000/XP/ Vista/ 7/ Server 2003/ Server 2008.
To install a kernel driver on Windows 2000/XP/ Vista/ 7/ Server 2003/ Server 2008 special user rights are required (load and start a kernel driver). By default an administrator will have these user rights.

A file cannot be installed because it is used by another process.
Before you begin to install WIBU-KEY drivers you should close all other Windows applications, especially all WIBU-KEY protected applications and the Windows Control Panel.

What kind of Linux distributions are supported?
At the moment a lot of different Linux distributions are existing. WIBU-SYSTEMS tested the WIBU-KEY drivers for the current versions of the distributions from SuSE, Red Hat, Mandrake and Debian. Depending on the Linux system there should generally be other distributions applicable. Primary important is only the version of the used Linux kernel as well as system libraries such as glibc and libstdc++. If you are not sure, please make sure that you are using the WIBU-KEY network server on a Linux distribution, which is explicit named in relation to the driver version.

    System Requirements - Linux:

  • Linux Kernel 2.4.x (or kernel 2.6.x )
  • Architektur: i386 or x86_64
  • glibc 2.3
  • stdc++ 5.0
  • stdc++ 6.0 (x86_64)
  • hotplug or udev
  • and for the WkConfiglin - Tool SunJava >= JRE 1.4 (optionally)
  • gcc 3.3.x for the WibuKey Development package (i386) (optionally)
  • gcc 4.0.x for the WibuKey Development package (i86_64) (optionally)