jeff 1/11/2026 9:50:54 AM | I expect to publish the first JCapper Platinum 2025-2026 Full Program Update on or before Wed 1/14/2026 this coming week.
New Features include something many of you have been asking for - a new EICA2.csv File that gets populated during a SQL Calc Races (same column structure as the Full EICA.csv file populated during DBBuilds.)
Also, on 1/8/2026, Visual Crossing elevated the security protocol for their API from TLS 1.1 to TLS 1.2 with no advance warning.
Those of you running the JCapper TrackWeather Module under Win 10 or Win 11 (with anything close to current Windows Updates) likely did not notice the change - your TrackWeather Module continued to ping the API, parse JSon, and write Weather Data to the TrackWeather Table.
BUT, I still have three old Win 7 laptops.
The change to TLS 1.2 "broke" the TrackWeather Module on those machines - rendering it incapable of calling the Visual Crossing API.
I spent about a day and a half working to solve this and eventually did.
Several years ago Microsoft published a Windows Update (KB3140245) that enables TLS 1.2 for older operating systems like Win 7.
Despite KB3140245 being installed on those machines, all three were unable to call the Visual Crossing API.
I eventually came up with a script (contained in a .BAT file) that writes four entries to the Registry. (AI only got me part of the way there.)
After running the script in an elevated command prompt followed by a system Restart, the TrackWeather Modules on all three of those machines are now calling the API, getting JSon, and writing Weather Data to the TrackWeather Table.
I'm including the .BAT file in the new program update.
Nobody in the JCapper User Community reported any downtime from this, which has me wondering:
Am I the last software developer on the planet still running Windows 7 laptops?
Don't answer that.  
-jp .
|