Hi All,
Runtime question.
I have a RT out that requires purchasing to unlock from demo mode.
I would like to put out a stripped down free version to release also.
I'm having trouble deciding if the two versions should use the same
bind key or not for the RT app.
The paid version needs a key code for access so that's not really an
issue.
I'm more concerned about what happens when multiple runtime apps are
installed on a system.

Anything to share?

In Advance
Thanks
Vincent

In article <1163551104.654825.108410 (AT) h54g2000cwb (DOT) googlegroups.com>,
"vcirilli" <vcirilli (AT) dslextreme (DOT) com> wrote:

The Binding Key is basically there so that you can have multiple
Runtime applications on the same computer and each one knows which
files belong to it ... but, since the runtime application itself is
always the same and separate from your data files, it's simplest to
re-use the same Binding Key for both versions. People could then
download the huge "demo" version to try it out, and then simply
download the proper data files when they're allowed the paid version
and replace the "demo" files.

A better way might be to simply have one version of the files - the
scripts can check a Global field (for example) to see whether or not
the system is still in "Demo" mode and should be limited.

Personally I don't think it's worth bothering with anti-piracy /
registration systems. If your solution is "so good" that everyone wants
it then the pirates will find a way around whatever system you try, and
if it's not that good then "nobody" is going to want it anyway ...
you're basically wasting your own time either way, as well as annoying
buyers who have to deal with silly registration systems or extra
downloads. (Adobe's "online" registration is hopeless since the website
is hopelessly slow to access from New Zealand for some strange reason,
meaning that we have to phone up each time.)



Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)