I guess because of these issues, WIBU systems implemented a new approach, the HID or _h_uman _i_nterface _d_evice mode in which the CodeMeter dongle acts as a human interface device (like mouse or keyboard). The trashcan issues should also be resolved by switching to removable disc mode, however Microsoft also provides a patch for Windows 7 that fixes this bug:
After that you should not be bothered any more by warnings about this particular dongle.
Where xxxxxxx needs to be replaced with the proper serial number.
Once you know the serial number of your dongle, open a CodeMeter Command Prompt from your start menu and enter the commandĬmu32 -s 2-xxxxxxx -set-config-disk RemovableDisk These numbers have the format 2-xxxxxxx or 3-xxxxxxx. To do that, you will need to know the serial number of the dongle - this is not the CVB serial number, but the one lasered on the USB plug and visible in the CodeMeter Control Center.
To get rid of the low disk space warnings, you can modify the behavior of the CodeMeter dongle so that it presents itself to the operating system as a removable disc (for which the low disc space warning will not be shown). (Click arrow to see a remedy for these issues) However, the mass storage device can have undesirable side effects: Some versions of Windows repeatedly pop up a low disc space warning when a CodeMeter dongle with 0 bytes free is attached, and on some versions of Windows 7 the presence of a CodeMeter dongle with 0 bytes free can disrupt the operation of the system’s trashcan (to be more precise: The trashcan continues to work, but the contents are no longer visible). This system of the dongle doubling as a regular USB flash drive is very elegant in that it does - unlike previously used devices - not require a system driver to be installed on the machine, making the installation less intrusive and easier to author. In the case of the dongles this drive invariable has 0 bytes free memory, but if you enable the display of hidden and system files you can actually see pseudo file system entries behind which the IC with the license information listens and responds to the queries of the CodeMeter runtime. Originally the WIBU CodeMeter dongle always mimicked as a mass storage device: If you plugged one of them in it would take a few seconds and a new drive named “CodeMeter” appeared in the Windows Explorer (or whatever other file browser you are using) under the next available drive letter. The issue that describes seems to match something that WIBU Systems introduced with the 5.x CodeMeter runtime versions. I hope that helps (I also hope that is the issue…)Īllow me to add a few (admittedly only semi-interesting) details to the discussion… This has implications only for the detection of the hardware dongles, so once they are detected, any CVB licences that are on the dongle will be visible to CVB.
However installing a newer version of the Codemeter runtime will give you backward compatibility for the 2xxxxxx dongles as well as the 3xxxxxx dongles.Ĭodemeter runtime is not listed as a separate program to uninstall in Window, but you can install a newer version over the top. The Codemeter runtime (including the Codemeter Control Centre) had no knowledge of the future hardware version, so it is simply not detected. New dongles (at the time of writing) have serial number 3xxxxxx, indicating a newer security chip. This indicates the security chip version. This number can be found at the base of the USB plug.
When this version was current, the Codemeter dongles had serial numbers starting 2xxxxxx. You are using the WIBU Codemeter dongles with CVB 2011. There is one quite likely explanation with a straightforward fix.