Lipton...oh, and to be more precise:
0 is being written to trialDays when calling:
hr = TrialDaysRemaining((STRCTYPE)TA_GUID, &trialDays);
Switching from 0 to x days unverfied trial
LiptonHi there,
I've been using TurboActivate for a while and been very happy with it. So far my software could only be used with a product key, but now I want to give users the chance to test it without having to go through the activation procedure.In order to make this happen I changed the trial length on wyday from 0 to 30 days, downloaded the TurboActivate.dat file, and replaced the old .dat in the bin folder where my executable is located.
This does not work.
Is there anything that needs to be done to enable an unverified trial period?
Lipton
LiptonExcuse me if it has been asked before. I'm kindly asking you to refer to the right thread if that's the case, but I definitely need an answer here.
The problem is very likely you're casting a non-wchar_t string to wchar_t string. Or vice versa. Don't use casts at all with TurboActivate. If it's failing to compile it's because you're passing an incompatible data type.
See our Example.c file to see how to pass strings on various platforms.
Let me know if that helps.
LiptonThanks for your response. I took out the cast and checked if everything else is done as shown in example.c (which was the case). The behavior is still the same - still getting a 0 as remaining trial days while the return value is 'S_OK'.
Any other ideas??
If you already downloaded the TurboActivate.dat file, and you're actually using the correct string types (UTF-8 char* on Linux/Mac/Unix, UTF-16 wchar_t* on Windows) then everything is good.
Also realize that downloading a new TurboActivate.dat doesn't reset the trial. If you ever called UseTrial() from your app when you had the 0-day trial then that is when the trial started.
It's likely that's what's happening.
Dies that make sense?
The way to test a "fresh install" is to make a VM, the install your app.
A VM is easiest (test, restore snapshot, test again etc.) If you use TA_USER, you can also create a few test user accounts/logins and switch around. Not sure if that works on Windows but I do that test on OSX.
