Activation takes 5+ seconds? Disabled WiFi on Win7Solved

I'm using the 4.0.9.6 Java APIs and using the convenience function IsGenuine (IsGenuineEx in other APIs) with params 45, 14, true, true. However, after initially activating (which I expect to be slower), every subsequent call to IsGenuine takes 5+ seconds. Is this to be expected? I'm pretty sure it's correctly *not* contacting servers, since I deactivate through the web API, yet it allows the software to run (since I'm waiting 45 days to recheck). Since it's a native call, it's hard for me to debug further. I got the impression it would be <1 second to do a local check from the documentation.

(P.S. Testing from a pretty standard Win7 computer with an SSD, 8 cores, 32 GB RAM, and a great internet connection, so probably not environmental/hardware, but possibly).

, edited

Under normal circumstances, no, that's not normal. Typically what slows the calls down is either (a) using an old version of TurboActivate (always use the latest!) or (b) having slow hard drives attached to the computer that how to power on and spin-up if they're accessed at all.

Neither are the case in my situation (SSD drive to boot and using the lastest that I downloaded this week). Any other ways of debugging this? thanks for the fast response.

Here's my code (in Scala): logger.info("Pre-genuine check") val isGen = ta.IsGenuine(CHECK_DAYS, GRACE_DAYS, true, true) logger.info("Post-genuine check, pre-activated check") val isAct = ta.IsActivated logger.info("Post-activated check")

(isGen, isAct) match { case (IsGenuineResult.Genuine, true) | (IsGenuineResult.GenuineFeaturesChanged, true) ? new LicenseInfo(LicenseInfo.Activated, version, licensee, expiration) case (IsGenuineResult.InternetError, true) ? new LicenseInfo(LicenseInfo.ActivatedGrace, version, licensee, expiration) case (_, true) ? new LicenseInfo(LicenseInfo.ReVerify) case _ ? new LicenseInfo(LicenseInfo.NeedKey) }

And the results:13:25:02.577 [pool-2-thread-1] INFO - Pre-genuine check13:25:07.327 [pool-2-thread-1] INFO - Post-genuine check, pre-activated check13:25:07.328 [pool-2-thread-1] INFO - Post-activated check

Should I not be checking IsGenuine every time? I thought the point of those day parameters were to skip the round trip to the server automatically.

I did confirm I was using 4.0.9.6 both in the API code and in the DLL properties via Windows Explorer. Additionally, using JProfiler I confirmed that all 5 seconds were spent in:c.w.t.TurboActivate.IsGenuinec.w.t.$Proxy8.TA_IsGenuineExc.s.j.Library$Handler.invoke(i.e. inside the native call, not any of my code or other unrelated locations).

>> "Should I not be checking IsGenuine every time? I thought the point of those day parameters were to skip the round trip to the server automatically."

You should be calling it like the example shows (which it looks like you're doing).

What happens when you just put TurboActivate.exe, TurboActivate.dll, and TurboActivate.dat all in the same directory and then double-click TurboActivate.exe? Is it slow as well?

If not, then the slowness might be because JNA is taking a long time. So, update your JRE and JDK to the latest versions. Then update your JNA to the latest version and try again.

Good idea, but putting the 3 files in the same dir and running your wizard .exe is still 5 seconds from the time I launch the command until the window comes up and says I'm activated. I'm up to date on Java and using the latest JNA as per your release notes (but this test shows that it's not in the Java layer). Is it possible there was a minor performance regression bug in the latest release since I'm using your newest release?

My guess is that it's an attached storage medium (not necessarily your main hard drive) that is slow. I get that you have an SSD as your main drive. That's likely fine. It's all the *other* drives causing a problem.

1. Do you have any attached hard drives (either internally via SATA or IDE, externally via USB, eSATA, etc.)?

2. Do you have any SD cards plugged into the machine?

TurboActivate will go as slow as the slowest medium installed on your computer. So if you have a creaky old spinning harddrive attached or a very old SD card (or SD card reader) attached, then TurboActivate will wait for that medium to respond before continuing.

Ah I see. I do have a 7200 RPM standard secondary HD internal to the computer as well, but that typically is in use and shouldn't have spin up time (for example, my Dropbox-synced folder is on that HD).

However, I also have a network share folder mounted as drive Z: , and a virtual CD-Rom. I uninstalled the virtual CD ROM, unmapped the share drive, and disabled all drives shown in my computer except for the two HDs and the 5 second lag remains. I do not have any other phones or SD cards attached.

I think it has to do with my wireless adapter being disabled. When I'm at work, I leave it disabled to force it to use my wired connection. I'm at a coffee shop (using WiFi) now and it's about 1 second. Is that expected?

Ah, yes, on old versions of Windows (Windows 7 and older) if you disable the network adapters TurboActivate will attempt to re-enable the adapters temporarily to read their information (which, depending on the hardware itself, can be a slow process).

More information here: https://wyday.com/limelm/help/faq/#disabled-adapters

This isn't a problem on new versions of Windows (8.0 and newer).

OK great! thanks for your time and I'm glad it's a known thing and that it probably won't happen to users.

Hi, having just upgraded to Turbofloat 4.0.9.6 from 3.x we have just hit this problem ourselves. Is there any other workaround? We currently have three quarters of our customers on Windows 7 and don't see that changing very soon. And we don't really want to get into discussions with customers about configuring network adapters. Would it be possible to add an option to "not check disabled adapters on Windows 7" or something?

Nope, the network adapters are required. A lot of thought, development, and testing went into 4.x to solve all outstanding false positives and false negatives. Requiring real network adapters being enabled solves the edge cases from the noisiest customers.

See all options and a full description here: https://wyday.com/limelm/help/faq/#disabled-adapters

Also, TurboFloat *requires* an active network connection (by the very nature of floating licensing). So, a customer complaining about disabling network adapters when they're using TurboFloat doesn't make sense.

On further inspection it looks like all the adapters are enabled on the problem machine. However there is one adapter for a VPN which does not have enable/disable options, could that be causing a problem?

BTW - I am talking about TurboActivate, sorry for the confusion.

If it's a VPN it might appear as a connection, but it's really not (and TurboActivate does not take it into account). TurboActivate only cares about real network connections (wired and wireless). Tell the user to enable all *real* network adapters on their computer. If they've done that, and they're still having problems, then shoot us an email at support@wyday.com and we'll send you some commands for the customer to run.

Sent you an email yesterday.

We just shot you an email with instructions & commands for the customer to run. Something is broken on that machine (and no, TurboActivate doesn't care about VPNs being enabled or disabled)

Answer

We've fixed this issued (many and/or very slow and/or broken "storage devices") in TA / TF / TFS 4.4, out now.