String value with maximal length of 40 characters which describes your program (for example: "Text editor PRO V4.0").
Protected application will use this information as window title when interacting with end user.
Application signature uniquely identifies project files and thus protected application on remote computer. Applications protected with same application signature will share the same license information on remote computers.
It can be any string value with minimal length of 6 and maximal length of 10 characters.
For example, if you have application named "Text editor PRO V4.0" your application signature could be "TEEDPROV40".
Application signature enables installation of application updates without entering new (or original) activation code again (both original application and update should share the same application signature).
It also enables sharing of license information between a group of applications. For example, a group of applications can be activated with just single activation code and in this case all applications should share the same application signature.
Machine ID (MID) code is also based on application signature. In this way activation codes can be generated for applications protected with appropriate project only. If wrong project is loaded MID code decryption error will be reported.
If you are distributing free updates for your application use same project settings (including Application signature) as for original application. New update will be automatically unlocked in this case.
If your are distributing non-free updates for your application you can change Application signature and new update will generate different Site/MID code. You can also consider using different Program ID for such updates.Use updates policy feature to manage application updates.
Be sure to use same Program ID for applications with same Application signature. If you have two applications with same application signature and different Program ID running on same computer one of them will be wrongly decrypted and will display "File damaged!" error message. Both applications will share same license data including Program ID (encryption key) and this is why one of them will be wrongly decrypted.
In order to test different protection scenarios you need to use different application signature for each strategy in order to avoid possible conflicts when experimenting with different project settings. You can use special application signature values for each test build like TEST0001, TEST0002, TEST0003 and so on.
Update ID option
Application Update ID is used for identifying application updates.
It can be set to any number from 0 to 999999. Default value is 0 and should be increased with each update (higher value = newer update).
This option will affect the following options/features:
- Reset demo mode for this update option.
- Erase previous license option.
- Reset previous counters option.
- Reset previous user information option.
Full path to application to be protected. Use '...' button to browse for application.
Note: This field can be set directly from command line by using -FILE command line option (see command line interface for more information).
If application backup is enabled backup copy of original application will be created before protection process starts.
Backup original application option.
Set this option to enable application backup. Default status: ON
Set full path to backup filename here. This field can be left empty. In this case default backup with _OLD extension will be created.
Full path to output application filename. If left empty, protection will be applied to original application.
This field can be set from command line by using -OUTPUT command line option (see command line interface for more information).
There are three buttons above output filename field.
"/" button will open target output directory in Windows explorer.
"I" button will copy interface dll to output directory.
">" button will run output application.