Information on TTNCFGen
What is TTNCFGen?
TTNCFGenis a tool which requires
online activation and provides a simple way to download updates.
TTNCFGen "produces" the
TTNCFFinal files for you.
This means:
- You download (at purchase) the TTNCFGen Setup.
- You install TTNCFGen on the PC(s) where you will work with TTNCFFinal.
- You activate TTNCFGen and start to work with TTNCFFinal.
The update problem OR distributed installations!
You get your product via downloads. You copy them to one (or a number of) PC(s).
Then an update arrives. You download the files and the problems start.
Read how TTNCFGen can help you...
Is this all TTNCFGen does?
NO - TTNCFGen also enables you to brand / lock your wrapper files.
Read how this works...
Do I have to lock / brand?
No you don't. You can still distribute
TTNCFFinal runtime files with your
commercial solutions.
Only if you give your products for "free" (Shareware)
you have to brand AND lock the wrapper.
Read more about it...
You can navigate these sections with the Tabs on top of the page or with...
Next page >>
Information on TTNCFGen
The update problem OR distributed installations!
You get your product via downloads. You copy them to one (or a number of) PC(s).
Then an update arrives. You download the files and the problems start.
Where is it installed, who uses it, which PCs must get this update.......
From our support we know these issues.
Customer: Something is wrong with.....
Support: Which version are your running?
Customer: x.yy we got it 2 weeks ago.
Support: Please take a look at the application directory and check xxxx.DLL
Customer: It has version.... (the old one)
Support: ......
Most of this things occur because some "forgotten laptop" did not receive the update.
TTNCFGen stops these problems?
YES - TTNCFGen requires activation to run.
So you know exactly the number of PCs where it runs on.
The "forgotten laptop" blocks a license and you will see it, when further activation is not possible on another PC.
At this point you have to remove the license from the Laptop (you do this via this web site).
From this moment
TTNCFGen will no longer run on this Laptop and it can not produce "outdated wrapper files".
You have an enterprise license and think this means "open number of activated PCs".
You are right - but TTNCFGen also handles the updates.
So if it runs on that laptop the user will able to obtain the updates by clicking a button.
And
TTNCFGen will remember him to do so!
You can navigate these sections with the Tabs on top of the page or with...
Next page >>
Information on TTNCFGen
Use TTNCFGen to lock / brand your files
You can enter textual information which is included in the wrapper DLL's.
Later this information can be obtained from the DLL. Either via
TTNCFGen or a
TTNCFFinal function calls at runtime.
TTNCFGen enables you to lock your wrapper files.
You can tell with which EXE(s) the "produced" version of
TTNCFFinal will run.
So you can ensure that "Version XXX" runs only with "YourProduct.exe".
This prevents you from "strange wrapper version mixtures".
And it prevents "
copy buyers" from using the wrapper you paid for.
Do I have to lock / brand?
No you don't. You can still distribute
TTNCFFinal runtime files with your
commercial solutions.
Only if you give your products for free (Shareware)
you have to brand AND lock the wrapper.
Take a look at point 5 of the license agreement!
5) SHAREWARE
You may include part(s) of this software (see 3a) with (real) Shareware distributions.
The runtime restrictions of you shareware license must include the functions of the distributed PPP Components.
If it is possible these components MUST be reduced (branded / locked).
If the SOFTWARE contains possibilities to do this they must be used with all features.
This does not include Freeware (open source) distributions.
You will have to ask for permission and a special version of TTNCFFinal for such cases.
Take a look at point 6 of the license agreement!
6) FREEWARE / OPEN SOURCE
This SOFTWARE or parts of it MUST NOT be distributed as Freeware or part of Freeware.
This SOFTWARE or parts of it MUST NOT be included in Open Source distributions.
In special cases we can permit explicit written permissions for such distributions.
Take a look at the whole license agreement!