1900 results found
The actual solution is to use TurboFloat: https://wyday.com/limelm/help/vm-hypervisor-licensing/ If you just all TA activations in VMs it might work for a little while.
We don't currently have enough free time to build something for you, but here's the basics of what you need to do: Make a "POST" request to the LimeLM servers (specifically, to https://wyday.com/limelm/api/rest/)Make sure you pass the parameters to generate the product key.
So in summary I am trying to debug the code from https://code.google.com/p/wyupdate/source/checkout in visual studio but the debugger detaches.
I wonder what your thoughts are about a special administrator-mode TA_* function that encapsulates the desired behavior, like this: https://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/script-to-disable-enable-network-interface/8eb15e24-7d85-4a16-b42a-a874b9bb3a28
The problems you're having with any node-locked licensing on VMs, and the solution to said problem is described here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ >> "Now, I enforce checking the License every 0 (for VMs, 30 for real PC *) days on the Internet.
from https://wyday.com/limelm/help/using-turboactivate-with-c-plus-plus/ I read :"Handling the case where the customer has not re-verified with the server in X + Y daysIf the customer has not successfully re-verified with the servers in nDaysBetweenChecks + nGraceDaysOnInetErr then TA_IsGenuineEx() will return TA_FAIL" I am new in using LIMELM,I need to better undesrtand this question:Suppose a user has downloaded a tria version of my app, and he has not re-verified in (nDaysBetweenChecks + nGraceDays = 90 + 15 = 105 days.
Hi, I hope I am not wasting your time with simple questions but unfortunately I could not understand following points(Although I have already read https://wyday.com/limelm/help/trials/ verified and unverified trial sections) 1-I can not understand what “verified trials: 1” statistic means under my LimeLM “Account" tab\"Your account" title .
I've followed the steps found here (https://wyday.com/limelm/help/using-turboactivate-with-nsis/), replacing the version GUID with the one found on our product page.
$AuthNetTest && !(isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on'))){ header("HTTP/1.1 301 Moved Permanently"); header('Location: '.'
You can find the patch at the Google code repository: https://code.google.com/p/wyupdate/issues/detail?
I have the same question as the post at https://wyday.com/forum/t/2040/change-initial-number-of-activations/#post-10511 but need a more specific answer: I'd like the default number of activations for my products to be 3 to allow for installation on a work and home computer or to allow for a new computer, hard drive crash, etc. without my manual intervention.
Firstly, can Internet Explorer contact https://wyday.com? If not, then they're blocking wyday.com somewhere on their networks.
>>In TurboActivate 4.0, rather than using the typical user agent we've previously used -- TurboActivate / VERSION (https://wyday.com/limelm/) -- we're spoofing the Internet Explorer user agent.
Post by Wyatt O'Day on Aug 12, 2016You can get it on your API page: https://wyday.com/limelm/api/#turboactivate >> "Apparently you only prepared Windows and Mac libraries, even though the issue obviously affects Linux as well, correct?"
If they can't unblock wyday.com either due to faulty policies or old technology (e.g. firewalls that don't support domain names, but only support IP addresses), then the customer can always offline activate: https://wyday.com/limelm/help/offline-activation/ >> "Could you please let me know the IP address of TurboActivate license server (used for activating a trial license)?"
Not to mention well documented: https://wyday.com/limelm/help/turbofloat-server/
Wyatt wrote:> Heres how to keep config files:> https://wyday.com/wybuild/help/faq.php#config-files That's definitely what I'll do going forward, but that's not how it's been done at the moment.
https://wyday.com/limelm/help/using-turboactivate-with-csharp/#target-anycpu In short: either target x86, or, if you're targeting AnyCPU, make sure you name the dlls correctly.
https://wyday.com/limelm/help/faq/#fix-broken-wmi