POI Loader error

 

Never had this happen before. POI Loader always worked A1. But today when I am trying to install the RLC POI on the 855 I get an error message "There was an unexpected error during the transfer of the custom POI file".

Then when I check the POI folder on the GPS the file name is there but ZERO Kb, nothing,nada.

I already uninstalled POI Loader and re-installed it, same error problem still exists.

I have also rebooted the computer.

I have sox.exe installed in the POI Loader program.

Any idea what the possible problem my be?

Thx

--
Nuvi 2797LMT, DriveSmart 50 LMT-HD, Using Windows 10. DashCam A108C with GPS.

yes

There is a problem with the RLC file. That's what POI Loader told you. I believe there is/are a few locations without coordinates.

--
Illiterate? Write for free help.

File

So what you are telling me is that the NEW RLC file is flawed?

I will try the previous version to see if it loads.

Thanks

--
Nuvi 2797LMT, DriveSmart 50 LMT-HD, Using Windows 10. DashCam A108C with GPS.

Muchas gracias, thank you, thank you

Box Car wrote:

There is a problem with the RLC file. That's what POI Loader told you. I believe there is/are a few locations without coordinates.

After a complete re-install including sox.exe I can report that the previous RLC file loaded perfectly.

Thanks BC

--
Nuvi 2797LMT, DriveSmart 50 LMT-HD, Using Windows 10. DashCam A108C with GPS.

Both files

Both files seem to have an error - I am looking.

Edit: was because I was trying to load to one of my "computer" based nuvis. Tried another "computer" clone and both new camera files loaded. Tried my 765 and both new files loaded. I will have to research why the 2GB "F:/" does not work anymore - because it was working recently. The message POI Loader gives is "There was an unexpected error during the transfer of the custom POI file." I read this message as indication that POI Loader successfully read and compiled the custom POI file but had a problem in the "transfer" of the compiled file to the "device". Since it works on the 765 and on the "stick2595", it seems to be the "F:/".

Note that I did a Revo Uninstaller "uninstall" of POI Loader (before realizing that the problem was with the "transfer") and then a reinstall from my hard drive (that is - I did not do an new download of 2.7.3.0). As a matter of interest, Revo left the folder C:\Program Files (x86)/Garmin/POI Loader on my computer because, I think, that it contained "sox.exe" which was not part of the Garmin install originally.

If I can determine what is causing the "transfer" problem, I will post a report. Isolating it may be a problem.

Another Possible Solution

Why not just have POI Loader send the file to the computer rather than the Nuvi.

I always send to the computer to all my saved POI files folder, then transfer the file to both my Nuvi's. If it transfers the file to the computer, then we can rule out any errors with POI Loader in creating the file.

--
Nuvi 2460LMT 2 Units

Good Suggestion and solution to Transfer

muell9k wrote:

Why not just have POI Loader send the file to the computer rather than the Nuvi.

...

Right you are.

Actually the first thing we should have said was that it was highly unlikely that there was anything wrong with the poi-factory camera files.

When I first attempted to see if there was a problem with the files, I used my 765 clone (which is a SD card in the card reader of one of my printers - named "Memory Card (F:\)). I use that card for the same purpose that you suggest using the "computer". The reason I prefer the card is that, since it has a GarminDevice.xml file, POI Loader will find it and I do not have to "browse" to some place on my computer.

However, that said, in debugging the problem that Melagueman reported originally, I should have immediately switched and tried the "computer" option of POI Loader. When that worked, I would have been given a clue.

OK - now to report that my "Memory Card (F:/)" 765 clone had somehow become "Write Protected" - which I found out by trying to access the card with Windows Explorer and delete some of the .gpi file already on it. I removed the card and toggled the write protect tab switch on the side and reinserted it. It now worked. How it became confused is one of those little computer mysteries we never solve.

So - my guess is that Malequeman may have been putting his Custom POI file onto his "card" rather than his 855 and the card had become write protected.

Hopefully Malequeman will tell us what happened.

I am noticing that POI Loader seems to have three distinct phases -"Reading data files", "Writing databases" and "Initializing transfer". You see this clearly when you have enough POI files to cause POI Loader to have to do enough work for the messages to appear. Even with the camera files (6600 or so locations), you have to look close to see the messages appear.

LOL, my old internet

I could read War and Peace while it was loading