Interaction between difference version TAsSolved

OK - strange problem here.

I am releasing a new version, with a new product version in TA.

I want (need, actually) to be able to grab V1 keys from within V2 so that I can populate a referrer key during the purchase process, so I instantiate an old TA for V1 using an explicit TA.dat and the old GUID.

When the user downloads the new version of my software, they can install side by side with the old and get a new trial.This works fine with the new TA product version (i.e. a completely(?) independent license to v1).

Things get a little weird, however, when I check for the activated status of V1 when running in V2, which I need to do so that I can grab the old key and present the user with an "upgrade" window rather than a "purchase" one.

This is what seems to be happening:

When V2 is running in trial mode, V1 ALSO REVERTS TO TRIAL MODE!! This only happens if I interact with the V1 license, to check if it is active & grab the product key.

So: Run V2, get a new 14 day trial, with a normal V1 activation present on the computer.

Now - run V1 (which the user may well want to do), and the activation is "gone" somehow and trial mode is engaged - this is despite the fact that there has been no new V1 trial at all.

Any ideas what could be going on here?

Quick followup:

The response I get in V1 is "NotGenuine" after doing something with the V2 app. The trial that it reverts to is possibly a "genuine" trial. I can't remember if I ever trialled this PC (I must have done, but long ago - so it does seem a little weird).

Could this be a version issue? Do I need to update the old V1 to the most recent TA binaries/TA.dat file??

I have reduced TA calls to a bare minimum in order to get this result.

Calling IsGenuine from another version of my application, using a newly downloaded TA.DAT and the lastest TA binaries results in V1 of my app getting a NotGenuine response to its own IsGenuine call.

This is a big issue for me - likely fixed with new binaries/Ta.DAT for my V1?

We resolved this via email, but I'll update this topic to include the conclusion. This has been covered elsewhere, but TurboActivate is backwards compatible but not forwards compatible. Meaning you should not run an old version of TurboActivate on the same activation and trial data as a new version of TurboActivate. When a new major version of TurboActivate runs (like TA 4.0) it will upgrade any old versions of TurboActivate's activation and trial data. This makes it possible to use all the newest features and bug fixes. But it also means that the old version of TurboActivate cannot read the new data.

So there are multiple possible solutions:

a. Only use one version of your app at a time on a computer (if they're using the same activation data -- a.k.a. they're using the same LimeLM version).

OR

b. If you want to use multiple versions of your app on the same computer make sure they're all using the same version of TurboActivate.

OR

c. If you want to use multiple versions of your app on the same computer make sure they're all using separate versions of LimeLM (and thus separate activation data -- so the version of TA doesn't matter because it won't touch the other version's data).

So to go with option C, does that mean different products in LimeLM? How do we allow users to run multiple versions of our software, with different versions of TA, on the same machine?

Thanks,Chris

Hey Chris,

It doesn't have to be separate products (but it could be). It just has to be a separate version. You can create that separate version in the same product (by clicking "Create new version").

Wyatt wrote:> Hey Chris,> > It doesn't have to be separate products (but it could be). It just has to> be a separate version. You can create that separate version in the same> product (by clicking "Create new version").

Hi Wyatt,Could you please clarify what the difference between a new version and a new product is, as far as Lime is concerned?As far as I can see, there is no difference - what am I missing?

The only difference is how things are organized in LimeLM (and how you can then search for keys and verified trials).

Reply
Discard post