|
|
Check for System Date modification |
|
|
|
|
||
Check for System Date modification |
|
|
|
|
|
|
|
Check for System Date modification |
|
|
|
|
||
Check for System Date modification |
|
|
|
|
|
|
|
||
Enables checking, if the system date is modified back more than 1 day. See error screen - System date was tampered
This option will stop the application if the date was turned back.
|
To unlock the system date lock, you can use any Activation Key - e.g. a key which sets demo version to true or a key without any settings. To open the license file despite the error message, use PrepareForce and then open the License Viewer so that the user can type in a key. The command PrepareAndCheck will offer the License Viewer by default.
If your application is in evaluation mode and the application is uninstalled and then reinstalled, this is automatically detected. The application will have the same number of days left like before the uninstall process. CheckSysdateChanged is an additional test to the test in evaluation mode.
If you want to control that the system date check is only done when the version is in evaluation mode, you need additional checks.
Do not use CheckSysdateChanged. Instead use this test sequence
•After the main license check with PrepareAndCheck test your main module if it is in evaluation mode or a demo version •Check demo version: ValidateEx •Check time limited mode: NoOfDays •Only if the version is a demo version or NoOfDays is >0 then check if the System Date was modified with SysDateChanged •This command gives you full control to decide if you want to continue or not. In case the system date was changed and you do not want to continue display an error page with ShowStartErrorPage using error number 16382 (which will display this page) or display your own error message
|
See also
How to unlock system date lock?
