On Wed, Nov 18, 2009 at 3:02 PM, Zero3 <zero3 at zerosplayground.dk> wrote: > Matthew Toseland wrote: >> On Tuesday 17 November 2009 07:20:03 Zero3 wrote: >>> Matthew Toseland wrote: >>>> On Sunday 15 November 2009 01:14:54 Ed Tomlinson wrote: >>>>> On Saturday 14 November 2009 16:02:11 Matthew Toseland wrote: >>>>>> On Saturday 14 November 2009 17:19:15 Ed Tomlinson wrote: >>>>>>> Hi, >>>>>>> >>>>>>> For a test I installed freenet on a windows 7 box. ?All went well. ?The >>>>>>> new installation process is pretty simple. ?One small bone to pick. >>>>>>> ?The first use wizard tells you NOT to use the same browser for freenet >>>>>>> as you use normally - fine. ?However there does not seem to be a way to >>>>>>> configure 'Launch Freenet' from the systray to use your prefered >>>>>>> browser. ?I want to set it to use chrome... >>>>>> It *does* use Chrome if available, in incognito mode. Ask Zero3 why it >>>>>> isn't working. >>>>>>> This should be easy but it does not seem to be... >>>>> Think the problem is that I installed chrome after freenet and it _is_ >>>>> what I want freenet to use. ?I see no option to tell freenet to switch to >>>>> it. >>>> That is odd, I thought it detected it in the launcher at launch time? Have >>>> you filed a bug about this? >>> It does. If you read his previous reply, you will see that Microsoft >>> changed the registry path for uninstall entries in 64-bit Win7 (and >>> possibly 64-bit Vista/XP too?). Which means the launcher won't find >>> Chrome on these systems... >>> >>> I need to figure out which versions that use the changed path, and >>> change the launcher for these versions. >> >> Looks like that's simply due to installing a 32-bit Chrome on a 64-bit >> Windows... > > Hmm. Maybe. But that would mean that our own uninstallation entry would > be "relocated" on those systems as well. Which means uninstallation > might not work as predicted. > > In any way, I need to sort out exactly what happens - and when it happens. >
WoW32 registry / path are created when you run 32-bit apps on 64-bit windows. If you 32-bit application try to read HKEY_LOCAL_MACHINE\SOFTWARE\XYZ\123 It would try HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\XYZ\123 first, and fall back to HKEY_LOCAL_MACHINE\SOFTWARE\XYZ\123 if it does not exist. see http://support.microsoft.com/kb/896459/en-us
