There are three ways for customizing dialogs:

1) Basic: You can change default text messages in language editor.

2) Custom dialogs: You can create completely customized dialog resources for all dialogs used for interaction with end user including activation dialog. Your custom dialogs will be loaded from your application (.exe/.dll) with dialog resources and displayed instead of default dialogs. Our protection code embedded into protected application will still provide dialog handlers code.

Sample MS Visual Studio Win32 DLL C++ project with default dialogs is included in full featured version.

3) Full control. If you are looking into completely controlling the way dialogs are displayed and managed you need to use advanced protection interface functions with your dialogs:

- Enable demo mode together with date or exec limitation.

- Set "Protected application will handle expired demo option" option.

- Set "Protected application will handle license management" option to manage license removal, update or license transfer from your code.

- Set "Protected application will handle expired license" option to manage expired limited license from your code.

Protection code will only mark protected application as expired and pass control to protected application.

Protected application will be responsible for handling license management by using advanced protection interface functions.

For example, you can display your own activation dialog and unlock protected application by calling UnlockApplication() protection interface function.

NOTES:

- .NET applications should use alternate protection interface implementation or let another Windows application protected with same settings manage licensing tasks.

- Protection interface documentation together with source code examples is included in full featured version and can be accessed from Help menu.