2112Re: [tracker2] Re: Firmware update posted, for real...
- Aug 31, 2007I updated the version number to 54100, and discovered that it wasn't
getting compiled in right. I bumped it up to 54105 and now it shows up
in the banner but not in the config header that otwincfg reads.
I really have no idea why it's not set properly. That was why I delayed
updating it, but I finally decided it's got to be a compiler bug. I
rebuilt everything, and nowhere in the source can you find the old macro
definition, but it's still there. I've got to go clean out all of the
intermediate files and see if that changes anything.
So for now, it'll show up in the config screen as 54100, but the banner
will say 54105.
I think this might have happened in the past, but I'm not sure. There
used to be a bug where the version would be carried over if you didn't
erase your configuration. I'm almost certain that's been fixed, but I
always attributed mismatches to that bug and didn't think about the
possibility that the compiler wasn't catching the updated macro.
It wouldn't be the first bug I've found. The PSK31 varicode table has
one entry in hex rather than binary, because if you initialize the
entire table in binary it drops one value. That drove me nuts... spent
hours trying to track it down.
> Thanks Scott:
> I had tried this morning and still had the 2006-12-06 (how I hate
> the illogical US date format!) listing on the web download so
> thought it had not changed. Now at work and can't check. However I
> just went to http://n1vg.net/opentracker/downloads.php
> <http://n1vg.net/opentracker/downloads.php> and it looks
> like the version posted there now is 54100 (D354). This also used
> to be 54085 (D345) so this has been updated. Is this the same
> updated version that I can download to my files?
> So my question is - is the latest firmware version still called
> --- In firstname.lastname@example.org <mailto:tracker2%40yahoogroups.com>,
> Scott Miller <scott@...> wrote:
> > Ok, I'm an idiot. I'd been posting firmware updates but the index
> > was going to the wrong place. I discovered it yesterday when I
> > from another machine and saw that it was still showing up as
> > beta firmware and was loading 53085.
> > I've fixed the index file and you should now get the updated
> > including the MAXRANGE and Garmin escape fixes.
> > Scott
- << Previous post in topic