|
AVLock Gold v5 has changed substantially. Mostly of properties has been removed from the Object Inpector. A new utility; AVLockManager was added allowing to centralize all tasks implicated in the process of administrate your applications and the security level has been highly improved.
|
 New in v5.4.
| · | In order to make it compatible with Windows Vista I changed the features to acquire the sources for the Installcode value so now the machine IDs from the Bios, the Processor and the Hard Disk are retrieved using the Windows extensions WMI (Windows Management Instrumentation). This extensions come included into Win Vista, Win XP and Win 2000 but must be installed in prior versions like Win 98 and Win Me. You can download it from Microsoft. So, if you are using AVLockGold v5.3 and upgrade to this new version 5.4 then the installcodes for your customers will be different than the previous version and they will need to register again your application. |
New features in v5.3.
| · | The InstallCode has been extended to 13 characters length in order to hold information about the machine numbers CPU ID and HD SN, so when the user ask for an new registration key affirming that your machine was damaged, then you are able to determine if the new installCode received from the user come from the same computer or not and which part of the machine was changed. |
| · | In the user form in the AVLockManager utility has been added a new feature "InstallCode report", so when you receive a new InstallCode you can see a comparative report displaying old and new values for the CPU ID and HD SN. |
| · | In the Users & Keys tabsheet in the AVLockManager utility has been added a new feature "Verify moved keys", for the special cases when the user moved the registration keys to another machine one or more times and then the machine crashes and he ask you for a new set of keys. This feature help you to determine the authenticity of these demands. |
| · | Several events have been added in order to improve the user-component communication and enhance the component customization, especially when you define your own registration form. These events are the following: OnStartError, BeforeRegisterKey, AfterRegisterKey, AfterRegisterAll, OnRegularRegistration, OnRequestName, OnMoveReg and AfterRegMoved. See in the Demo3 program how to use them. |
| · | In the registration form, the "Another way" registration option was changed to the "Print order form" feature, so you may give to your users the option to print a registration form in order to be posted to you. |
| · | Added support for the .NET version in the AVManager utility. |
 New "MoveReg" feature added in v5.2.
| · | With this feature the final user have now the chance to translate all registration keys from one machine to another. Safely, without any posibility of misuse this feature in order to increase the number of registered machines. |
 AVLockManager centralize all administrative tasks, namely:
| · | Manage and configure the component into your application. |
| · | Run the application to evaluate the result of your settings. |
| · | Unregister the application in order to try again with another configuration. |
| · | Manage all users for each application. |
| · | Generate Keys and ship it to your users. |
 The security aspect has been highly improved.
| · | Rijndael encryption for RegKeys and all data saved in the registry and sensitive files. |
| · | The "encryptionkey" string has been added, used to generate the encryption key (128 bytes length) used with the Rijndael algorithm. In the previous version 4.x the AppID number (dword) was used to generate this key. |
| · | With the new strong encrypted avconfig.ini file, all risky configuration data has been taked out from the exe file, avoiding so possible hacking meddlings. |
 Modules management improved.
| · | In the registration form has been added the "Modules" section, so the user can see anytime the status of the modules; the registered ones and which are available to register. |
| · | Modules now have a "Module name" field asociated, more suitable than only a number as in previous versions. |
| · | Modules now have a "Moule ID" field asociated. Then, you may to change this value for a new improved version in order to disable the module and force so the user to pay again for this module. |
| · | Related to the previous point as been added the "RestartModulesAsTrial" property; if True the modules with the "ModuleID" changed initiates a trial period otherwise it becomes disabled. |
| · | The "TrialIncludeModules" property has been added to determine what to does with modules while the trial status. If True all modules are enabled while the trial period otherwise these are disabled. |
In the version 5.1 has been added the "LoadLangList" method adding so a new quite ease way to change all textual messages into the component. Please see the "How to translate AVLock Gold to any language" topic.
|
