We've been using TurboActivate in our product for a while and not really noticing any significant issues.
However, today I just happened to run our app after intentionally disabling the Wi-Fi card on my notebook, and I noticed that IsActivated() returns TA_FAIL, even though it was previously activated successfully.
Subsequently enabling the Wi-Fi card again, and running the app again, caused IsActivated() to return TA_OK as expected.
Is there some reason that disabling the Wi-Fi would cause IsActivated to fail? This could be a serious problem for our users.
Thanks in advance for any insight.
There's a difference between disabling wifi, or using another network connection, and actually disabling the wifi card (or any other network adapter in the network adapter settings). Don't disable the network adapter.
That being said, a lot of customers do end up doing stupid things like disabling network adapters, so we're going to make TurboActivate 4.0 more robust in detecting network adapters that are still connected to the machine (but aren't powered up).
Correct. Customers do stupid things. There is no way we can control that, so we have to account for it. Thus, the possibility of them disabling the wifi card must not interfere with their activation. Good to know that this will be handled in 4.0.
oPryzeLPI second this. I get soooo many emails from people that need me to deactivate their key because TA thinks their hardware changed. When is 4.0 coming out? I realllly need this.
No hard date yet. We're working hard to get it out soon.
