badgolferman said:
Okay, I'll respect that. By the way, how many registry entries does the
Mozilla program you're using have?
S'il vous plait: I want to answer that one.
I don't want to answer it by looking in my own active registry. Due to
the fact that I have complicated matters by registering the Mozilla
Active-X control, for use by some misc apps. And due to the fact that
I have a few Mozilla filetype keys in there, left lingering without need.
They got there either because I did not fully clean up after the Mozilla
installer; or they got there when I did some test, forgetting to clean up
afterwards, involving checking into how Mozilla did things when one said
yes to giving it associations.
The question I am interested in with programs is which writes to the
registry or external files are forced and unavoidable. Exclusive of
those which are voluntary and as exclusive of unnecessary installer
debris.
So I booted into my semi-virgin w98 partition, one that has never met
any of the Mozilla programs.
I made a copy of Mozilla's bin directory. Then I ran the executable. I
deleted the default profile that it creates off in the appdata folder,
and chose my own location for a profile in the Mozilla folder.
That leaves, for external files, two small ones.
%appdata%\Mozilla\ pluginreg.dat (~1k), registry.dat (~2k)
I've never been able to budge those. Mozilla executable evidently is
hard-coded to look there first, as its inquiry routine on where to look
for active profiles. It's the same deal with Firefox. And with the Mozilla
Active-X control. K-Meleon alone in the family keeps all files completely
self-contained.
For registry, Mozilla requires only one key.
[HKEY_LOCAL_MACHINE\Software\Mozilla]
[HKEY_LOCAL_MACHINE\Software\Mozilla\Desktop]
"haveBeenSet"="1"
"showDialog"="1"
This key tells it whether to ask, on its startup, the question about taking
over associations.
For the record, this was Mozilla 1.6. I know I'm a bit behind the times;
nevertheless, I'd bet high wager that the described behavior is close
enough to identical in later releases.
Next, still on the virgin partition, I checked in with Firefox. On this
one, in additional to an installed one already on disk, I had an installer
to log. I almost thought I'd be reasonably current, too, since there was
a version .91 setup file stored on my drive. But when I got to it, found
it was a corrupt download. So I used another setup file that was there, a
version .8 Firefox setup. But again, I believe this test is still valid;
same as with Mozilla, I much believe the results apply equally to current
versions.
Firefox, to run, all it insisted upon was that pair of files off in the
appdata directory. As I did with Mozilla, I set the local profile data
into a folder of my choice.
%appdata%\Phoenix\ pluginreg.dat (~1k), registry.dat (~2k)
Firefox needed no registry entries to run.
Its installer had added registry entries. They were mild. After running an
app, I always delete these two:
; HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\Mozilla Firefox (0.8.)
; HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\firefox.exe
The first one I delete because I do not use the uninstall routines that
are bundled with programs. The second one because it's only needed <1%
of the time. For an app that cannot figure out its own location, when
it's hunting for its libraries. Then, or the ability for launch from
places like the Run... box, I prefer using the method of putting an .lnk
to the app in my path. Finally, the one other possible use, for reinstall
or upgrade, in case installer looks there -- well, I can tell an installer
where to put files.
I also had no hesitation about deleting the following two keys:
; HKCU\Software\mozilla.org
; HKLM\Software\mozilla.org
I remember deleting those long ago in my active registry, and that has
never affected Mozilla. So it would not affect Firefox either. The data
there is the version release and the installation path. It's just the
installer sending itself notes, and nothing the program needs to run.
There was one last pair of keys added by the installer, which might be
needed. I deleted them, and they were not re-added, and did not affect
Firefox's ability to run. However, they involve defining paths for
Firefox extensions. So it might likely enough be that once one starts
installing the Firefox extensions, these keys will either be re-added
automatically (most likely), or else I could need to import a deleted
key (the HKLM one) back into the registy.
; HKLM\Software\Mozilla\Mozilla Firefox 0.8.
; HKCU\Software\Mozilla\Mozilla Firefox 0.8.
....\Software\Mozilla\Mozilla Firefox 0.8.\Extensions]
...."Components"="D:\\INET\\WEB\\test\\firefox\\bin\\Components"
...."Plugins"="D:\\INET\\WEB\\test\\firefox\\bin\\Plugins"
...."PathToExe"="D:\\INET\\WEB\\test\\firefox\\bin\\firefox.exe"
SUMMARY REPORT ON THE MOZILLA FAMILY
Required on run K-Meleon: no external files, and no registry
Required on run Mozilla: two external files, and one small hklm regkey
Required to run Firefox: two external files, and no registry
Required to run Firefox+Extensions: ", and maybe a small hklm & hkcu key