Update
Fri, 07/18/2025 - 9:30pm
 |
    18 years
|
About a year ago, I posted that I was having problems with POISync, and having it corrupt numerous POI's with blank lines. I have since discovered that the problem may be with Java. POISync requires Java version 1.6.0_17. I am in the middle of installing me new Dell PC, with Windows 11, so I will insure I have the latest Java installed when I get around to testing POISync again.
Java version
I haven't worried about Java versions for ages so maybe I'm worrying about what may be a non-problem.
But I base my worry on a related GPS software issue in the past. Garmin's POI Loader was designed to offer custom audio alerts using mpg audio files. It was found that adding the sox.exe file to the POI Loader's folder would also allow wav audio files to be used with Windows PCs. (Apple products are able to use use mpg and wav audio alerts for Garmin Custom POIs without sox.exe.)
Both POI Loader and sox.exe have undergone numerous version updates over time, and in 2011 some Windows users, those with a newer sox.exe, when they tried to load custom WAV audio alerts, experienced really odd issues. See:
http://www.poi-factory.com/node/33887
but you'll have to wade through the thread to near its end to find the solution that POI Factory member Evert found. The issue was that starting with a POI Loader version first offered in 2011, only sox.exe 14.0.1 would work with POI Loader to allow Windows users to have wav audio files. To muddle things further, sox.exe at one time had a version 14.1.0 which wouldn't work with POI Loader yet could easily be confused with the correct 14.0.1.
In your post you mention that POISync requires Java 1.6.0_17 but then state you will make sure to install the latest Java issue. I worry that POISync conceivably could require the 1.6.0_17 and if it's an older version, a newer Java may fail for you just as a newer sox failed with POI Loader. Keep this in mind and if you have a problem, try to find the known-to-work Java version files.
Have fun.