Difference between revisions of "Support:Licensing"
Line 33: | Line 33: | ||
* <tt>license.flic</tt> | * <tt>license.flic</tt> | ||
+ | |||
+ | A ''license.flic'' file can contain more than one license string (e.g. for different software versions) but each license string must be on a separate line. | ||
== License File Location == | == License File Location == |
Revision as of 16:54, 20 October 2014
Contents
Licensing
Requesting a License
To request a license, send a mail to Digital Vision :
With the mail, please include details :
- What product you want licensed
- Your system MAC address (see below)
- Your name, company name, address and contact details
System MAC Address
To find out your system MAC address on Windows :
- Click the Start button
- Type : cmd (and press enter)
This starts a command console. In the command console :
- Type : getmac /v > mac.txt
This creates a file mac.txt containing details of your system MAC address.
- Email us this file at the address above.
License File
Licenses are placed into a text file called :
- license.flic
A license.flic file can contain more than one license string (e.g. for different software versions) but each license string must be on a separate line.
License File Location
The license file is expected to be in a folder as given by the environment variable :
NUCODA_LICENSE_DIR | For Nucoda products
e.g. C:\Nucoda\License |
PHOENIX_LICENSE_DIR | For Phoenix products
e.g. C:\Phoenix\License |
LOKI_LICENSE_DIR | For Loki products
e.g. C:\Loki\License |
BIFROST_LICENSE_DIR | For Bifrost products
e.g. C:\BifrostQC\License |
Version 2010.0 and earlier
For version 2010.0 and before, the environment variable is DV_LICENSE_DIR. This will probably be set to C:\Digital Vision\License.
Troubleshooting
Follow these steps if you are having problems getting your license to work :
1. | To find the license file, we look in a foldfer given by an environment variable (based on product) e.g.
For Nucoda (as an example), this would be set as :
and we expect the license file to be called license.flic in the above location. |
2. | Make sure that the environment variable (e.g. NUCODA_LICENSE_DIR has no odd spaces (e.g. at start or end).
As an example, the following would be wrong :
|
3. | The license file is called license.flic.
Make sure that there are no hidden extension (e.g. .txt). In a file browser, check : Tools / Folder options / View tab / Hide extensions for known file types (un-check) |
4. | Make sure the license.flic file is the only .flic file in the folder. We check all .flic files in alphabetical order. |
5. | Make sure the date and time is correct on your computer. Never put the computer clock back! |
6. | Make sure that the system ID (MAC) in the license string (third field e.g. 003048671219) is correct for the machine you run on. |
7. | The system ID (MAC) must be on an active network interface i.e. it must not be disabled. |
8. | Make sure that the license string is in the license.flic file on one line only (a single line per license string) |
9. | If the license string has been given to you split over 2 lines with a "\" line continuation character used - delete it when placing the string on a single line i.e.
FilmMaster 3.6 001F294EAEBC 12-Aug-2009 14 \ Avid Enh Res Conv 89D82D4CD40EA4234668 Should be : FilmMaster 3.6 001F294EAEBC 12-Aug-2009 14 Avid Enh Res Conv 89D82D4CD40EA4234668 |
10. | Make sure that the version of software you have installed and are running matches the version in the license (second field e.g. 2014.1) |
11. | We read the license.flic file from top to bottom and choose the first valid license. If this is an old license, we will use it, and you may still get expiration warnings. Make sure any new license line is before old ones. |
12. | The license file has format :
where :
So make sure that DATE + DAYS is a within your active period (license is not expired). |
13. | Make sure you are running the correct application, as specified in the license file i.e. run "Phoenix Finish" when the license.flic file specifies "PhoenixFinish" as the product name. |
14. | Some virtualisation products (e.g. vmware, virtualbox) can interfere with the network devices we try and attach to. If you have such software installed, try disabling or uninstalling it. |