After hearing from a user of my Garmin map that BaseCamp had failed to load it into her etrex, I tried the same using my Windows BaseCamp and got "There is a problem with your Big Sur Trailmap installation. Re-install the product and try again." Of course, re-installation gave the same result. My map is complex, with cgsmapper compiles (of contours and streams), with mkgmap compiles (of trails, boundaries, and other data), and with TYP files - and it routable. I use NSI to produce an installation file which does install and display correctly in my BaseCamp (and is routable there). Many years ago, when first creating the map, I was able to successfully install the map to my GPS using BaseCamp. But since then my usual procedure has been to install the map by simply writing the corresponding IMG file to the GPS Garmin directory, not installing via MapSource (since updating MapSource is a slow procedure).
There have been considerable changes from the initial map (e.g. inclusion of a wildfire polygon) and I don't know at what point the BaseCamp problem developed. The error message is obviously not helpful. The only way I can think of trying to solve this is by successively removing elements from the map (e.g. first the wildfire polygon, then the trails, then the contours, ...) until it works. That would be very time consuming and I'm don't think I can devote that time. Still, I want to make a quick attempt at finding a solution. So my question is: is there some method (e.g. a software package) of testing the installation executable, one which would provide more useful error messages?
And if anyone has advice on how to best proceed in ferreting out the problem, I would love to hear it!
Jack
There have been considerable changes from the initial map (e.g. inclusion of a wildfire polygon) and I don't know at what point the BaseCamp problem developed. The error message is obviously not helpful. The only way I can think of trying to solve this is by successively removing elements from the map (e.g. first the wildfire polygon, then the trails, then the contours, ...) until it works. That would be very time consuming and I'm don't think I can devote that time. Still, I want to make a quick attempt at finding a solution. So my question is: is there some method (e.g. a software package) of testing the installation executable, one which would provide more useful error messages?
And if anyone has advice on how to best proceed in ferreting out the problem, I would love to hear it!
Jack