freeday

Montana Wiki --> http://garminoregon.wikispaces.com/message/list/Montana

>>batterie life i had similar results: http://translate.googleusercontent.com/translate_c?act=url&hl=en&ie=UTF8&prev=_t&rurl=translate.google.co.nz&sl=auto&tl=en&u=http://www12345678.wordpress.com/2011/07/03/laufzeitladezeit/&usg=ALkJrhjPCUg8JzdaO-7-rzyVm4No5qD8jw The PowerSave-modus is very useful. On the Oregon, the PowerSave-modus did not make any difference for me.

Thank's, i am using this pointer.

@yogazoo Where did you get these funny pointers?

Pedestrian routing never worked with garmin units (there is a specific minimum speed level which is impossiple for walkers)

42 $ for shipping !!!!!!!!!

Thanks - this is different to the daily logfile from gpsmap 60csx - there was only ONE daily tracklog (96400 points). Six different track segments from the day is nonsense and does not make any sense for me.

Selecting "when full" - i am not sure to get a daily log. Did anyone test this option already? The 60csx does work different than the oregon. 60csx logs automatic daily - if you clear the current log or not - it doesn't matter (i prefer this option because starting a track, i do not like to see the track of the previous journey to the starting point) clearing the Oregon current log - there is NO daily log of the deleted track.

Using the Montana with the following track setup: Track log: Record, show on Map Record Method: time Interval: 00:00:01 Autoarchive: Daily The track is visible for some time (about a hour) on the Display - and then there is no more track line from a specific point(timestamp) Can anyone confirm this BUG, or is it a false setting (i need a track line all the time) Maybe there might be a reason, that the track is saved every 3.000 points to the internal memory as a daily track. I would prefer one daily track with 86400 points like the gpsmap60csx.

here are the same results (click: to "Running time - loading times" on the right side): http://translate.google.co.nz/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=auto&tl=en&u=http%3A%2F%2Fwww12345678.wordpress.com%2F&act=url

Feel free to use this file in http://www.gpspassion.com/upload/comprose.zip or http://resmark.se/gps/garmin_vehicles.zip from http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=78125&whichpage=16 Or is there a specific reason why you do not want to use it. you can also translate a site with google: http://translate.google.de/translate?js=n&prev=_t&hl=de&ie=UTF-8&layout=2&eotf=1&sl=de&tl=en&u=http%3A%2F%2Fwww12345678.wordpress.com%2F

No, it is from the zumo specialists. http://www12345678.wordpress.com/2011/07/02/pointer-wie-beim-60csx/ (Just follow the link to the german naviboard.)

Smaller arrows already exist. You do not have to wait any longer.

Changing the .srf File is a great option to have again the small cursor (pointer) from the GPSmap60 series. I love this trick, and missed this option on the oregon/dakota/gpsmap62 series

My Power button works fine. - Seems, that yout unit is broken. On my unit (i am talking about the hardware) only the batterie back does not fit very well. (you can move it a little bit).

Garmin should give the user an option: autocalibration = ON/OFF

My Montana SQUEEKS - it is the batterie case which makes the noise. Does your Montana batterie case work as designed without any squeek?

GOOD: Nice new unit. It is really waterproof (i mounted the protector-shield under the water which is much easier) Much easier to change settings than in the oregon family (i like the power-menues) great display (much better than oregon) very fast speed compared to gpsmap62 and oregon-series BUT: NO COMPASS calibration possible (failed) In the first 4 hours i had 7-8 CRASHES under different operations (profile change, calculation, map scrolling,...) I hope Garmin can solve this CRASHES within 12-15 months. So, in summer 2012 the unit might work as designed. Overall, the best GARMIN of the 21th century, but crashes very often as every new garmin. Is there a specific email-adress to contact montana-developers? I think, the unit was not tested before rollout.

The same problem on the gpsmap62-series. Garmin knows about the problem - but they never could solve the bug.

Yes, Garmin got all information to correct that bug. But they did nothing.

GARMIN was informed about that bug already on 27 August 2010 (!!!) http://forums.Groundspeak.com/GC/index.php?showtopic=258465&st=0&p=4449619&hl=batterie&fromsearch=1entry4449619 Garmin also was informed about a method to solve that bug. Until now - no update :-(

GARMIN was informed about that bug already on 27 August 2010 (!!!) http://forums.Groundspeak.com/GC/index.php?showtopic=258465&st=0&p=4449619&hl=batterie&fromsearch=1entry4449619 Garmin also was informed about a method to solve that bug. Until now - no update :-(

>>What ver firmware is it on and have the bugs been fixed ? http://garmingpsmap.wikispaces.com/Bugs http://forums.Groundspeak.com/GC/index.php?showtopic=264941&pid=4567809&st=0entry4567809 https://forum.garmin.de/forumdisplay.php?f=219 https://forum.garmin.de/forumdisplay.php?f=218 There are still a lot of bugs, but garmin is working on it and it should be fixed in a few months.

>>Is there a key lock, to prevent keypresses from waking up the screen when the GPS is in my backpack? No, there is no keylock. Garmin has been informed a few months ago, but it looks like they do not want to implement it. >>What does the "power save" mode do for the display? turn display off after the light is turned off (parameter in light setting) >>If I modify a profile, do I need to "save" the changes, before I move to a new profile? And if I create a new profile, does it inherit the settings of the current profile? no save option - changes will be saved automatically copy a profile and the settings should be the same but (!!!) do not invest to much time because currently, there is a bug which sometimes destroys the profile - garmin knows about this bug but could not solve it until now.

We were talking about the unit and had a strange conclusion: Garmin is testing the unit only with a simulator inside the Garmin office. ERROR on Batterielevel (after 2 bars, you do not have half power) ERROR on position (sometimes curious position and curves are sometimes far away from the real road) ERROR on hangup during logging (i had 6 crashes in 2 weeks - so the unit stopps logging and the users does not get any feedback therefore) This should have been solved already (after being a lot of months on the market), but these bugs are still not repaired. What do you thing about?