Originally Posted by
PepiMK
The location where the executable is installed shouldn't matter. I'll try to describe how our tools try to locate the Mozilla/Firefox/&c browsers:
1. For each user, it gets the application data folder.
2. There, it looks for the following files in subfolders:
* Phoenix\registry.dat
* Mozilla\registry.dat
* Beonex\registry.dat
* Firebird\registry.dat
* nsreg.dat
* Mozilla\Firefox\profiles.ini
* Thunderbird\profiles.ini
3. Each of these files, if it exists, should point to a prefs.js file, which is then regarded as a profile location of the corresponding browser.
(Only exception: for K-Meleon, another clone, the registry file is looked for in a subfolder of the program files folder)