Well, if the new fw screws up your gadget so bad that it doesn't work then how will you do the downgrade to make it work again? I say don't fix it if it aint broken cause the fix might break it anyway. Anybody remember Catch-22? :eek:
Well, if the new fw screws up your gadget so bad that it doesn't work then how will you do the downgrade to make it work again? I say don't fix it if it aint broken cause the fix might break it anyway. Anybody remember Catch-22? :eek:
One might expect software releases to show improvements over earlier versions and one might expect regression and beta testing to have been carried out prior to release, unfortunately the current view expressed here and elsewhere is that 2.7 works (for save track) whereas 2.8 and 2.9 don't.
I've tried it out. Its supposed to have solved 'save track' problem and it doesn't.
Garmin: ***yawn***.
You dropped the ball on the Dakota (2.80/2.90) and Oregon (3.30). Better hurry up and fix it, the buying season is open and you'll soon have a lot of pissed off customers like me.
Dakota: 2.70 works, 2.80 clearly does not, and one vote now says 2.90 isn't much better. :confused:
