Jump to content

GPSteeve

+Premium Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by GPSteeve

  1. I'm also having a printing problem. I use the Simple (No Logs) option. When I print the page, there is nothing above the "Short Description" except for the IE page header. So cache name, coordinates, size, difficulty/terrain ratings don't print (even the disclaimer don't print ) This also happen when using the browser's print preview. To print the missing parts, I have to change the print size from "shrink to fit" to 90% (size changes with cache page) or hide some images. However some images are needed (for a multi-cache). I use WinXP Pro SP3 with IE Version 7.0.5730.11. Printer is a Canon MF3240 with 2.40 drivers. The problem can be seen on caches GC1F3X3 and GCQ86V. This does not happen on every cache page. Please have a look on this issue. Regards.
  2. FYI, after describing the issue to Garmin, I got the following e-mail. We'll see how long it will take.
  3. I infomed Garmin of the problem (via their website). Since they've made that mistake before, at least, they already know how to fix it. Hopefully, it won't take long.
  4. Tersanyus, you have the same problem I have. I can add the following information (after updating to 2.70 again): - I have Topo Canada installed. However, I also removed the maps (in fact, I removed the memory card). The issue is still present. - When I reach the cache, I get the message "Arriving at..." but the unit is still stuck on compass page. Until I press Stop or Found. I'll inform Garmin so they will (hopefully) find a solution. Thanks
  5. Hello, I updated the unit software (eTrex Vista Cx) to version 2.70 (from 2.60). Since the update, when a geocache is selected as destination, I can scroll through the pages (map, trip, etc.) until I reach the compass page. Then the unit is "stuck" there until I stop navigation. The problem does not happen if I select a normal waypoint (ex. my house). I "downgraded" the software to 2.60 and it's working properly. Did anybody notice the same behaviour?
×
×
  • Create New...