Unitrunker Forcing Users To Update?

[enosjones]

besides that thread has been quiet in my emails...

 

[GTR8000]

but he also said it wasn't mandatory to switch if we felt uneasy about it until all bugs were resolved.

Anyway, my hunch is that the ticking time bomb code wasn't scrubbed before 2.1.0.110 was promoted to an official public release.

As I said, it's probably a simple oversight and he forgot to remove the time bomb code from 2.1.0.110 when he released it publicly. It happens, no one is perfect, assuming that's what happened here and it wasn't some sort of weird .NET/Windows glitch having to do with the year rolling over to 2026.

For the record, he wrote what you're referencing in April 2024 when 2.2.0.5 was released, cautioning those running 2.1 not to jump too quickly to 2.2 unless they understood the risks. Since that time there have been 32 or so subsequent previews of 2.2 released, and the latest 2.2.0.37 is quite stable.

Every version of Unitrunker has some glitches and bugs. That's not an indictment of the software or Rick's coding, it's simply the nature of fast evolving software that attempts to keep up with all of the quirks of these trunked systems it decodes. It's also the nature of the beast when Rick adds new features or functionality, that something isn't going to be perfect the first time around, and it might even break something else. I suppose y'all could ask for a refund if you're not satisfied. 😂

 

[KevinC]

It's also the nature of the beast when Rick adds new features or functionality, that something isn't going to be perfect the first time around, and it might even break something else.

I can attest to that. I updated my SDS200 and my refrigerator stopped working 2 days later.

 

[KE4ZNR]

I can attest to that. I updated my SDS200 and my refrigerator stopped working 2 days later.

Is your refrigerator now running?

Because you probably want to put on some tennis shoes and chase it down before it gets too far away......

 

[GTR8000]

I can attest to that. I updated my SDS200 and my refrigerator stopped working 2 days later.

Ah, that was probably due to the IV&D fix. Also make sure your fridge is set to 2.

 

[RadioDitch]

That was absolutely the issue. People were joining the Google group and were installing preview versions (aka beta, or even alpha in some cases), and never bothering to keep up to date. Rick would subsequently release a dozen or more previews that fixed numerous bugs. Someone would then come along with a badly outdated preview asking for help on bugs that had already been addressed long ago. That was the impetus for Rick to code a ticking time bomb into each preview release. I believe initially it was 12 months, then he expanded it to 18 months. Which by the way is extremely generous given the ever-evolving nature of Unitrunker previews (there were 74 previews of 2.0, 110 previews of 2.1, and so far 37 previews of 2.2).

GTR with the answers as usual. Thank you. That's a reasonable and logical explanation. That makes sense. And the 12 months is consistent with the previous install date before this happened.

Participation in the Google group and installing those preview versions is entirely voluntary, however Rick has always asked that early adopters stay as current as possible to avoid having to support many stages of the software's evolution. I don't think that's an unreasonable request, especially for such feature rich software that he has developed for over two decades at no charge to end users.

Anyway, my hunch is that the ticking time bomb code wasn't scrubbed before 2.1.0.110 was promoted to an official public release.

It's not an unreasonable request, but I wish it had been mentioned it was there. Also, as stated in the original post, the way it originally presented itself was obstructive. Neither 'okay' nor 'cancel' would allow me to go back to the program. Apparently for others 'cancel' worked from the start, but it was initially persistent for me. I can get around it now though.

Glad to know it's a time bomb though and not a background connection. Still disagree with it, but at least I understand why now.

 

[RadioDitch]

I can attest to that. I updated my SDS200 and my refrigerator stopped working 2 days later.

You laugh, but I've seem some wild stuff with IOT (Internet Of Things) connected devices. Guy updated his modem and his vacuum stopped working. Hell of a way to find out your cordless vacuum has an undocumented internet connection.

 

[Echo4Thirty]

I can attest to that. I updated my SDS200 and my refrigerator stopped working 2 days later.

Must be a Motorola.

 

[Unitrunker2]

Sorry folks.

Certificates renewed for the website.

The plan was for 2.2 to be cleared as an official release so that - by the time this popup appeared, everyone on 2.1 could upgrade to 2.2. However, 2.2 isn't ready. I have an ask to update 2.1 to support the HydraSDR RF1 (as 2.2 preview does today). I can take that opportunity to also push back the nag window.

To be clear - that pop up does not prevent you from doing anything. It's just a reminder. No one is making you upgrade. Dismiss it and carry on.

Part of the reason for the pop up is certain websites - namely with .ru domains - hosting very old copies. The nag window eventually makes the user aware of where to get the current and latest version.