allory

Garmin Communicator Plugin for Mac version 4.0.1.1 Beta https://forums.garmin.com/showthread.php?t=25160 Fixes an issue that causes some of the transfers from geocaching.com and opencaching.com to fail.

eXplorist® 310 Version 1.18 Upgrade Wizard Software Improvements Added support for Fish & Hotspot Maps Windows - http://support.magellangps.com/support/index.php?_m=downloads&_a=viewdownload&downloaditemid=324 Mac - http://support.magellangps.com/support/index.php?_m=downloads&_a=viewdownload&downloaditemid=323

Dakota (WebUpdater) software version 5.20 as of February 20, 2012 http://www8.garmin.com/support/download_details.jsp?id=4527 Changes made from version 5.10 to 5.20: Improved GPS response at low speeds

GPSMAP 62/78 (WebUpdater) software version 3.90 http://www8.garmin.com/support/download_details.jsp?id=4995 Changes made from version 3.80 to 3.90: Added symbol filtering to FIND > Waypoints and Waypoint Manager Improved GPS response at low speeds Fixed daylight saving time issue in Sun and Moon application Fixed issue that could occur when restoring map zoom level defaults Fixed issues with support for Canada BlueChart g2 maps

eTrex 20/30 software version 2.61 Beta http://www8.garmin.com/support/download_details.jsp?id=5557 Changes made from version 2.60 to 2.61: Improved GPS response at low speeds

It does not.

I'm certainly not going to recommend geocaching with the 295W, but not only does it have a compass page, it has a real 3-axis compass.

You should be able to use the method outlined on the Dakota wiki page. http://garmindakota.wikispaces.com/Versions

Dakota (WebUpdater) software version 4.90 http://www8.garmin.com/support/download_details.jsp?id=4527 Change History Changes made from version 4.70 to 4.90: Added Photo Viewer application (go to Setup -> Main Menu to add to the current profile) Improvements to the geocaching experience. See TrailTech (http://garmin.blogs.com/softwareupdates/2011/09/improved-geocaching.html) for more information. Updated the Geocaching - Nearest dashboard Fixed a potential hang on startup when importing large numbers of waypoints, tracks, routes, or geocaches Fixed issue with very long geocache descriptions Fixed shutdown when reviewing certain geocache descriptions Fixed issue where some auto-archived tracks would be named in English regardless of user language Fixed issue that could cause some geocaches to not import Fixed issue with track log recording while using the stopwatch Modified default map trails to appear as dashed red lines

http://www8.garmin.com/support/download_details.jsp?id=5553 Changes made from version 2.30 to 2.40: Improvements to the geocaching experience. See TrailTech (http://garmin.blogs.com/softwareupdates/2011/09/improved-geocaching.html) for more information. Improved behavior on startup when importing large numbers of waypoints, tracks, routes, or geocaches Fixed issue where the progress bar would not display any progress when importing waypoints, tracks, routes, and geocaches Fixed issue with very long geocache descriptions Fixed shutdown when reviewing certain geocache descriptions Fixed issue where some auto-archived tracks would be named in English regardless of user language Fixed issue with track log recording while using the stopwatch Fixed potential shutdown while scrolling through Garmin Connect photos Fixed minor graphical issue with the backlight slider on the status page Modified default map trails to appear as dashed red lines

The bike mount is definitely different than my old Vista mount: https://buy.garmin.com/shop/shop.do?pID=11411 I had bought one for my Dakota and it works just fine with the eTrex 30. Never had a suction cup mount for the Vista, but what I'm using for the Dakota and eTrex 30 looks just like the bike mount above except that it has a socket for the ball joint on the standard nuvi style suction cup. What I found was just the part that attaches to the eTrex in this mount (https://buy.garmin.com/shop/shop.do?pID=15428) and only cost ~$10. I don't know whether it would work with your existing suction cup. It does need the ball joint. The differences that I'm remembering between the 20 and 30 are the compass, altimeter, and wireless data transfer. The compass and altimeter are nice, but not critical (though geocachers sometimes think the compass is). The wireless transfer is for moving a cache or waypoint between units, playing with chirp enabled caches, and the heart rate monitor and cadence sensor. I don't know anyone who uses those, but can see where they could be handy for some.

A couple of short answers. The bicycle mount and suction cup windshield mount is the same as for the Dakota/Oregon series. They work quite nicely. Why the eTrex 20 instead of something else? Smaller, lighter, and less expensive than the 62 or Oregon. More familiar interface (eTrex-like) compared to the Dakota. Better daylight screen than the touch screen models. I have older eTrex, eTrex 30, and Dakota 20. Love them all, but looking like the eTrex 30 may become the new favorite.

