I got a few of them from a few digital cameras, still were in the wrapper. Turns out the nuvi 660 handles POI files very well from interchangable SD chips. I've experimented putting important data such as local red-light camera POI files directly in the nuvi ram and larger POI files I don't use often on a SD chip. You can have a lot of POI's on 16MB.
When you 1st turn on the nuvi or push in a chip (if POI's are on an inserted SD chip) it asks if you want to load them in the nuvi ram. I've been saying no (and not checking the box "don't ask me again"). This way the internal ram doesn't get cluttered with the megabytes of POI's I want for a short time. Then if you yank the chip, you only have the basic POI's you really need all the time. Pretty good implementation.
Toe may to, toe mah to...
Personally, I just like loading every POI I can find directly onto my 660 and having them with me all the time. I travel too much to be bothered with adding/removing POIs and, sometimes, my destinations get changed "on the fly", pun intended since I'm a pilot.
Over 100,000 custom POIs and a bunch of mp3 music files in my 660 and I still have around 700 megs left. Don't think I'm going to fill it up anytime soon!
My Tax Data,,,they are Great will hold many years worth...But a 32 mg would be cool with my 650 to keep some Mp3s on..or a couple hundred photos at the size it can show for a slide show..and I would think 32 Mg would be a Bunch of POI...
I can understand that. But, sometimes I want to drive around & find red-light cameras. I want my camera file to come up right after Extras, Custom POI, I don't want to scroll down a hundred files looking for camera while driving. So, in the nuvi ram, all I have is the camera file. That's the neat part, customizable, for everyone's taste.
I know it saves the individual files as an alphabetized list. Just rename your camera file to Acamera or something.
When I'm driving around looking for red-light cameras, I wish clicking Extras could get directly into all the Custom POI's (just camera files when the chip is yanked), bypassing Fodor's Sample Data. I've tried finding the Fodor teaser files on the nuvi 660, they seem to be bundled into the Garmin software.
I found a neat way of finding just the cameras I still need (haven't seen yet), by putting the word NEED in the lines I still need, in the CSV file. Then when on the nuvi, I hit SPELL & enter NEED. Those I already found will not show up.
Btw, individual files are not sorted in alphabetical order on the 660's SD chip (only place I looked). They're random.
Well, if they're random, they're probably in the order you have them in the folder. If that's the case, you can order them however you want. The Nüvi 660 does alphabetize when using the internal memory.
If you load your red light camera file to internal memory. Then explore the internal files ► garmin ► poi you'll see poi.gpi rename this to redlight camera.gpi or any other name you like.gpi
Then if you have other poi data on the sd card, the redlight file is first after "extras" ► "custom poi's" then it's the sd card files.
That's how I currently have mine set up. Redlight files on internal mem and the rest of my poi files on sd card that I keep installed. I've not gone crazy installing every poi file ever created, just the ones I think I might like or need. I also have a bunch of mp3's on the card.
When I update the redlight file I rename the existing redlight_camera.gpi to redlight_camera.gpi.old
then update, and rename poi.gpi to redlight_camera.gpi
if it all checks out delete the old copy.
As far as the sd card and alpha order..use the folder system..
for example on mine I have redlight cameras on internal mem
on sd card costco, discount tire, ihop, starbucks, texas roadhouse, texas wineries
when I go to extras, custom poi's I see:
Then as I press each one I'm given a list of the closest 50 to my current location.
If that isn't alphabetical I need to go back to school..Mindful that Redlight Cameras is on internal mem.
There's no need to argue about this, life's too short alrerady. Besides, we both have different machines, different firmware... Here's a link to what I see, after the internal camera file:
Only offering suggestions to a proposed...I wish...
and ...how to..
Suggestions may help someone else, who is not posting but only reading.
This would be quite boring if each poster asked a question, then answered it themselves in the same post.
Yup, no argument here. And CaptNorm, yes, we do have the same machines. What firmware are you running? I'm running the latest 4.2 and really like the faster screen refresh.
I hate to start a new topic, but will since we're talking about firmware. I've downloaded (not w/web updater) new firmware & installed it on the 660 just fine. I usually don't keep the GTM 20 traffic receiver plugged into the 660 when on the pc, but recently did. Then ran web updater. Only then did it upgrade the firmware. Actually downloaded it & incorporated it on the next boot. Haven't tried it yet.
That's strange. I never bring the traffic receiver/charger inside and every update, including traffic updates have loaded into my 660 just fine. However, I'm using webupdater, which has always worked fine for me, vice the manual method you did.
The OS firmware takes effect immediately on the next reboot. The next time it's connected to the traffic receiver, it installs the traffic update that was previously loaded into the 660 with the OS update.
That's what I was saying, if I just install the update with out web updater, I'm pretty sure I didn't get everything, just 660 firmware. With web updater, I got the traffic receiver also.
terms | privacy | contactCopyright © 2006-2020