Installing Individual Licenses
The software license is supplied in a file called appname.lic. It usually arrives by email, as
an attachment which can be extracted or saved to the appropriate location. In some cases (for example
at a site which has purchased multiple node-locked licenses) the individual license file will have been
supplied by your network support or administrator. The file should still be saved in the same fashion.
Next time you start the software it will automatically locate the license file and use that.
License File Location
When searching for a license key the software will check the following locations:
- C:\Program Files\Common Files\VSN International\Licenses.
- C:\Program Files\appdir\Bin
The first location is preferred as it will simplify installation of software updates in the future. When
you install a new version it will find the key in "Common Files" and run immediately, if still valid.
If you are unable to access "Common Files" you can instead put the license file in the application Bin
folder, e.g. C:\Program Files\Gen9ed\Bin, as selected during installation.
Note that non-English versions of Windows may use alternative names for the Program Files or Common Files folders
and you should substitute these as appropriate in the above examples.
Finally, in case you cannot access the attachment in your mail the license text is also repeated at the end of this
message.
Environment Names
If the license software does not find a valid license key in either of the locations listed above it will also
check some environment names to see if they have been set. These are principally intended for network installations
and their use is not recommended for individual copies of the software. However, for reference purposes, they are listed here:
- appname_LICENSE_FILE, where appname is set appropriately, e.g. GENSTAT_LICENSE_FILE, ASREML_LICENSE_FILE, SAMM_LICENSE_FILE.
- VSN_LICENSE_FILE
can be used where licenses for a number of products are held in one license file.
- LM_LICENSE_FILE is a legacy setting that is still recognized, for compatibility with older versions, but is
not recommended for new installations.
Usually the license file will be stored at a convenient location and the chosen variable set to the appropriate pathname.