Pantelones wrote:Can you provide any information on questions and speculations within this thread? But neither does anyone else here by looks of it. I don't mind speculation. Just don't dress it up as fact or knowledge.
You did the right thing by saying you have zero evidence, which tells us all we need. He was just making a statement based on the direction the industry is going. It's a valid contribution to this thread and does make some sense. Majority of people don't want software based programs, they want apps/cloud computing now. (Yes I know apps have software, I just didn't know how to distinguish the two). My comment wasn't negative, just pointing out that there's often too much speculation and I acknowledged Pantelones's stated ignorance on this specific case.
TrainingPeaks WKO+ 3.0 + Crack Keygen/Serial. Date added: Jan 2018. TrainingPeaks WKO+ 3.0 screenshot ScreenShot. Download free apk file Trainingpeaks Wko 3 0 Keygen Crack 4e7d4275ad Keygenrar GridProv45EDGEzip WINZIP17 0 CRACK Keeper of the Lost Citiespdf.
As for general industry trends, perhaps most people like cloud computing. Personally I don't for this kind of in-depth analysis application. Spoke wrote:When does WKO4 come out? Whenever it comes out. It has been very clear over the years that WKO+ is the red headed foster child of the Training Peaks family.
It has been my thoughts that the WKO+, compared to the Training Peaks website, is a small revenue stream and therefore is poorly resourced. If you look at the features which were added in WKO+ 3.0 (released Dec 2009, from v2.2) it was not a very impressive upgrade and has not seen a single features added since. Hopefully version 4.0 redeems and becomes well supported. 3.0 was merely a copy protection upgrade. In the days of 2.2, TP was enjoying their monopoly. So much that they could charge quite a bit and also implement a draconian DRM scheme that was linked to your Windows serial number (maybe your MAC address or HDD serial number as well--it's been awhile).
Many folks found themselves up the creek without a paddle when their HDD crashed or they reinstalled the OS. They had to go beg TP for another registration code only to be accused of software piracy and denied. After being called out on various blogs and forums, TP relaxed their policies a little. Hunter Allen took the opportunity to whine about how rampant software piracy nearly destroyed their little company.
However, extensive searches of the 'net revealed no pirated versions of the software. None whatsoever. It wasn't because their copy protection scheme was particularly robust but because their software flew under the radar of pirates who tended to focus on popular products. This 'rampant piracy' was either imaginary or simply some people requesting replacement serial numbers that they didn't really need. Either way, it was not rampant. Someone wanted to make Hunter honest about his claims, cracked 2.2, and released it on B*tT****nt. Near the end of its life, there were a flurry of builds for 2.2.
That was because each build required a new crack (exe patch) and also incorporated new anti-debugging features. TP eventually gave up and rushed a buggy 3.0 to the market. The reason it added so few features and was no more than a cosmetic refresh was because its main purpose was to introduce a new copy protection scheme which they believed was much harder to crack. It's no coincidence that TP didn't wait long before ceasing support of 2.2. WKO+ 3.0 even started referring to the alphanumeric ID derived from the user's Windows serial number (or HDD serial # or MAC--I forget) as the 'fingerprint' which has interesting and likely deliberate connotations. The first build of 3.0 ran the registration code check something like 47 times while loading. Many of the main routines called the registration code check so that nearly every user action resulted in a check of your registration code.
I believe every mouse click warranted a registration code check. That's why people complained that 3.0 was slow. Of course, this was ridiculous because if someone wanted to patch the.exe they would just patch the one registration check not the 400 calls to it individually. What happened though was even worse for TP: WKO+ 3.0's registration code generation algorithm was reverse engineered and a key generator was released that allowed anyone to generate registration codes at will. Install xender app. Since TP could not change the algorithm without causing problems for legitimate keys, they could not solve the problem by releasing new builds. And that's why 3.0 builds and updates were few and slow to come. It was merely a copy protection upgrade and with its primary purpose foiled, TP had little motivation to fix its bugs or develop new features.