Topic: So..here's a hypothetical question...

[rnvinc]

So here's a hypothetical question...

So it seems from watchin the boards that ...:
*6.180 was a widespread disaster
*6.310 might be "stable"
*HB software releases contain "all" previous updates...(therefore updating to 6.310 also gives version 6.180 with a fix included in 6.310...

Wouldn't that be like going to the doctor to pick up vitamins...

And while you're there...

The only way to get your intended quest for vitamins is to also get infected with the flu virus and get the antibiotics to combat it...??

Rickie

[Roddy]

rnvinc, Yep !!

Roddy

[Jim Jack]

It's like getting your vitamins from someone who got over the flu. That person is no longer infected.

[Bob B]

That's why I rarely get in a hurry to get the latest software.......same thing no matter who it is.  Wait til the bugs get worked out.
I always say don't be on the "bleeding" edge.

[George]

rnvinc

I have installed every update as they were released and I keep a copy of all of the updates just in case I need to reinstall an older version.  So far I have only reinstalled an older version once.

George

[rnvinc]

I have yet to see an update feature that warrants me taking the chance of locking my unit up...none...

I just find it interesting to try and comprehend the programmer's thought process that leaves the user with no choice but to receive the infected part of the download..."whether I want it or not"... Just to get a later update feature that may actually be beneficial to my needs...

"OH but don't worry about being infected..We're including the antibiotics too..."

Yay.... I feel so comforted...

(It does make interesting discussion tho)...

Rickie

[ITGEEK]

I think you are thinking about this incorrectly.
The way I figure it, each part of the system has
it's own set of programming code.

As each set of code gets revised, sometimes it doesn't work
correctly (has bugs).

So, when you are installing an upgrade, you are just
installing the combined set of each of the newest code
parts.
You are not first installing a set of code with a bug in it,
then installing over top of that, a set of code that fixes
that bug.

I don't think it installs every complete old update.
If it did that, then update files would be 100+ or so
megabytes, and may take an hour or so to update.

So, you are not installing an old bug at all.
I can tell you that I am as hesitant as the next person
to update.

I took the plunge with 6.310 and I've never been happier.
My 1197c is the best it's ever been.
I would highly recommend update 6.310.

[rnvinc]

I think you are thinking about this incorrectly.
The way I figure it, each part of the system has
it's own set of programming code.

As each set of code gets revised, sometimes it doesn't work
correctly (has bugs).

So, when you are installing an upgrade, you are just
installing the combined set of each of the newest code
parts.
You are not first installing a set of code with a bug in it,
then installing over top of that, a set of code that fixes
that bug.

I don't think it installs every complete old update.
If it did that, then update files would be 100+ or so
megabytes, and may take an hour or so to update.

So, you are not installing an old bug at all.
I can tell you that I am as hesitant as the next person
to update.

I took the plunge with 6.310 and I've never been happier.
My 1197c is the best it's ever been.
I would highly recommend update 6.310.

And this is exactly why I started the idea of discussion...

To invite into the discussion other ideas of how update programming is applied into the unit inner workings...

I'm not a programmer... Never claimed to be...

I just a curious user with a curious idea...what if...??

My premise in the entire thread is to spark discussion of the "what if"....in hopes...

In hopes that someone with factual knowledge in HB programming sequences would be interested enough in the discussion to input the facts into to the following question...:

What does the below statement from HB actually mean...??...

"All HB updates include all previous updates"

Hasn't anyone ever wondered if you are installing every bug HB ever inadvertantly released in their software updates....??

Rickie

[ITGEEK]

I think Humminbird should re-phrase that statement to be:
"All HB updates include the most recent code available at the time each update is released"

It would be nice if Greg could chime in here and give us some
insider info.

[Bob B]

What does the below statement from HB actually mean...??...

"All HB updates include all previous updates"

Hasn't anyone ever wondered if you are installing every bug HB ever inadvertantly released in their software updates....??

Rickie

I think that HB is trying to indicate is that it is not necessarry to install each update in succession to get the functionality of the previous updates......The next update may include the code to support 360, but it is not just that.....it also includes the previous updates as well.....The new update doesn't just "add" to the previous software......it totally replaces it.

I also think Itgeek is correct about the fixes HB applies to the updates.

[George]

I could be wrong, but I believe that Greg has already stated that each new release is in total with corrections and updates so that we do not to install each release.  Also, most of the time HB tells us what the updates are, not sure they are always stating the error corrections.

George

[Jim Jack]

Each new version of the SW has all the previous fixes and features in the SW plus the new stuff.

"All HB updates include all previous updates"
What does the below statement from HB actually mean...??...

Think of it like this. If 1 year you fixed broken windows in your house, the next year added hardwood floors, the year after that remodeled the kitchen and 6 months after that you redid the landscape then sold your house. The new owner would get the house and all previous updates. Then new owner did not get the house with the broken windows, shag carpet, 70's kitchen, and overgrown yard plus the upgrades.

[ITGEEK]

Humminbird certainly does not tell us all that are in the updates.
They don't document that an update actually caused a problem.

Update 6.180 caused my XM weather to stop working.
Update 6.310 caused the XM to start working again.

There was no mention in the 6.310 update documentation
that it fixed the XM problem, or that the previous update
caused an XM problem.

[rnvinc]

I could be wrong, but I believe that Greg has already stated that each new release is in total with corrections and updates so that we do not to install each release.

George

You guys bear with me here a second... My OCD thinks way too deep sometimes...

The above statement (from a paraphrased statement from Greg)........"in total with corrections and updates"... can be expanded into 2 completely different possibilities..(let's omit "brand new" features released in updates ...just for clarity of discussion)...

Scenario 1.. Update version "x" contains the bugs from the previous version ...plus (+) additional code to fix that earlier bugged code....

Scenario 2. Update version "x" contains corrected code that replaces that bugged code from the previous version...

Rickie

[Jim Jack]

The technical answer is it could be either or both. It depends on what the bug was, these as far as I know are not viruses.

If the bug was code that pointed to something that was not there then code would be added so that the pointer worked.

If there was an error in the previous code, then it would be corrected.

So the bug is no longer there. Just like the analogy I posted about the house, you do not get a broken window underneath a new window, you get the new window.

The all previous updates statement means that each new SW release is a complete version of the SW. The updates do not just install a feature or a fix. This means you could start with no SW install the latest update and having everything.

Feel for you brother your OCD is running a muck. LOL

Regards,
Jim

[ITGEEK]

I vote for scenario #2.

The update files are now about 4 megabytes.
If scenario #1 was true, then the update files could be
ten times as large, and take that much more time to complete.

[gramps50]

It appears to me that your thinking about this as if you were updating Windows, where the patch to fix the bug breaks something else and you end up with a broken system until they figure out how to make it so you don't know it's broken any more.

From the process I think they are reflashing the prom each time you do an update so in essence your getting new software each time, not just adding stuff on top of what you already have, so any bug fixes shot be good clean code to fix a problem.