Post by Phil FryI haven't done this before, not sure what you wanted.
I selected seamonkey-2.41.en-US.win32.installer.exe
<https://l10n.mozilla-community.org/%7Eakalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/seamonkey-2.41.en-US.win32.installer.exe>,
downloaded it and ran it. I tried a few things and it seemed to work
fine. I had turned off all my add-ons, then added two back, so I did
not check SM 2.41 with all the add-ons I was using. I can do that if
that was your interest.
I see you thrashing around with trying to install 2.41, but I'm not
convinced that your problem is really related to versions.
Further up in the thread, I see a suggestion that you try running in
Safe Mode, but I don't see any evidence that you've given that a try.
(Besides the suggested way of launching with a command-line parameter,
you can also get to Safe Mode with Help -> Restart with Add-Ons Disabled...
I'm inclined to believe that there's something in your profile that may
be giving you problems, and that while your problems may have surfaced
with 2.39, that they really aren't specific to 2.39, but that 2.39 is
merely the symptom
With Safe Mode, not only does that temporarily disable any extensions,
but it also resets your user prefs to default settings. And I've seen
it happen once or twice, where a one-time restart in Safe Mode is enough
to clear odd things that are coming from your profile.
You may also want to consider using the profile manager to create a new
profile -- that will get *everything* back to default settings.
Personally, besides my normal working profile, I keep a separate profile
that I call "bare metal", where nearly everything in that profile is
defaults. Thus, if my regular profile isn't behaving, I can switch over
to the Bare Metal profile, to verify whether the problem is something
that's generic to Seamonkey, or if it's something in my profile. There
might be one or two exceptions, but the only time I can think of that
the Bare Metal profile didn't work for me was years ago, before the
normal Seamonkey User Agent string was not set to spoof Firefox.
I should note that I just rebuilt my Seamonkey profile -- the one I have
been using is *very* old, dating back early releases of Seamonkey 1.x,
if not to the old Mozilla suite, or even derived from a Netscape
installation. The old profile had a lot of years of accumulated cruft in
it. Following a rebuild (the browser part was easy, although it took me
longer to redo the Mail/News client), I find that Seamonkey runs
noticeably (although not dramatically) faster, and I have far less
frequency of temporary lock-ups (e.g., dark screen, and spinning wait
cursor) and browser crashes. There's still a couple of small things that
I haven't resolved (saving search results as virtual folders, and one
web site that complains about not seeing Firefox, even if that site
responds correctly in the Bare Metal profile), but overall, I'm quite
pleased with the results of moving to a new profile.
For whatever version of Seamonkey that you're running, I suggest that
you might want to see what happens with Safe Mode or a new profile,
before trying to fight through anything that might be related to version
differences.
Smith