Basecamp Shenanigans

[Berin]

I wanted to clear out some waypoints and routes from my last East Europe trip, to make the Nav IV easier to use day to day in the UK. So I fired up Basecamp, connected the unit, selected the device internal storage and then selected all the routes/waypoints I wanted to delete.

But - no delete option on right-click, and no way to modify even the name of the route/waypoint. I can delete/edit if the waypoint is in the Basecamp library, though.

So, I saved all the stuff I wanted into the Basecamp library, disconnected the unit and manually deleted all of the routes and waypoints, verifying that they have gone.

Reconnected to Basecamp, look at internal storage on the device - and everything is still there! Disconnected again, nothing shows up directly on the device!

In the middle of this, Basecamp tells me 4.1.0 is available, so thinking it may be fixing some bugs I downloaded and installed it, and it crashes every time the device is connected.

Rubbish!

 

[JoeBiff]

I had trouble a while ago deleting stuff from the 660 & BC.

Try going to Zumo:\gpx\TEMP.gpx. in your hard drive structure on the PC.

Sometimes BC throws data into this little-known area of your 'puter, and can't find it again when the time comes to delete.
Obviously, make sure you've got a back-up of other important data you want to retain before treading this path, but it worked for me.

I'm afraid I can't make any suggestions with the BC update - though the possibility remains if BC was doing a background download/update/install, it may have corrupted itself, somehow whilst you were working on the deletes.

HTH
JB

 

[Berin]

Did that, thanks, BC now only sees the stuff on the device.

I had to go back to BC 4.0.5, though, 4.1.0 still crashes. After some discovery work I figured out the Mapupdater put all of CN Europe 2013.3 on the SD card. It left the AdriaRoute 4.1 I had on the device alone.

I think I will run it through an Express update tonight to see what happens.

 

[JoeBiff]

I've read of others having trouble on Mac & some PC versions with the new BC update.

There was also the suggestion that removing file 006D135900.gpi from the POI folder, solved the glitch.
Maybe, if your system has that file, you could delete it, and all should be well??

HTH