CDS231

Maybe I am a day late and a $ short but a new update for the 700 series Nuvi. Hope this is an answer to the only frustration I have ever had with my 750 and this excellent macro. * Corrected shutdown issue associated with an active proximity alert or tour guide alert. Change History Changes made from version 3.10 to 4.10: * Improvement in MAD Maps performance. * Added Australian traffic support. * Corrected reboot issue while installing language guide at power up. * Corrected shutdown issue associated with an active proximity alert or tour guide alert. * Support for more GPI files. * Fixed an error in MSN news reports where a report could be lost.

I haven't checked in a couple of weeks but does the Tourguide feature still lock up the 700 series Nuvi's? I know it is on the Garmin side of things and would really enjoy this feature. With the last Nuvi update my 750 was still locking up more than 50% of the time. Thanks.

Hint.....you don't need no stinkin hint.

Make sure the unit is in Mass Storage mode. If you are just powering the unit with the USB cable this will not work.

Still crashing my 750. Anybody else?

Before the 2.3 upgrade I was seeing around 35-40 foot accuracy but still finding caches with very good readings for the final destination. After the 2.3 upgrade I am seeing 15-20 foot accuracy, picking up a WAAS reading for the first time and still zeroing out at a final. Just to convince myself to rely more on the unit and feel confident with the Oregon I went and found around 6 benchmarks. After that I feel that it may not be quite as accurate as the 60 Csx, but it is almost there. For someone who has found a couple hundred caches and knowing what to look for on regular size hides it should be no problem at all. I love the touch screen and do not feel I am handicapped by the screen brightness. Yes, I am starting to believe in the unit and just wondering what Garmin will bring out next.

and from the Garmin site. I'm done https://buy.garmin.com/shop/shop.do?pID=13424

News about it from this side of the pond. http://tinyurl.com/64t8bg

Garmin introduces new unit http://www.prnewswire.co.uk/cgi/news/release?id=233097

The screen reminds me very much of the one I have on my Garmin Nuvi 750. I have a screen protector on it and it does not effect the operation. I plan on putting one on my Oregon when Zagg makes them available. In regards to the screen brightness I have found it to viewable in full sun which to me is better than a Colorado. That was the main thing that kept me from going with it.

Yep. Do NOT use the tourguide feature on a 7xx series, until garmin fix it. Your machine will lock up on numerous occasions! IN fact if you are unlucky when you switch your 7xx on, and it is inside a tourguide radius, you might not be able to get to the map page before it crashes!! Nasty vicious circle. It's an ugly bug..... Thanks for the confirmation on the Garmin issue.

Has anyone else had any problems with the macro locking up their Garmin Nuvi? I have a 750 and today on several occasions it locked up and I had to turn it off and on. I was running the TourGuide feature with 2000 feet for proximity. I remember reading something in pilotsnipes page about Garmin needing to update a software feature. Is this the same thing?

Wonderful macro and I really like it since I now use the NUVI instead of a laptop for road trip caching. Question? Is there any way an individual can change the Traditional and the Multi cache to the regular gc.com icons? I find the current ones fairly large and different than the usual ones. I also have the custom icons on my Garmin 60csx and would enjoy the same icons on both units. Again, great macro and thanks for all of your work.

Yes, I have just started having this very same problem. I have been using the 60csx for 9 months and with the last update (3.10) it started doing the same thing with the pointer disappearing. For me is does not matter what function I was doing previously. This is happening after the compass is calibrated also. I calibrate everytime I change batteries. Also, I have had the pointer being off 180 degrees (backwards) and have had to find a cache that way.