SecureEngine contains lots of internal options mostly related to compatibility issues with specific applications. These options are not public available as they will confuse developers if we display all current available options, which are not related to security and hardly used by most applications. Developers will feel confuse (and unsecure) if they see lots of options and he is not using them in their applications.
When there is a special compatibility issue in a specific application when applying our protection, we send the required special option to the customer so he can use it for that application. In order to add a new advanced option, just right-click on the Advanced Options panel and select Add.
Here we have a small list of advanced options that you can use if you consider:
▪OPTION_ADVANCED_IS_MULTICORE_PROTECTION: You can set this option to NO in case that you want to use a single core to protect your application. By default multicore protection is enabled
▪OPTION_ADVANCED_SECTION_NAME: You can set the section name (PE header) that will be appended to your protected application
▪OPTION_ADVANCED_USB_RUNTIME_CHECK_SECONDS: You can change the number of seconds that a USB drive is checked in case that you have locked your license to a USD drive ID and you have selected the option Detect unplug in the Hardware Lock panel. The internal default value is 30
▪OPTION_ADVANCED_NETWORK_INSTANCES_DEFAULT_PORT: (for Network Instances) You can set the default port when working with Network Instances (floating licenses). The default value is 5000
▪OPTION_ADVANCED_NETWORK_INSTANCES_LIVE_TIMEOUT: (for Network Instances) This value should be increased for heavy loaded networks (or very long distant communication) to increase the internal timeout to give some extra time for packets to arrive. The default value is 4000 (4 seconds)
▪OPTION_ADVANCED_NETWORK_INSTANCES_COUNT_BY_COMPUTERS: (for Network Instances) If set to YES, this option will count one instance per computer, no matter if the user has launched several instances on the same computer.
▪OPTION_ADVANCED_NETWORK_INSTANCES_NO_SERVER_INSTANCE: (for Network Instances) If set to YES, this option will not create an instance in the server. This means that the application on the server will stay on memory just waiting for clients to be connected, but your application code won't be executed.
▪OPTION_ADVANCED_NETWORK_INSTANCES_DEFAULT_IP: (for Network Instances) You can set the default IP address that will be used by the protected application. A typical usage is to use the localhost IP address 127.0.0.1
▪OPTION_ADVANCED_NETWORK_INSTANCES_ON_LOCAL_HOST: (for Network Instances) You can set this option to YES if you want to restrict the network instances feature to work only on a single computer. This is suitable if you want to restrict the number of instances of your application on a single machine
▪OPTION_TRIAL_IS_DEBUG_MODE: You can set this option to YES and the trial counters and status will be stored under the Registry key: HKEY_CURRENT_USER/SOFTWARE/WinLicense/WLdebugTrial/Instance. If you are doing tests on your development machine, it's better to use this option, so you can easily delete all the stored information in the Windows Registry, so the trial will be reset. When you are going to release your application, you should remove this option or set it to NO.
▪OPTION_ADVANCED_KEEP_DEBUG_INFO: You can set this option to YES to keep the debug information in your protected application. This option is recommended if you want to debug crash dumps (.dmp)
▪OPTION_ADVANCED_LAUNCH_APP_WHEN_TRIAL_EXPIRED: When the trial is expired/manipulated, you can launch an external application before your application starts. You can also set a link to launch the default browser. Example:
▪Launch an application:
OPTION_ADVANCED_LAUNCH_APP_WHEN_TRIAL_EXPIRED=%APP_FOLDER%\MyExternalApplicaiton.exe
▪Launch a web linkk:
OPTION_ADVANCED_LAUNCH_APP_WHEN_TRIAL_EXPIRED=start www.yourweb.com