890 results found
Like mentioned above, we were getting reports that it was trying to contact LimeLM server even well before the valid period, i.e., before another time it should verify with the server again as the value passed as renewingDay inside IsGenuineEx(renewingDay, grace, false); https://wyday.com/forum/t/3587/isdatevalid-equivalent-function-adobe-air/#post-17435Looking forward.
You and I actually chatted regarding this exact user before about 18 months ago (though at the time I hadn't pinpointed the USB drives as the issue): https://wyday.com/forum/t/4325/slow-isgenuine-check-after-reboot-on-some-pcs/ Back then, the performance issue was more of an inconvenience, as he was seeing 15 second startup times after a reboot.
Below is code I use for checking a Lime license from Intel Fortran.Folks at the Intel Fortran support forum were instrumental in producing this.I can't explain the code, but it works for me.The code can go in a single file e.g.
https://wyday.com/forum/t/495/autoupdater-wpf-2-6-11-unhandled-exception/#post-2471 Anyone have any ideas what might have caused this?
When I tried to update this program, I get the below error.Similar thread: https://wyday.com/forum/t/71/error-file-name-too-long/#post-346 "The Specified path, file name, or both are too long.
I watched the tutorial, read the help files and forum posts and I am still confused. So I am here asking for help.
5. The fallout (this forum topic was created accusing us of incompetence, amateurish behavior, etc.).
------------------------------------------------------ Known problematic workarounds To get wyUpdate to use TLS 1.2, you also need to do one of the following (each of which has some downsides): Make registry changes (see wyBuild forum post)1) But in many cases it’s not practical to change a user’s system-wide registry settings given the user has other apps other than your own running on their device.
They'll still buy in to the future (literally) while satiating those who come to you as: 1) developers wanting or needing functionality you may never roadmap, 2) contributors to future editions who are able to make their cost-benefit-analysis -time- more bountiful than you've admitted in several responses above to being able to justify with the overall source-revenue of this product, 3) end-users who are ultimately always hamstring'd by the inability to compile their way around a program/need and instead tend to find themselves trying to cobble together disparately sourced combinations of <stuff> at each step of their own process to accomplish each <step> they come across (again, those "opened" sections can at least be provided an "as is" "plug-in" comprised of the above user submissions as well as any "approved" modifications of your own), 4) Prospective new funding sources for you who are going to run the gamut between wanting simple, clear, intuitive final products and extensible, robust, full featured, configurable and evolving integration software (all of which currently are just as likely right now to see the last release date and move on; if not, the next step is generically to find legitimacy within the periphery of the same site leading them to this support forum rife with unanswered premises and the above posts highlighting genuine concern over the future of the products themselves).
Based on what I saw in the forum I changed my call to ForceCheckForUpdate() to ForceCheckForUpdate(True).