This is the reply I got from Garmin support this afternoon. Haven't had a chance to play with it yet. "With the older eTrex units it was possible to select segments from multiple mapsets and send them all to the device at one time and you could see each one and enable or disable them as needed. With the new memory system in the eTrex 30 you would need to transfer the map segments separately for each type of map and rename the file in the device to something other than "GMAPSUPP.IMG" before sending over the next set of maps. In other words, load the TOPO maps first and select the segments you want on the device and send them over. Navigate to the "GARMIN" folder in the card or device memory and rename the "GMAPSUPP.IMG" file to something like "National" or something similar. Then load the other maps and rename them in the same way. The last map you send would not have to be renamed."

This is basically because the eXplorist 310 doesn't have a compass. It has a page which looks like a compass which will indicate the direction you are, or last were, moving. It sounds like yours is working exactly how it was designed to work.

My memory from the Dakota update last week is that I just imported (transferred) the waypoints, etc. into BaseCamp, applied the update, then exported them back to the Dakota. Seemed to work. I think it did create a new GPX folder.

Oregon x50 (WebUpdater) software version 5.00 http://www8.garmin.com/support/download_details.jsp?id=4523 IMPORTANT: if upgrading from a software version less than 4.80 you must follow these steps for future BaseCamp Compatibility: If you are a user of BaseCamp now, or plan to be in the future, you must follow these steps to ensure your data is protected during this software update: - Connect your handheld unit to a computer and launch BaseCamp. Transfer all tracks, routes and waypoints to BaseCamp. - Delete the /Garmin/GPX folder from the handheld's mass storage. - Update the handheld's software via WebUpdater and reboot the handheld. - Reconnect the handheld to a computer and transfer your data from BaseCamp back to the handheld. Changes made from version 4.80 to 5.00: Modified default map trails to appear as dashed red lines Fixed issue where geocache icons would sometimes not draw on the map while using Garmin GB Discoverer™ maps

Nothing for the x00 Oregons yet. Yes on the Dakota, Montana, X50 Oregon, and 62/78.

The 310 at that price seems like a good deal to me. I've been playing with one for a couple of months using maps from maps4me.net. Because of the lack of a memory card slot you are limited in how many maps you can add, but that isn't really a problem. The 310 comes with a serious street level map rather than the type of asemap which is so common on handhelds. The maps4me site requires a registration fee of about $15, but you can fit a couple of states worth of topo maps in the 310's memory if you want.

I don't have any experience with either model, but would like to point out that maps4me.net has a pretty good collection of topo maps for the Magellans. Not as comprehensive as the gpsfiledepot.com collection for the Garmin units, but its a start. Also, with the latest version of VantagePoint Magellan has digital raster images available for the newer units (similar to Birdseye from Garmin).

http://support.magellangps.com/support/index.php?_m=downloads&_a=viewdownload&downloaditemid=283

http://support.magellangps.com/support/index.php?_m=downloads&_a=viewdownload&downloaditemid=282

http://support.magellangps.com/support/index.php?_m=downloads&_a=viewdownload&downloaditemid=281

Endura GPS 1.5 software update http://www.lowrance.com/Downloads/Product-Software-Updates/Endura-Software-Update/ Key 1.5 Update Enhancements 15-30% Faster startup, more responsive performance and better battery life New Zoom Indicator Bar and Cursor 'crosshairs' graphics Significantly improved GPX file handling including new 40MB capability from past 3MB limit New tools: Area Calculator, Waypoint Averaging, Waypoint Projection New funtionality: Screen Capture, ability to turn off the Navigation Arrival Alarm (Destination Reached alarm and message), Delete All for data file categories, Geocache icon display options for map screen

Dakota (WebUpdater) software version 4.30 http://www8.garmin.com/support/download_details.jsp?id=4527 Changes made from version 4.10 to 4.30: Fixed issue with the color of the line at the top of the elevation plot. Fixed issue where custom POI images would not show up in the review page. Fixed occasional issue related to the alarm clock.

I have a Dakota rather than an Oregon, but have been using it with a mac and both free and paid maps with no problem. The first thing you should do is make sure your Oregon has the most recent version of the firmware (4.20). If you haven't already, go to http://www8.garmin.com/macosx/ and get at WebUpdater. One of the recent fixes was 'Fixed problem with certain custom maps'. There was a version where even free maps with no unlock code would endlessly ask for one. If that doesn't help let me know which map you're trying and I'll see if it works on my Dakota. There's at least some possibility that there's a problem with the map.