Hi,
I "had to" install 4.2 on my etrex 30 yesterday.
Basically in preparation for saturday's audax I put a gpx on it (which was fine) and put fresh batteries in it and it wouldn't turn on. Just displayed the garmin logo for about 5 seconds then went off again.
On getting home I discovered that it did exactly the same thing even when I tried to hard reset it by holding down enter and menu and switching it on. Just garmin logo for 5 seconds then off again. So I was completely stuck...
So then I installed garmin express on my windows pc and updated it. At first it appeared that it did exactly the same thing. Wouldn't turn on. But then, I did the master reset combination but held down 'back' as well, and it came on and applied the update.
The only things I think I could have done that it could have taken exception to are:
* I put in (fresh) non-rechargeable batteries when previously it had had rechargeables
* I put a gpx on it that, albeit fully schema compliant and nothing of the sort it hasn't seen before, did have a space at the *end* of its file name before the extension - e.g. "Cambrian .gpx" rather than "Cambrian.gpx"
If neither of those things, then why wouldn't it turn on?
Bit annoying as this is a bit of a dent to its reliability reputation in my eyes.
Can anyone confirm whether the reset procedure is just menu+enter and turn on, or menu+enter
+back and turn on... is the inclusion of back an 'even harder' reset?
Can anyone confirm or deny whether the version of software I had on it before (what it would have come with in august 2012) has a bug that takes exception to file names with spaces before the extension e.g. "Cambrian .gpx" (don't try it just before a ride
)
However, one thing I have noticed about the new version, that I regard as a major improvement to it, is that it now beeps!
After 2 and a half years of being mute, it now makes sounds.
This means proximity alarms are useful, and it stores them as waypoints and can recognise them from (and stores them as) waypoint extensions in gpx.