I have a Birdseye image subscription but every time I start my device it gives me an error invalid JNX file. It lets me go on but is annoying. I would like to know a way to identifiy and delete or fix the invalid file without deleting all my images. Any ideas would be apprecieated.
This might not be very elegant, but backing up all the jnx files that are on the device and deleting them one by one should allow you to find the offending BirdsEye.
Delete all JNX files from the unit and reload them onto your GPS from Basecamp "My Collections" folder. Transfer the JNX files to the units internal memory.
Very very disappointed with garmin 810. This product is overpriced and is no good to me as a mountain biker unless i pay another £250 or more for topo maps. To add insult to injury the device is outdated to me. It looks like a nokia phone from the 1990s. It keeps crashing after trying to install birdseye maps. I actually got lost in the french countryside yesterday and had to resort to my phone.
Why oh why did i think that wasting so much money on garmin 810 would improve perfectly decent (and free) mapmyride app with my android phone??? Am sending the garmin back. A load of hype. The company should be ashamed.
I have a Birdseye image subscription but every time I start my device it gives me an error invalid JNX file. It lets me go on but is annoying. I would like to know a way to identifiy and delete or fix the invalid file without deleting all my images. Any ideas would be apprecieated.
This would be a very long and frustrating approach:
This might not be very elegant, but backing up all the jnx files that are on the device and deleting them one by one should allow you to find the offending BirdsEye.
A more sensible approach would be:
Make an archive copy of all JNX files loaded to the GPSr. Clear half the JNX files from the GPSr. If the warning still occurs after rebooting the GPSr, the offending file is on the GPSr, and you must now move half the remaining JNX files on the GPSr to a unique folder on your computer, rebooting each time until the error no longer occurs. When the warning no longer occurs, the faulty JNX file will be in the group you most recently removed. You now have a group of JNX files on the computer that includes the offending file. Now you need to move half the remaining JNX files (from the offending group) on the computer to a unique folder (inside the JNX directory) on your GPSr, rebooting each time until the error again occurs. When the warning returns, the faulty JNX will be in the group most recently moved to the GPSr.
Continue repeating this process until you are left with only a single JNX file, the offending JNX file.
The beauty of this method is that with each and every step, you are able to remove half of the remaining files from the equation, without taking the time to test each individual file, allowing you to locate the offending JNX much more quickly.
Testing a group of 20 JNX files one by one would require you to remove a single file and reboot the GPSr up to 20 times, until the offending file is located.
Using this method with the same 20 JNX files, you would have reduced the number of suspect files to 10 with the first step, 5 after the second step, then maybe two or three on the third, and you will have located the offending file with absolute certainty by the fifth step, probably even sooner.
This method can be used for any potential problem files on your GPSr, such as GPX files that may be preventing it from booting properly.
I was asked a similar question by a customer so referred him to this topic. His solution was very simple:
"Solved the problem by opening the Birdseye folder in windows and deleting several Birdseye JNX files which were not visible when looking through the Base Camp dropdown menu."
