LM-X License Manager does not provide executable code protection against reverse engineering and accidental or deliberate tampering with the executable content. If you want to use software that provides protection from reverse engineering, you will need to use a third party solution.
Please note that LM-X License Manager allows you to perform a clock check on the client side to ensure users have not backdated or tampered with their system clock.
For more information about protection against time tampering, see System clock check.
Activating your license using License Activation Center is simple:
LM-X License Manager supports Java.
On top of Sentinel HASP HL Pro dongles available at X-Formation for some time, now you can also buy 2 GB Flash driverless Sentinel HASP Max dongles.
For more information about downloading the latest Sentinel HASP drivers, go to End User Tools Downloads. You can also visit our blog to learn more about driverless Flash Sentinel HASP Max dongles.
Note: If an LM-X dongle is plugged into a machine that does not have the dongle drivers installed, the Windows "Found New Hardware" dialog will appear. You can follow the prompts in this dialog to install the drivers using Windows update.
You may also download the dongle drivers attached to the bottom of this article. If desired, software vendors can ship the drivers to customers along with the dongle.
X-Formation products are designed to get you up and running quickly without a lengthy and complicated installation process or lots of documentation to go through.
See LM-X License Manager Quick Start for instructions on how to get started with LM-X.
If you see the error "LMX_BAD_SECURITY_CONFIG" during checkout, you may have multiple security configuration files (security_config.lmx). The license may be using one security configuration file, while the application is using a different security configuration file. Both the license and application must use the same security configuration file.
To resolve the problem:
To download the latest version of LM-X, to the LM-X License Manager download page.
See LM-X License Manager Quick Start for more details.
When software vendors upgrade to a new LM-X License Manager release, their end users must also upgrade their LM-X license server. If they don't do this, the new server will not work with existing licenses.
See Version compatibility for more compatibility-specific information.
With Amazon EC2, you can use the Instance ID for the HostID (see HostID values). However, for other cloud service providers, such as Microsoft Azure, virtual machines do not have HostIDs.
See Licensing for virtual machines and cloud computing for further information on licensing software for cloud applications.
You may see the following error message when attempting to compile the LM-X distribution using Visual Studio Express Edition:
'devenv' is not recognized as an internal or external command, operable program or batch file.
This error is due to different file names in Visual Studio versus Visual Studio Express. The file devenv.exe is the name of the IDE executable for Visual Studio editions. For Visual Studio Express editions, each IDE executable has a different name, specifically: Visual C++ 2005/2008/2010 Express Edition - vcexpress.exe.
To solve this problem, copy the attached batch file (scroll down for attachment), devenv.bat, to a location such as C:\Windows where it will be added to the system path and recognized from the command line. LM-X will then compile normally.