Messages

Boyd - I looked at the thread you mentioned earlier. It's not exactly the same problem, but I think in their attempt to fix one problem, they may have inadvertently created the one we're faced with now. Hard coding the Wow6432 key into the registry path is probably a bad idea. I suspect the NSIS installer is confused as to which registry it's working with (32-bit or 64-bit). Normally you would tell it by using the SetRegView command. My advice would be to go back to the old script. It seemed to work just fine for both Windows XP and Windows 7 64-bit when I tried it. Maybe we should bring -Oz- into the discussion. I think he was the one that made the changes.

But how would I have gotten the regestry entry there to begin with?  I THINK I only used installers to install maps on my laptop.  But there is a posibility I could have used mapsettoolkit for some of my maps.

Is there a way to modify the installers to make sure that entry is there?

Probably if you upgraded your laptop from Windows XP or Vista, the change would have been carried over to Windows 7.

I'm guessing the programmer that wrote the installer would have to make some changes to the code. I wouldn't think it would be that difficult.

[Families]

The problem seems to only happen if the HKLM\Software\Wow6432Node\Garmin\MapSource\Family Family registry key is missing (like it is on a fresh install of Mapsource). If it already exist, the auto installer works flawlessly. The FL Topo map was the only one I tried.

Correction: I should have said HKLM\Software\Wow6432Node\Garmin\MapSource\Families registry key.

The problem seems to only happen if the HKLM\Software\Wow6432Node\Garmin\MapSource\Family registry key is missing (like it is on a fresh install of Mapsource). If it already exist, the auto installer works flawlessly. The FL Topo map was the only one I tried.

I had the exact same problem until I went into the system registry and made a few changes. For some reason the auto installer for the Florida Topomap is making registry changes in the wrong location. Instead of adding to HKLM\Software\Wow6432Node\Garmin\Mapsource, it puts everything under HKLM\Software\Wow6432Node\Wow6432Node\Garmin\Mapsource (note the additional Wow6432Node level). This seems to only happen under Windows 7 64-bit.

Shawn