To top
Support & Downloads Support & Downloads

Frequently Asked Questions

Share:

Hardware

  •  

    The Firm Key cannot be read directly from a Firm Security Box (FSB) or the Firm Code.

    In order to compare it between 2 FSBs, a public key of the corresponding entry can be created and compared with other public keys.

     

    These public keys must be identical for all FSBs that have the same Firm Code.

     

    To create a required public key, proceed as follows:

    1. Call core API function CmAccess2() and execute an entry access to 99:<Your Firm Code>.

    2. Create a public key with this access (handle) together with the function CmGetPublicKey() and use the Secret Data data field type 128.

     

    The above steps can also be done with CodeMeter API Guide.

    You open this tool via the system menu "Start | All Programs | CodeMeter | Tools".

  •  

    If a CmDongle is connected and can be displayed and read in CodeMeter Control Center, it can usually be assumed that it is working.

    A defect of a CmDongle is already apparent when connecting. In CodeMeter Control Center on the register "Events" you can see entries which show errors and describe them in more detail.

     

    However, an error is not necessarily caused by a defect in the CmDongle, but is often due to the USB communication, i.e. the USB port, USB hub or USB driver used.

    Further information can be found in KB-0201.

    In these cases you should try the CmDongle on other systems. If the CmDongle does not work on another system, a defect is more likely.

  •  

    Which mode is to be used can be set via the Windows registry and the UseUmsDA key.

    Proceed as follows to open the registry:

    - Press the key combination [Windows] + [R] to open the dialog

    "Execute".

    - Enter the command regedit and confirm with [Enter].

    - Searching for the value

    [HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\CodeMeter\Server\CurrentVersion].

     

    If the parameter UseUmsDA is set to a value of 0, FileIO mode is activated; if it is set to a value of 1, PassThrough mode (default) is activated.

    Please note that if there are no sufficient rights for UseUmsDA=1, CodeMeter automatically switches to FileIO mode.

     

    Usually the reason is that CodeMeter does not run as a service and therefore does not have sufficient rights to communicate with the CmDongle in PassThrough mode. Therefore the solution is to simply start the CodeMeter service.

     

    Alternatively the firmware update of the CmDongles can be run on another system where CodeMeter was installed as service by default.

     

    You can find out which mode is currently used from the CodeMeter Event Log. When CodeMeter is started, the last line is displayed:

    Box Access: use direct access mode. corresponds to PassThrough mode

    or

    Box Access: use compatibility access mode. corresponds to the FileIO mode

  •  

    The information you are looking for is stored in the Extended Protected Data field 131 of the license entry 0:0.

    Enclosed you will find a code snippet (C++) that reads the information and interprets it accordingly.

     

    You can execute this code snippet by using the CmDemo C++ example from the CodeMeter Software Development Kit (Start | Programs | CodeMeter | Samples) and replacing the method MyCode() there.

    After starting the program you can select the CmContainer and then use Run MyCode to display the hardware type.

  •  

    The VendorID (VID) is an identifier assigned by the USB Implementers Forum for companies that manufacture USB devices. The assigned VID is only assigned once and cannot be changed. All CmDongle produced by Wibu Systems AG therefore have the defined VendorID 064F.

     

    However, if you are looking for the ProductID of your CmDongle, please proceed as follows:

    1) Open the document "USB Products, VID and PID".

    2) Search the CmDongle for the USB product number. This can be found on the CmDongle housing, e.g. 1001-01-100.

    3) Search the list for the corresponding product number and find the corresponding PID.