|
||
You can limit the evaluation period
There are 2 different options to limit a module
•Number of days after first usage and/or
•Final expiry date (Valid until day)
If you specify number of days and an expiry date, then the event which happens first, is used.
Example
Expiry date is 10.10.2008, number of days is 10
•First program start is June 5th - program would expire after 10 days on June 15th
•Frist program start is October 5th - program would expire after 5 days on October 10th
Time limitation starts not with installing the program or with opening the license file - it starts with the first usage of the Validate / PrepareAndCheck call for a module.
This allows to start the time limitation for each module separately. Example:
You have 2 modules. Both modules have a trial period of 30 days.
If module A is first used on 01.01.2007, then module A expires at 30.1.2007. If module B is first used on 10.01.2007 then only module B expires at 10.02.2007.
|
The evaluation version allows to start the application for a specific time without registration. During each program start, the days left for evaluation are displayed.
The following evaluation options are possible •Limit number of days after first program start •Limit until a specified expiry date •Just display the evaluation screen to register but always allow a program start (evaluation without time limitation) •No evaluation version - Serial Number is mandatory •Limit number of program starts •The evaluation version cannot be activated. Full version requires a new installation package
Example
Evaluation time is 30 days. After 10 days of testing the application, the user uninstalls it and then reinstalls the application. The Start Screen would now display There are 20 days left because Licence Protector detects, that the application was already installed.
If the user would install the application 2 months later because he makes a new download, then the application would instantly show the screen Evaluation Period Expired. This is due to the fact that Licence Protector calculates during the initial installation an final expiry date and the application will never run beyond this date even after an reinstallation.
The evaluation option is available for each module and each module can have a different evaluation time.
Example •Module A has a time limitation with 20 days •Module B has a time limitation with 10 days •Module C expires at 01.01.2009
|
The demo version of Licence Protector always sets an expiry date of 10 days