TA_IsGenuineEx behaviour with short GENUINE_OPTIONS

Hi Wyatt,

I am using TA_IsGenuineEx with minimal GENUINE_OPTIONS values (nDaysBetweenChecks = nGraceDaysOnInetErr = 1) and online activation. When I don't use my application for a "long" time (> 2 days) and I reopen it then it starts but TA_IsGenuineEx returns something different from TA_OK (I suspect TA_E_INET or TA_E_INET_DELAYED but unfortunately I don't have logged this warning). If I close the application and reopen it then TA_IsGenuineEx returns TA_FAIL and the application does not start.There are no networks problem (I can contact wyday.com without problems with IE) and I'm using TA v4.0.9.3.I put these short times for security reasons to avoid the situation in which the user works out-of-internet for too much time (a temporary outage of the internet connection is allowed, but it must be short).I realized that I can reopen the application even after many days and then TA_IsGenuineEx updates its internal date/time counters returning TA_OK, but I was wrong at this point.The questions: a) can I keep the current values in GENUINE_OPTIONS and try to force TA_IsGenuine when TA_IsGenuineEx fails?b) if not, which is then the best policy?

Best Regards,

Alessandro

Hey Alessandro,

>> "If I close the application and reopen it then TA_IsGenuineEx returns TA_FAIL and the application does not start."

With X & Y both being set to 1 day (not recommended!!), then yes, then next time the user starts your app after not being able to contact the servers it will return TA_FAIL.

See the documentation and example for how to prompt the user to reverify.

>> "a) can I keep the current values in GENUINE_OPTIONS and try to force TA_IsGenuine when TA_IsGenuineEx fails?"

Nope, see our examples for how to handle things. TA_IsGenuineEx() already contacts the servers. Just hammering the servers with another call to TA_IsGenuine() is not the solution.

Also, always use the latest version of TurboActivate. Currently that's TA 4.0.9.6.

Reply
Discard post