Google Earth & Basecamp
Thu, 02/01/2018 - 3:40pm
 16 years
|
The latest iteration of Google Earth prevents usage of the link in Basecamp from working even if GE is running at the time.
Garmin acknowledges this: https://support.garmin.com/faqSearch/en-GB/faq/content/go8ph...
Garmin's solution is to create a kml file in Basecamp, then open it in Google Earth. Its a feature I frequently use so their solution doesn't work well for me.
The update came automatically. Fortunately I had a backup image of my drive that had been saved just prior to the GE update.
After restoration I changed the GUPDATE service in Windows from automatic to manual.
Another option
From the Command Prompt, and signed in as an Administrator, type the following as applicable and press ENTER:
(Make sure you are in the C: root directory)
"C:/Program Files (x86)/Google/Google Earth Pro/client/googleearth.exe" /RegServer (works with Google Earth Pro in Win 7...10)
"C:/Program Files/Google/Google Earth Pro/client/googleearth.exe" /RegServer (Google Earth Pro in XP)
"C:/Program Files/Google/Google Earth/client/googleearth.exe" /RegServer (Google Earth in XP)
"C:/Program Files (x86)/Google/Google Earth/client/googleearth.exe" /RegServer (Google Earth non-Pro on Win 7, 8.x and 10)
(forum won't allow backward slash so you'll need to change all but the last forward slash (/RegServer) symbols to backward slash)
Note for those not used to using the command line in Windows, the double quotes in all of the examples are critical. They MUST be there and in the indicated places or you'll get an error that the directory name is invalid. It won't harm anything; it simply won't work.
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20
Google Earth Pro Mac.
This probably needs to go into the Mac section. On a Mac, if you will rename Google Earth to Google Earth Pro, then Basecamp will find Google Earth when you choose to view the Data that way.
Frank DriveSmart55 37.322760, -79.511267
Did not work for me
Did it work for you?
Registering Google Earth Pro as described did work up until v7.3.0 of GE. With 7.3.1 the program was moved from Program Files (x86) to Program Files in Windows 10. So, when I first encountered the problem I registered it for the new location.
As mentioned previously, even with Google Earth active Basecamp will not transfer whatever is active to GE.
Thanks for the suggestion and for your many postings
Well ...
Mine works perfectly ...
Where there's a will ... there's a way ... DriveSmart51LMT-S, DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20
GE 7.3.1
My issue appears to be related to properly registering a 64 bit application.
Here is the story:
All three of my machines had auto updated v7.3.1, whereupon I could not get the link to it in Basecamp to function. So, I reverted to 7.3.0. All three are Windows 10, 64 bit machines.
Subsequently Google Earth re-updated itself after I had changed services to manual for google update. The reason was that Google update is incorportated as a scheduled task.
The first time around, GE updated all three to the 64 bit version. This time, one machine updated to the 32 bit version and another to the 64 bit. With the 32 bit version the link works. On the machine with the 64 bit version of GE installed it does not.
Apparently, registering an exe is different for a 64 bit program than it is for a 32 bit. If I enter the following
"C:Program Files/Google/Google Earth Pro/client/googleearth.exe" /regserver into a command prompt it only opens GE.
(Yes, into a command prompt with administrative privileges working from the C: and using back slashes where appropriate.)
I have now installed the 32 bit version of 7.3.1 that had autoupdated to the 64 bit version and everything is back to normal. Also the 64 bit version was removed during the process. Is there any real advantage to using the 64 bit version? If so, how do I register it?