Experimental 2.5.0 solved my K4 problem but it timed out on August 31. The current release is 2.4.0 so I'm back to square 1. Is there a way to extend the lifetime of the experimental release or will the K4 fix be incorporated into a production release some time soon? Thanks, Rick N6XI
On Mon, Jul 19, 2021 at 7:50 AM Rick Tavan <rick@...> wrote:
--
-- Rick Tavan Truckee and Saratoga, CA
|
|