Choose Implementation

The following implementations set guidelines how the protected application can be licensed and used by the end-user. They also enable related options for the protected application such as limits and messages that the application uses to communicate with the end-user.

Custom

You customize how the protected application is licensed, as well as messages that the application uses to communicate with the end-user.

 

The followings describe how the end-user uses the application:

 

         The end-user must first register with you and request a License Key.

         When receiving the Registration ID, you generate the License Key using the Custom implementation. It allows you to customize all limits in Key Properties.

         Once the end-user applies the License Key, the application operates under the given license.

Distribution

The protected application is distributed as a full version, or for sale. The end-user is granted a license to use the application without restriction.

 

The followings describe how the end-user uses the application:

 

         The end-user must fist register with you and request a License Key.

         When receiving the Registration ID, you generate the License Key using the Distribution implementation, which has no limit on Key Properties.

         Once the end-user applies the License Key, the application operates without restriction.

Leasing

The protected application is for lease in which the end-user is granted a license to use the application for a period of time. The lease is renewable. The application displays the Registration dialog box for renewal whenever the lease expires.

 

The followings describe how the end-user uses the application:

 

         The end-user must first register with you and request a License Key.

         When receiving the Registration ID, you generate the License Key using the Leasing implementation, in which you can specify a time limit.

         Once the end-user applies the License Key, the application can operate for the defined time period.

         When the lease expires, the end-user must register with you again for renewal.

Evaluation

The protected application is distributed as an evaluation version. The end-user is granted a license to use the application for a trial period, such as 30 days. The application displays the Registration dialog box every time it is run. The end-user can choose to continue evaluation or register for the full version. The Evaluation implementation is available in 2 modes: Secure and General.

 

The followings describe how the end-user uses the application distributed in the Custom/Secure Evaluation mode:

 

         The end-user must first register with you and request a License Key.

         When receiving the Registration ID, you generate the License Key using the Evaluation implementation. It allows you to set limits for evaluation, such as a 30-day period, or the number of executions.

         Once the end-user applies the License Key, the application operates under the evaluation license.

         If the end-user decides to use the application after the evaluation, he must register again and request a new License Key.

         When receiving the Registration ID, you may grant a new license to the end-user using any implementation such as Distribution, Leasing, and Re-evaluation.

         Once the end-user applies the License Key, the application operates under the new license.

 

The followings describe how the end-user uses the application distributed in the General Evaluation mode:

 

         The end-user can run the application without registration as long as the trial period has not expired.

         If the end-user decides to use the application after the evaluation, he must register with you and request a License Key.

         When receiving the Registration ID, you may grant a new license to the end-user using any implementation such as Distribution, Leasing, and Re-evaluation.

         Once the end-user applies the License Key, the application operates under the new license.

Shareware

The Shareware implementation is different from others. It follows the concept of shareware distribution. The Registration ID is generated based on the end-userís name and organization/company name. If the end-user uses the same name and organization name on different PCs, this gives the same Registration ID. Thus, the end-user can apply the same License Key and run the application on different PCs. Nevertheless, this is illegal! In this case, the granted license is only enforced by the license agreement stating that the application must be used on a single PC.

 

noteNOTE: All other implementations, except the Shareware, use the randomly generated registration ID. This causes a different Registration ID every time the end-user runs the application on a new PC. Therefore, the granted license is enforced in which the end-user cannot apply the same License Key on different PCs. Note that the end-user can use the application on different PCs only by transferring the Harddisk Key to those PCs.

 

The application protected as a shareware grants the end-user a license to use the application for a trial period. The application displays the Registration dialog box every time it is run. The dialog box also requires the end-userís name and organization for registration. The end-user can choose to continue evaluation or register for the full version.

 

The followings describe how the end-user uses the application:

 

         The end-user can run the application without registration as long as the trial period has not expired.

         If the end-user decides to use the application after the evaluation, he must fill in his name and organization for a Registration ID. Then, request a License Key from you.

         When receiving the Registration ID, you may grant a new license to the end-user using any implementation such as Distribution, Leasing, and Re-evaluation.

         Once the end-user applies the License Key, the application operates under the new license.

The following implementations set guidelines how the protected application can be licensed and used by the end-user. They also enable related options for the protected application such as limits and messages that the application uses to communicate with the end-user.