Best Content of All Time
I have a GARMIN GPS III (not plus), and I had the 1995 problem (mine was showing may) that you seem to have.
I discovered it could be a combination of the Y2K bug, and the End of Week problem. Apparently around in 1999, the way GPS was operating needed to be updated, so they changed a few things in the method. The End-Of Week issue was solved by an update for GARMIN GPS units (including the GPS III).
I found a link at http://home.mira.net/~gnb/gps/gps38.html that (near the bottom) spoke about the end-of-week problem. The Readme file from Garmin (and the Zip file) are linked, but it links to:
I know this says GPS38, but it seems it was a generic problem in many units (one program to fix all), and the software seems OK on my GPS III
I had the serial cable for the PC, so I powered up my GPS, attached it to the computer, and ran the GPSEOW file on my PC. After I got the serial port working in (COM1 - COM4, rather than COM5 I had by default), it connected, and updated my GPS. It now has Jan 2015 (correctly)!
It does need to autolocate after the update, so having an antenna and the sky handy is useful, but that seemed to behave OK after it got a fix.
So, even with my Win8.1 PC, and a USB-Serial adapter in 2015. I can get it to update fine.
Hope that helps someone else.
Are you using a Route and a routeable map? It sounds like you are. If so and you set the via point to " dose not alert" it won't alert the point however it will still alert you to turns. If you go into "setup" then "Tones" then "Early Turn Waring" and "Final Turn Warning" you can set them both to off. You can also go into "Proximity Alarms" from the tone menu.Then turn on "Proximity Tones" you can set tones or turn them off for "Proximity Alarm", "Approaching Proximity Alarm" and "Leaving Proximity Alarm". Then from the main menu go into "Waypoint manager" Select the waypoint you would like to alarm by pushing in on the joy stick. Then push the "menu" button then go into "Set Proximity" You can then set how close you would like to be when it alarms.
I did create a lot of "weeds"........ <<grin>> I just can't help myself, sometimes tangent paths are to irresistible for me.
tried my Nuvi 2797via one of these meters plugged into my USB3 port with a fully charged GPS and it shows 4.85V with a current starting at 0.880A (880 mA) settling down to 770mA.
That could be a hefty drain on many a computer port and it is recommended that the GPS be fully charged before connecting to a PC.
Lowering the screen brilliance to about 50% reduced the consumption to 330mA, this could be a simple solution if power consumption is the issue.
I will do a bit more experimentation as I have experienced many false start attempting Nuvi connect to W10 and just persevered, maybe it is time to track it down.
Software version 7.50 was released this morning for the DriveSmart 55. Maybe it will help your situation.
Just over 14, 15th day's hike was just 9 miles ... first time I did it I had 27 miles on the 15th day so did it quicker this year :)
Hey, OldGeezer, I loaded Ver. 7.50 and now have 2 hours of Bluetooth navigation without a reboot. Yeehaa! That's the longest I've gone with any of the DS 55's. Maybe, it was the fix (fingers crossed). If I get a reboot with the new software I'll post it here.
Well that's a strange question ...
If you know the route from your home to the town centre is there any need for you to worry about this?