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

WIBU-SYSTEMS Knowledge Base

The WIBU-KEY Knowledge Base is an expanding list of solutions for problems with WIBU-KEY. In the following, freqently asked questions are discussed.



My WIBU-BOX/U is not recognized by the hotplug mechanism on SuSe Linux 10.1. Why?

After PlugIn, the WIBU-BOX/U can not find the needed drivers.

Why is the LPT-Port not deteced by the WIBU-KEY drivers on my Linux PC?

If I try to program a WIBU-BOX with WkList32, the Firmcode selection field is greyed out.

The error message WK 1201 (21), if I try to program a new WIBU-BOX.

A WIBU-BOX/U-/RU does not work (or only partly) when connected to a Mac keyboard

A WIBU-BOX/P, SP, ST can not be found anymore after updating of the drivers or reinstallation

A WIBU-BOX/P sporadically displays the errors WK1202[8], or[7] or can not be recognized despite correctly installed drivers

After having installed the Java version 1.4.1 for Mac OS X the file libwibuKJni.jnilib can not be found anymore

After having updated the WIBU-KEY Development Kit only Firm Code 10 can be programmed into the WIBU-BOX

Error message: "Error when realizing transforms"

Error message when installing the WIBU-KEY Development Kit: Registration of module ..\DevKit\Bin\WKFirm.dll failed

AWARD CardWare - Problems with virtual drives

WIBU-KEY and ZIP-Drives

WIBU-KEY and UPS (Uninterruptable Power Supply)




My WIBU-BOX/U is not recognized by the hotplug mechanism on SuSe Linux 10.1. Why?
Problem: On SuSe 10.1 the hotplug mechanism is per default configured not to recognize mass storage devices automatically. You can change this default behaviour by changing the fstab to enable the automatic detection again. Please do the following:
Solution: Use the WibuKey driver version >= 5.20, this versions contain a internal handling for this problem.
Or:
Edit with root rights the file /etc/fstab
Replace the line:
usbfs /proc/bus/usb usbfs noauto 0 0
by
usbfs /proc/bus/usb usbfs auto 0 0
Reboot your system.

After PlugIn, the WIBU-BOX/U can not find the needed drivers.
Problem: If you first plugIn a WIBU-BOX/U to a "new" USB-port, the Hardware wizard is searching for the needed installation file (wibukey.inf)
Solution: The hardware wizard search for the file wibukey.inf. This file is normaly installed in the directory (%systenroote%\inf). Please check this directory for the file wibukey.inf. If the file can not be found, please search on the system for the wibukey.inf file. Espacualy if you have installed the drivers via a terminal session, the wibukey.inf is may be stored in a wrong folder.

Why is the LPT-Port not deteced by the WIBU-KEY drivers on my Linux PC?
Problem: After the WIBU-KEY driver installation the LPT-port is deactivated by default.
Solution: Activate the LPT-port. Please have a look at "Problems with localy connected WIBU-BOXes."

If I try to program a WIBU-BOX with WkList32, the Firmcode selection field is greyed out.
Problem: You try to program a "new genaration" WIBU-BOX with an "old" WIBU-KEY License file (wkfirm.wbc oder wkfirm.dat).
Solution: You need to perform a license update:
For this please send your WIBU-KEY license file "wkfirm.wbc" oder "wkfirm.dat" [.\wibukey\devkit\bin] to license@wibu.com.
We will send you a new (updated) license file (version 4) as soon as possible.

The error message WK 1201 (21), if I try to program a new WIBU-BOX.
Problem: The programing signature for the WIBU-BOX is wrong because you are using a "old" (version 4.10 or older)of our WIBU-KEY Development-Kit.
Solution: Install the current version of our WIBU-KEY Development-Kit (Version >U 5.0). With this version you can program all variants of WIBU-BOXes.

A WIBU-BOX/U-/RU does not work (or only partly) when connected to a Mac keyboard
Problem: According to Apple this is a known problem of the integrated "bus powered keyboard hub".
For more details please see: http://docs.info.apple.com/article.html?artnum=58649.
Solution: Use a free USB interface of your Apple PC or use the WIBU-BOX on a USB hub connected to this interface.

A WIBU-BOX/P, SP, ST can not be found anymore after updating of the drivers or reinstallation
Problem: When installing, the interface communication settings are reset to default, if not otherwise required.
Solution: Check on page Setup of our WIBU-KEY control panel applet (Start - Settings - Control Panel - WIBU-KEY) if the concerning interface is activated.
If necessary, check then the address area under "Location". The address should correspond with the interface. You can check this in the Device Manager of your system.

