Bookmark this page:
If you were Registered and logged in, you could reply and use other advanced thread options
Registry entries for Mapsource and the mapsets is another issue. As you may
recall a few yerars ago some map de-installs produced a registry error in
Mapsource.
This was a big problem after de-installing some maps. The next time you ran
Mapsource you got a error which said Mapsource had an error and had to be
reinsatlled.
Of courcse this meant a new reinstal with all the mapsets you had. I
attributed the error to a registry problem. After getting a Mapsource error.
I ran a registry cleaner.
It identified and corrected the registry entries and Mapsource then ran
normally without a re-install.
There were some emails floating around a few years back which explained how
to fix these registry erros manually.
This happens for the same reason most registry problems occur, poor
programing.
The program deveoper in the de-insall routine does not perform a clean
removal and leaves some garbage behind in the registry.
Now when you do a ReverseConvert and delete the mapset install files in
C:\Documents and Settings\All Users\Application Data\GARMIN\Maps
there are regsitry errors created because there are some registry entries
which pointed to these files even though the progam does not need them any
more.
I have found these entries again with a registry cleaner and deleted them.
Hope that explains a little more of what is going on
Harold Muller
| Registry entries for Mapsource and the mapsets is another issue. As you
may
| recall a few yerars ago some map de-installs produced a registry error in
| Mapsource.
| This was a big problem after de-installing some maps. The next time you
ran
| Mapsource you got a error which said Mapsource had an error and had to be
| reinsatlled.
| Of courcse this meant a new reinstal with all the mapsets you had. I
| attributed the error to a registry problem. After getting a Mapsource
error.
| I ran a registry cleaner.
| It identified and corrected the registry entries and Mapsource then ran
| normally without a re-install.
| There were some emails floating around a few years back which explained
how
| to fix these registry erros manually.
| This happens for the same reason most registry problems occur, poor
| programing.
| The program deveoper in the de-insall routine does not perform a clean
| removal and leaves some garbage behind in the registry.
|
| Now when you do a ReverseConvert and delete the mapset install files in
| C:\Documents and Settings\All Users\Application Data\GARMIN\Maps
| there are regsitry errors created because there are some registry entries
| which pointed to these files even though the progam does not need them any
| more.
| I have found these entries again with a registry cleaner and deleted them.
|
| Hope that explains a little more of what is going on
|
| Harold Muller
|
|
|
| > | The current 6.15.6 version of MS-T&WPM is not ony able to read
| > Metroguide
| > in
| > | the c:\garmin folder,
| > | it also is able to read most other third party maps which I have
placed
| > Metroguide
| > in
| > | the c:\garmin folder,
| > | it also is able to read most other third party maps which I have
| > in
| > | the C:\garmin folder.
| > |
| > | As you have probably figured out after you run the ReverseConverter
and
| > | the C:\garmin folder.
| > |
| > | As you have probably figured out after you run the ReverseConverter
| > | create the new files in C:\grarmin,
| > | you can delete new format install files in C:\Documents and
Settings\All
| > | you can delete new format install files in C:\Documents and
| > | Users\Application Data\GARMIN\Maps,
| > | version 6.15.6 still finds the files it needs
| > |
| > | It is a major irritant for those that use nRoute because it is unable
to
| > | version 6.15.6 still finds the files it needs
| > |
| > | It is a major irritant for those that use nRoute because it is unable
| > | find any maps in the
| > | C:\Documents and Settings\All Users\Application Data\GARMIN\Maps
| > location,
| > | but has no problem with them once they are ReverseConverted and moved
to
| > | C:\Documents and Settings\All Users\Application Data\GARMIN\Maps
| > location,
| > | but has no problem with them once they are ReverseConverted and moved
| > | c:\Garmin.
| > |
| > | The long range Garmin plan appears to be to drop nRoute (already
| > happened),
| > | get those that want it to buy Garmin Mobile PC a purchased program.
| > | Garmin Mobile PC then handles each locked map set as a new install to
| > Garmin
| > | Mobile PC with it's own unlock key.
| > |
| > | You then have to purchase two unlock keys, one unlock key to use the
| > map
| > on
| > | you handeld GPS
| > | and another key to use it on Garmin Mobile PC.
| > |
| > |
| > | Harold Muller
| > |
| >
| >
| > Thank you Harold,
| > This whole *hey it ain't compatible anymore* scenario is so typical!
| > I have taken note of all the 1st hand experience offered me in this
| > thread,
| > and when CNNA 2010 arrives I will put all this wonderful knowledge into
| > play. (and of course will inform this group)
| >
| > As far as creating new folders, etc. to preserve a working program
| > between
| > MS 6.13 and MetroGuide v.7 is concerned (for my 76s),
| > my major concern involved how installing a new program (CNNA 2010) would
| > affect the existing Windows registry.
| > A search of same revealed that the only significant issue I could see
was
| > |
| > | The long range Garmin plan appears to be to drop nRoute (already
| > happened),
| > | get those that want it to buy Garmin Mobile PC a purchased program.
| > | Garmin Mobile PC then handles each locked map set as a new install to
| > Garmin
| > | Mobile PC with it's own unlock key.
| > |
| > | You then have to purchase two unlock keys, one unlock key to use the
| > map
| > on
| > | you handeld GPS
| > | and another key to use it on Garmin Mobile PC.
| > |
| > |
| > | Harold Muller
| > |
| >
| >
| > Thank you Harold,
| > This whole *hey it ain't compatible anymore* scenario is so typical!
| > I have taken note of all the 1st hand experience offered me in this
| > thread,
| > and when CNNA 2010 arrives I will put all this wonderful knowledge into
| > play. (and of course will inform this group)
| >
| > As far as creating new folders, etc. to preserve a working program
| > between
| > MS 6.13 and MetroGuide v.7 is concerned (for my 76s),
| > my major concern involved how installing a new program (CNNA 2010) would
| > affect the existing Windows registry.
| > A search of same revealed that the only significant issue I could see
| > a
| > path to the Mapsource program itself--something that this thread has
| > already
| > covered by showing how to create a new shortcut, so that I could
| > independently open either MS 6.13 or 6.1
| >
| >
| > --
| > Regards,
| > Richard Harison
| >
| >
|
| > path to the Mapsource program itself--something that this thread has
| > already
| > covered by showing how to create a new shortcut, so that I could
| > independently open either MS 6.13 or 6.1
| >
| >
| > --
| > Regards,
| > Richard Harison
| >
| >
|
Thanks,
You confirm what I suspected.
When 6.15 arrives with CNNA 2010, I will hope just to use it and have it
read my MetroGuide v.7 for routing the 76s.
--
Regards,
Richard Harison
> Interesting! One of the issues that (especially) Jack E. & I have been
> hashing over is MS 6.15 and its ability to read my Metroguide map file,
> which is in (you guessed her!) a folder under c:\garmin. =A0
> hashing over is MS 6.15 and its ability to read my Metroguide map file,
> which is in (you guessed her!) a folder under c:\garmin. =A0
Hmm, Although I no longer use it, that last version of Metroguide USA
is still installed on my computer and it does run in Mapsource 6.15. I
don't remember, but may have modified some registry settings to make
it work. One only needs to be sure that Mapsource knows where to find
the files. The registry location is here: HKEY_LOCAL_MACHINE\SOFTWARE
\Garmin\Mapsource\Families\USA Metroguide v4. Note that I routinely
change the key name and it may have originally installed with a
slightly different name. You can change the key name with no adverse
impact.
The same is true with the plethora of free (and legal maps available).
Their installation programs are apt to send the files to all sorts of
strange places. I just move them to the C:\Garmin folder, then adjust
registry settings so that Mapsource can find them. Incidentally, when
modifying the registry be sure to back it up first. Should you make an
error, when loading Mapsource you will get an error mesage stating
Mapsource needs to be reinstalled. Instead of reinstalling, just go
back and review what you have done in the regisrty. If you can't find
it, restore the registry from the backup. There is also another free
program out there that will check the Mapsource installation for you
and lead you to where the error is. Its called MapsetToolKit (by
Cypherman).
To back up registry settings, go to the HKEY_LOCAL_MACHINE\SOFTWARE
\Garmin\Mapsource key, right click on it then export.
> As it stands so far, I have to consider that MS 6.15 and 6.13 will have t=
o be run as
> independent programs. =A0Kind of a drag!
Yeah, but no big issue. I have both versions installed in the same
folder under different names (C:\Garmin). On the desktop, the icons
are different so its easy to distinguish them.
> I wonder if copying the Metroguide map to the appropriate Application Dat=
a
> folder will allow 6.15 to access it?
No need to do it!
> Another drag: =A0One assumes v. 6.15 will deposit the files in the *all u=
sers*
> bin.
> Yet another place to look!!
> Yet another place to look!!
As another poster mentioned, MapReverseConverter creates new map files
and lets you choose where to store them. Then, those originally
installed by Garmin may be deleted, along with the registry pointers
to the Application data folder. Either the old or new versions of
Mapsource will open those maps.
Another thing, Garmin is inconsistent in the way they name their
products. I use a free program called TDBChanger to modify names.
Bob
> Interesting! One of the issues that (especially) Jack E. & I have been
> hashing over is MS 6.15 and its ability to read my Metroguide map file,
> which is in (you guessed her!) a folder under c:\garmin.
> hashing over is MS 6.15 and its ability to read my Metroguide map file,
> which is in (you guessed her!) a folder under c:\garmin.
Hmm, Although I no longer use it, that last version of Metroguide USA
is still installed on my computer and it does run in Mapsource 6.15. I
don't remember, but may have modified some registry settings to make
it work. One only needs to be sure that Mapsource knows where to find
the files. The registry location is here: HKEY_LOCAL_MACHINE\SOFTWARE
\Garmin\Mapsource\Families\USA Metroguide v4. Note that I routinely
change the key name and it may have originally installed with a
slightly different name. You can change the key name with no adverse
impact.
The same is true with the plethora of free (and legal maps available).
Their installation programs are apt to send the files to all sorts of
strange places. I just move them to the C:\Garmin folder, then adjust
registry settings so that Mapsource can find them. Incidentally, when
modifying the registry be sure to back it up first. Should you make an
error, when loading Mapsource you will get an error mesage stating
Mapsource needs to be reinstalled. Instead of reinstalling, just go
back and review what you have done in the regisrty. If you can't find
it, restore the registry from the backup. There is also another free
program out there that will check the Mapsource installation for you
and lead you to where the error is. Its called MapsetToolKit (by
Cypherman).
To back up registry settings, go to the HKEY_LOCAL_MACHINE\SOFTWARE
\Garmin\Mapsource key, right click on it then export.
> As it stands so far, I have to consider that MS 6.15 and 6.13 will have to
> be run as
> independent programs. Kind of a drag!
> be run as
> independent programs. Kind of a drag!
Yeah, but no big issue. I have both versions installed in the same
folder under different names (C:\Garmin). On the desktop, the icons
are different so its easy to distinguish them.
> I wonder if copying the Metroguide map to the appropriate Application Data
> folder will allow 6.15 to access it?
> folder will allow 6.15 to access it?
No need to do it!
> Another drag: One assumes v. 6.15 will deposit the files in the *all
> users*
> bin.
> Yet another place to look!!
> users*
> bin.
> Yet another place to look!!
As another poster mentioned, MapReverseConverter creates new map files
and lets you choose where to store them. Then, those originally
installed by Garmin may be deleted, along with the registry pointers
to the Application data folder. Either the old or new versions of
Mapsource will open those maps.
Another thing, Garmin is inconsistent in the way they name their
products. I use a free program called TDBChanger to modify names.
Bob
Thanks Bob!
Will advise when CNNA 2010 gets here
--
Regards,
Richard Harison
snip
>
> Aparently, changes were made to make the program compatible with Apple
> computers.
> Aparently, changes were made to make the program compatible with Apple
> computers.
Mapsource is not compatible and doesn't run under the Apple Mac OS X.
It runs under the Windows operating system.
I use Roadtrip which does run on Mac OS X and have no problems.
boojum
> Metroguide
> in
> | the c:\garmin folder,
> | it also is able to read most other third party maps which I have placed
> in
> | the C:\garmin folder.
> |
> | As you have probably figured out after you run the ReverseConverter and
> | create the new files in C:\grarmin,
> | you can delete new format install files in C:\Documents and Settings\All
> | Users\Application Data\GARMIN\Maps,
> | version 6.15.6 still finds the files it needs
> |
> | It is a major irritant for those that use nRoute because it is unable to
> | find any maps in the
> | C:\Documents and Settings\All Users\Application Data\GARMIN\Maps
> location,
> | but has no problem with them once they are ReverseConverted and moved to
> | c:\Garmin.
> |
> | The long range Garmin plan appears to be to drop nRoute (already
> happened),
> | get those that want it to buy Garmin Mobile PC a purchased program.
> | Garmin Mobile PC then handles each locked map set as a new install to
> Garmin
> | Mobile PC with it's own unlock key.
> |
> | You then have to purchase two unlock keys, one unlock key to use the
> map
> on
> | you handeld GPS
> | and another key to use it on Garmin Mobile PC.
> |
> |
> | Harold Muller
> |
> Thank you Harold,
> This whole *hey it ain't compatible anymore* scenario is so typical!
> I have taken note of all the 1st hand experience offered me in this
> thread,
> and when CNNA 2010 arrives I will put all this wonderful knowledge into
> play. (and of course will inform this group)
> As far as creating new folders, etc. to preserve a working program
> between
> MS 6.13 and MetroGuide v.7 is concerned (for my 76s),
> my major concern involved how installing a new program (CNNA 2010) would
> affect the existing Windows registry.
> A search of same revealed that the only significant issue I could see was
> a
> path to the Mapsource program itself--something that this thread has
> already
> covered by showing how to create a new shortcut, so that I could
> independently open either MS 6.13 or 6.1
> --
> Regards,
> Richard Harison
>