6336Re: [BPQ32] Re: New CMS Site
- Jul 8 3:52 PMIsn't there a Winlink reflector for this?
On Jul 8, 2011, at 11:07 AM, Matt Zilmer <mzilmer@...> wrote:Well, if anyone cares, it's RMS Express 126.96.36.199 now....
One logical reason for forced updates is compatibility with the RMS software. A very few times, I've seen some major downrev'ed clients try to check in at my MARS RMS. If the downrev is far enough back, there may be a few troubles (getting caught in a state-state loop sometimes). Forced updates are simply the best way to ensure that most clients stay compatible with the RMS software.
Long-term, forced updates make it more likely the whole system will interoperate with the fewest problems.
Yeah, getting boxed in by having the AP yell at you for trying to shut down before the update is complete can be a PITA. However, some users would *never* update if they were given the opportunity to choose. This is very common with SDRs as well (the K3 for example) and can have strange results if a long overdue firmware upgrade is applied. i know quite a few K3 ops that haven't done any upgrades at all. Updates are best applied serially, for reasons of continuity and incremental bug reporting: "Which rev caused that bug, this one or the one before, or ...?"
Meanwhile, our IT geniuses here at Magellan have very conveniently disabled SMTP outbounds as well as Telnet, so I can't get MARS traffic early in the day for distribution on the day's traffic net in the afternoon. Sheesh!
Matt Zilmer, W6NIA / NNN0UET / NNN0GAF THREE
NMCM RMS Winmor: NNU9ET-5: Upland, CA.
Date: Fri, 8 Jul 2011 14:25:02 +0000
Subject: [BPQ32] Re: New CMS Site
Looks like they've also changed something that prevents the hosts file trick from blocking autoupdate on their software, at least on RMS Express. Guess I'll just have to firewall it off.
Considering RMS Express v188.8.131.52 blew up the channel listings, I'd think it would be wise to rethink the forced autoupdate mechanism so folks could have a bit more control over when it happens. Why they have to be such a PIA on this topic baffles me. Why is it just too simple to just toss up a windows "hey there's an update available, do you want to download & install or wait till later" Good grief.
Sorry for my venting ;-)
--- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
> The Winlink team has deployed an additional CMS site
> If you are using the CMS option of TelnetServer to access the Winlink
> servers the new server should be picked up automatically. There is no need
> to reload BPQ32.
> John G88BPO
- << Previous post in topic Next post in topic >>