GPSFileDepot.com
 

News:

Welcome to GPSFileDepot!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - 2Wolfes

#1
Ok, managed to get the command prompt up (I said I wasn't the most "techy" apple in the crate  :o).  Anyway, ran "set" and yep, there's the "ALLUSERSPROFILE=C:\ProgramData".  But I can't find that directory using the default file explorer on the PC.  I reckon it's hidden from folks like me.  I noticed when I installed the FL topo, that it didn't give me an option of changing it's destination - it just ran right through and loaded.  And BaseCamp found it just fine.  So went looking for it using the "find" feature of the file explorer.  and it found it in the C:\ProgramData directory!! 

My speculation -

The Windows installer for the FL map was tweaked to use the "ProgramData" directory for the maps (to match change the Garmin made with Vista - something you pointed out  :D) .  The others I've installed are and earlier version that us the "Program Files (x86)" directory - the pre-Vista destination.

You knew what ailed me early on ("Garmin changed the install location for maps with the introduction of Windows Vista, so I suspect you are using some old maps and the installers are using the locations that worked in Windows XP.")  I just needed to make sense of that change.  I'm a newb at all this and a visual learner.

My next project will be to reload the maps other than the FL topo and change the destination folder to "C:\ProgramData\mapname" and get rid of my "workaround".

Interesting to note, when installing the "MyTrails" overlay the default destination is "C:\Garmin\MyTrails".  Must be why I "figured out" where to sent the other maps . . . ???

Thanks so much for your comments and insight.
#2
docboyd1 - I had the same problem loading maps to my Oregon 650.  The FL map worked just fine, none of the other maps (SE US) could be found by BaseCamp.  When loading the AL topo, a screen pops up giving a destination folder of "C:\Program Files (x86)\altopo11" (this is the third screen of the installation process).  Just change the destination to "C:\Garmin\altopo11" (I used "Alabama topo11" just looked a little cleaner).  Map should load just fine.  Restart BaseCamp (apparently it only looks for loaded maps when it initially loads - another of the nuggets I've learned on this site).  Your AL topo should show in your BaseCamp Maps tab as "altopo11".

Hope this works for you.  I was able to use this workaround to get all the maps on my pc and into my Oregon.
#3
So sorry about the multiple threads.  I'll do better . . . :-[

"Garmin uses this location for map installation, and a properly written third party installer can do this too.

C:\ProgramData\Garmin\Maps  "

My Win10 system doesn't have the "C:\ProgramData" subdirectory.  As I haven't installed a Garmin map (one put out by Garmin) on my system, I can't speak to what they use for a location on a Win10 system.  Regardless, by directing the maps from this site to "C:\Garmin\mapname" BaseCamp finds 'em and installs 'em.  And that makes me happy.   ;D ;D
#4
Map Making Support / Re: map_install_x64-x86.nsi
March 11, 2016, 07:34:20 AM
"Can you try the Arizona topo. I tried a different version with that installer. And try firemann59's idea above. Thus far I cannot recreate the problem you all are experiencing."

Just d/l'd and installed the Arizona topo.  Again, during installation changed the default destination of C:\Program Files (x86)\Arizona Topo to C:\Garmin\Arizona Topo.  Worked like a champ.

Now that it's on my GPSr, I reckon I'll need to take a trip out that way . . .  8) 8)
#5
Map Making Support / Re: map_install_x64-x86.nsi
March 11, 2016, 07:23:36 AM
" Have you tried installing the maps as an administrator?"

I have a window pop up and I have to install as an administrator.  My conjecture would be that the Win10/BasaCamp 4.6.2 combination requires it all to be in the C:\Garmin subdirectory vice the earlier default of C:\PregramFiles(x86) subdirectory.  Unfortunately, this is one of those "I don't know why it works but it does" items.
??? ???
#6
Thanks for your response.  I was able to resolve the issue with redirecting the installation of the maps to C:\Garmin (the installers ask fortunately).  Here's a note I posted earlier today about the same issue.

===================================================

After much head scratching, weeping and gnashing of teeth, I started playing around with the install instructions (I'm not near techy/nerdy enough to be comfortable with this).  I noticed that the topo maps I was working with wanted to install to c:\programfiles(x86)\topomapname.  Since the Garmin GPSs require the compiled map to be in the *:\Garmin subdirectory to be recognized I just changed the location in the setup screen to c:\Garmin.  That maps went there (were compiled there?) and Basecamp found them right away. Don't know if it's a Win10 thing or a BaseCamp thing but it works now.

So, in a nut shell - Win10 system, BaseCamp 4.6.2 --

Make sure the maps install to to C:\Garmin.  You'll be asked where you want them to go during the installation process.

Oh, and now I see that Firemann59 posted the same solution. 

I have spent WAY too much time on the forums these last two days.  There's some great information here.  And I can actually understand some of it.

Thanks to all who ask and those who share their knowledge.
Modify message

===================================================
#7
Map Making Support / Re: map_install_x64-x86.nsi
March 11, 2016, 07:09:09 AM
After much head scratching, weeping and gnashing of teeth, I started playing around with the install instructions (I'm not near techy/nerdy enough to be comfortable with this).  I noticed that the topo maps I was working with wanted to install to c:\programfiles(x86)\topomapname.  Since the Garmin GPSs require the compiled map to be in the *:\Garmin subdirectory to be recognized I just changed the location in the setup screen to c:\Garmin.  That maps went there (were compiled there?) and Basecamp found them right away. Don't know if it's a Win10 thing or a BaseCamp thing but it works now.

So, in a nut shell - Win10 system, BaseCamp 4.6.2 --

Make sure the maps install to to C:\Garmin.  You'll be asked where you want them to go during the installation process.

Oh, and now I see that Firemann59 posted the same solution. 

I have spent WAY too much time on the forums these last two days.  There's some great information here.  And I can actually understand some of it.

Thanks to all who ask and those who share their knowledge.
#8
Having the same issue - get exactly the same results..No unlocked maps were found for this device... (Oregon 650)

This is a new Win10 PC.  D/L'd newest version of BaseCamp (4.6.2)  Unable to install any maps from gpsfiledepot.com.  I have 12 state topo maps already installed (from a few years ago using an older PC).  BaseCamp doesn't recognize as being on the GPS (Oregon 650).  The files are on an SD card - can move the card to another 650 and it works just fine.  Just can't anything to install and be recognized.  Arghhhhh. 

Any ideas.  I've done the help files, the tutorials, tried reinstalling the maps I already have installed, tried installing new maps - nothing works.  At all . . .

#9
Map Making Support / Re: map_install_x64-x86.nsi
March 10, 2016, 08:35:06 AM
Sigh, absolutely CANNOT get Basecamp to recognize any  maps - either dowloaded/installed to new PC running Win10 or the maps previously installed on Oregon 650 using an earlier PC (Win 8.1).