A WIBU-BOX/P sporadically displays the errors WK1202[8], or[7] or can not be recognized despite correctly installed drivers
Problem: Some notebooks and "newer" PCs don't supply the LPT interface with enough power. This can cause a Timeout problem.
Solution:A Timeout occurs when the WIBU-KEY driver can not access the WIBU-BOX within the expectated time interval. The time interval can be increased by using a so-called DelayFactor. The DelayFactor is a normal registry extension.

Syntax:

[HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\WIBU-KEY\Driver\CurrentVersion]
"DelayFactor"="4"

Here you can download a zip archive containing various Delayfactors: DelayFactor.zip.

The Delayfactor can be activated by double clicking. After having changed the DelayFactors enter the command [..\wibukey\bin] wku32.exe reset all or restart your PC. Only this way it is guaranteed that all WIBU-KEY specific registry entries will be reread.

Note: For the first time try always a slow DelayFactor (such as 4), because it influences the WIBU-KEY processes and can therefore slow down the protected application.

After having installed the Java version 1.4.1 for Mac OS X the file libwibuKJni.jnilib can not be found anymore
Problem: The newest Java versions don't use the directory user/lib in the library search path anymore.
Solution: Use our WIBU-KEY driver version 3.31 or higher (WibuKey.dmg). These versions contain the appropriate installation paths.
You also can copy the file libwibuKJni.jnilib into the system directory
[/System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Libraries] or into the directory
[/Library/Java/Extensions] in order to use a system directory valid for all Java versions.

After having updated the WIBU-KEY Development Kit only Firm Code 10 can be programmed into the WIBU-BOX
Problem: Your firm license file wkfirm.wbc or wkfirm.dat has been overwritten.
Solution: Copy your firm license file (disk) wkfirm.wbc or wkfirm.dat into the directory
[..\WIBUKEY\Devkit\bin]

Error message: "Error when realizing transforms"
Problem: When installing the German Development Kit (SetupDE.exe) this error message is displayed if in the Regional Options the location is not set to Deutsch(Deutschland), but to "Deutsch(Österreich)" oder "Deutsch(Schweiz)".
Solution: Set the location to Deutsch(Deutschland) during the installation. After the installation you can change again the location to the required setting.

Error message when installing the WIBU-KEY Development Kit: Registration of module ..\DevKit\Bin\WKFirm.dll failed
Problem: TheWIBU-KEY Development Kit can only be installed if the WIBU-KEY drivers (Runtime Kit) already have been installed.
Solution: Install a WIBU-KEY Development Kit > 4.0 or install always the WIBU-KEY Runtime Kit before installing the Development Kit.

AWARD CardWare - Problems with virtual drives
Problem: If you install the AWARD CardWare software via the Express Setup it will also install drivers for ATA-, Flash- and SRAM-PCMCIA cards. The Windows Explorer displays these as additional virtual drives. Some applications that scan all drives and even the Explorer itself may report errors when they try to access these virtual drives.
Reason: It results from a bug in AWARD CardWare, or from wrong error handling with non existing PCMCIA cards.
Solution: Install CardWare using only the Custom Setup and deselect the other devices or use the devices control panel applet to disable the kernel drivers PCATA.SYS, PCDISK.SYS, PCSRAM.SYS and PCFLASH.SYS.

WIBU-KEY and ZIP-Drives
Problem: The WIBU-BOX/P is not detected when attached between the PC and a parallel ZIP-Drive. Sometimes the ZIP-Drive will also not function.
Reason: Iomega uses a proprietary protocol to communicate with the ZIP-Drive the WIBU-BOX cannot be accessed or is jamming this communication.
Solution: Simply attach the WIBU-BOX to the parallel port at the ZIP-Drive. Our customers have reported that this works without any problems.

WIBU-KEY and UPS (Uninterruptable Power Supply)
Problem: UPS (Uninterruptable Power Supply) is a piece of hardware connected to the serial port, which is supposed to protect the station from power failure. Starting the CPL, the wksvnw.nlm or other WIBU-KEY software, which first scans all ports, results in an error function in the power chute.
Reason: This happens because our drivers have general access to the serial port or because the Scan button in the CPL/WkLIST has been pushed.
Solution: Disable the port to which the UPS is connected. This can be done in the CPL on page Setup or in the wibukey.ini (wksvnw.nlm, e.g. WkCom=/D,*,*,*, if the power chute is connected to the COM1). In the current driver version the serial interfaces are deactivated as default.