997 woes....

Quote:

---

Originally Posted by CRAPPIEHUNTER68

Sorry I forgot that part. I keep the old version in case I do not like the new. I reloaded the old then the new again.

---

I just got off phone with HB. That is what they suggested.

My old version is on my computer at the lake house, so they are emailing me the older version.

Thanks

Tom

Older version installed, then newer version installed. No workie...........

However on my own imitative, I removed all my waypoints and now it works??????????:confused:

Dang thing is getting even with me for cuzzing the GPS donut....:eek:

This unit is full of ghost turds. They after me...:rolleyes::rolleyes:

You'll get it worked out CP. Is it under warranty?

Didn't I see something about resetting defaults before, and after the update? Thought I did.

Quote:

---

Originally Posted by mduncan62

You'll get it worked out CP. Is it under warranty?

Didn't I see something about resetting defaults before, and after the update? Thought I did.

---

It started working when I removed my waypoints. 997 hates me.:(

Quote:

---

Originally Posted by Cane Pole

It started working when I removed my waypoints. 997 hates me.:(

---

Does it stop if you import them again?

Quote:

---

Originally Posted by mduncan62

Does it stop if you import them again?

---

I ain't got that far yet..

Golden rule to always restore factory defaults before update 4.750 and after update even tho HB did say the 4.750 will restore defaults after this update. But what in Blazes does Gps way points have to do with anything. :confused:

Quote:

---

Originally Posted by jaxsprat

Golden rule to always restore factory defaults before update 4.750 and after update even tho HB did say the 4.750 will restore defaults after this update. But what in Blazes does Gps way points have to do with anything. :confused:

---

If I had written the update program, and the default settings were a mandate, I would have the update program set these parameters at program start and maybe program end. This would be my fix, not the "you all don't forget to" scenario. But then, I am old school and my grand kids are smarter than I am. Just ask them.

However, this "you oughta set" claim does gives them an "wiggle out" when things go to chit.

Quote:

---

Originally Posted by Cane Pole

If I had written the update program, and the default settings were a mandate, I would have the update program set these parameters at program start and maybe program end. This would be my fix, not the "you all don't forget to" scenario. But then, I am old school and my grand kids are smarter than I am. Just ask them.

However, this "you oughta set" claim does gives them an "wiggle out" when things go to chit.

---

Yep, you got that right.
me thinks all us early (3/4 years ago) buyers are $2000 owners of guinea pigs.:rolleyes:

Well now, isn't that strange. Canepole be sure to update us when you reload the waypoints if it works again or not.
My bet is this may lead to a new update from HB and stems from a directory issue with the resident maps in the Nav bundle and how the waypoints file is named. You are getting it because you have the NAV bundle.
Another bet it reloading the waypoints after the update will correct the issue because the directory will then we formed under the new firmware naming scheme.