Mozilla 1.7.3 Stable - A Web browser.

  • Thread starter Thread starter Gordon Darling
  • Start date Start date
G

Gordon Darling

Mozilla 1.7.3 Stable - A Web browser.

About:
Mozilla is a project to continue Netscape Communicator as an open project.
The project is maintained by employees of Netscape (now a division of
AOL), RedHat, some other companies, as well as contributors from the
community.

Changes:
This is a security update to Mozilla 1.7 that fixes several security
vulnerabilities.

Release focus: Major security fixes
License: Mozilla Public License (MPL)
Project URL: http://freshmeat.net/projects/mozilla/

Homepage: http://freshmeat.net/redir/mozilla/29579/url_homepage/#1.7.3

Regards
Gordon
 
Mozilla 1.7.3 Stable - A Web browser.

About:
Mozilla is a project to continue Netscape Communicator as an open project.
The project is maintained by employees of Netscape (now a division of
AOL), RedHat, some other companies, as well as contributors from the
community.

Changes:
This is a security update to Mozilla 1.7 that fixes several security
vulnerabilities.
Click to expand...
But I thought it was only Microsoft products that had security
issues!
 
Vrodok said:
Back to 'Windows "Update"', yet again... *sigh*
Click to expand...

LOL

Last time I went there was to get a language pack. They wanted to give
me loads of security updates; I declined politely.
 
jo said:
Last time I went there was to get a language pack. They wanted to give
me loads of security updates; I declined politely.
Click to expand...

I once made the very foolish choice of accepting micorsoft's offer
to update my video drivers. Resulted in immediate destruction of my
dual-monitor capability.

My worst choice on this machine, with msft downloads, it was WMP7. Ughh,
what a mess. There was a problem with it running. I didn't learn that the
cause of the problem I had was a corrupt skin file until too late. I kept
reinstalling on top, as well as repeatedly uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and climbed.
New registry entries were getting created each time (involved keys being
added with incrementing numeric tails), during the repeated reinstalls of
that thing.

It's been on my todo list for years now, to get in there to do a medical
operation, and liposuction out what I can of WMP. Once I find a pair of
industrial-strengh rubber gloves, and have my calendar cleared for a week.
 
I once made the very foolish choice of accepting micorsoft's offer
to update my video drivers.
Click to expand...

Yeah; M$ fooled me with that a while back. ~!@#$%^&* ..... took a G-D AWFUL
amount of effort to "downgrade" that software!!
 
omega said:
I kept
reinstalling on top, as well as repeatedly uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and climbed.
New registry entries were getting created each time (involved keys being
added with incrementing numeric tails), during the repeated reinstalls of
that thing.
Click to expand...

You ever used Test-Run?

http://dogkennels.net/testrun/testrun.htm
 
jo said:
omega wrote:
[WMP7]
reinstalling on top, as well as repeatedly uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and climbed.
Click to expand...

You ever used Test-Run?

http://dogkennels.net/testrun/testrun.htm
Click to expand...

That story took place several years ago -- when I was, comparatively, a
little more promiscuous. I did take inctrl logs during the process, but
that was about it. Back then I wasn't so cautious as to take always be
set with approaches such as starting out with a specific snapshot, then
proceeding into an installation with suspicion, and full preparations to
revert.

That battle with WMP7, it extended over about a week. If I were to expect
a prolonged battle like that again, I'd be likely to use Installwatch during
the specific interactions with such software, from which I can get detailed
logs, and which can then be converted to reg undo files. And then be able
to continue keeping, in the meantime, from the other hours of the week, the
normal aspects of my registry updated.

Or if I was dealing with software that seemed specially monstrous (such as
a number of the msft products), and I felt some foreboding of caution, I'd
boot into a temp ghost of my C partition, and mess with the install, logging
it, from there. That would take care of the matter of my system files,
together with that which Test-Run does, let one direct writes to a temporary
copy of the registry.

Speaking of monsters. I'm considering running an install of the dotnet thing
onto my temp C drive. Not because I have any intention in the nearby future
of yet submitting to it. But instead for the sake of getting a log, for
those who might wonder the scope of its impact, as far as system files and
registry changes. And for my own curiosity. To take a morbid peek into that
vat, without commitment.
 
omega said:
jo said:
omega wrote:
[WMP7]
reinstalling on top, as well as repeatedly uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and climbed.
Click to expand...

You ever used Test-Run?

http://dogkennels.net/testrun/testrun.htm
Click to expand...

That story took place several years ago -- when I was, comparatively, a
little more promiscuous. I did take inctrl logs during the process, but
that was about it. Back then I wasn't so cautious as to take always be
set with approaches such as starting out with a specific snapshot, then
proceeding into an installation with suspicion, and full preparations to
revert.

That battle with WMP7, it extended over about a week. If I were to expect
a prolonged battle like that again, I'd be likely to use Installwatch during
the specific interactions with such software, from which I can get detailed
logs, and which can then be converted to reg undo files. And then be able
to continue keeping, in the meantime, from the other hours of the week, the
normal aspects of my registry updated.

Or if I was dealing with software that seemed specially monstrous (such as
a number of the msft products), and I felt some foreboding of caution, I'd
boot into a temp ghost of my C partition, and mess with the install, logging
it, from there. That would take care of the matter of my system files,
together with that which Test-Run does, let one direct writes to a temporary
copy of the registry.

Speaking of monsters. I'm considering running an install of the dotnet thing
onto my temp C drive. Not because I have any intention in the nearby future
of yet submitting to it. But instead for the sake of getting a log, for
those who might wonder the scope of its impact, as far as system files and
registry changes. And for my own curiosity. To take a morbid peek into that
vat, without commitment.
Click to expand...

I was going to recommend that you use Oppcom:

http://www.beta10.com/oppcomme.htm

but don't know what version of Windows you're using and it's only for
Millennium Edition. Also, I just tried going into the Control Panel's
Add/Remover Programs module, and when I click on the Windows Setup tab
get an error message and can't run it. To be fair, this is probably
something I did while cleaning my registry because Oppcom has been
working fine on my system until now.

Looks like it's time for the periodic total reinstall of my system and
programs.


Sigh..........


--
Regards from John Corliss
No adware, cdware, commercial software, crippleware, demoware,
nagware, shareware, spyware, time-limited software, trialware, viruses
or warez please.

Because Andy Mabbett is stalking me in this group, I have him killfiled.
 
John said:
omega said:
jo said:
omega wrote:
[WMP7]

reinstalling on top, as well as repeatedly
uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and
climbed.

You ever used Test-Run?

http://dogkennels.net/testrun/testrun.htm
Click to expand...

That story took place several years ago -- when I was, comparatively, a
little more promiscuous. I did take inctrl logs during the process,
but that was about it. Back then I wasn't so cautious as to take
always be set with approaches such as starting out with a specific
snapshot, then
proceeding into an installation with suspicion, and full preparations to
revert.
That battle with WMP7, it extended over about a week. If I were to
expect a prolonged battle like that again, I'd be likely to use
Installwatch during
the specific interactions with such software, from which I can get
detailed
logs, and which can then be converted to reg undo files. And then be able
to continue keeping, in the meantime, from the other hours of the
week, the
normal aspects of my registry updated.

Or if I was dealing with software that seemed specially monstrous
(such as
a number of the msft products), and I felt some foreboding of caution,
I'd
boot into a temp ghost of my C partition, and mess with the install,
logging
it, from there. That would take care of the matter of my system files,
together with that which Test-Run does, let one direct writes to a
temporary
copy of the registry.

Speaking of monsters. I'm considering running an install of the dotnet
thing
onto my temp C drive. Not because I have any intention in the nearby
future
of yet submitting to it. But instead for the sake of getting a log, for
those who might wonder the scope of its impact, as far as system files
and
registry changes. And for my own curiosity. To take a morbid peek into
that
vat, without commitment.
Click to expand...


I was going to recommend that you use Oppcom:

http://www.beta10.com/oppcomme.htm

but don't know what version of Windows you're using and it's only for
Millennium Edition. Also, I just tried going into the Control Panel's
Add/Remover Programs module, and when I click on the Windows Setup tab
get an error message and can't run it. To be fair, this is probably
something I did while cleaning my registry because Oppcom has been
working fine on my system until now.

Looks like it's time for the periodic total reinstall of my system and
programs.


Sigh..........
Click to expand...

Well that was a close one. I Googled the error message ("Rundll32 has
caused an error in SETUPX.DLL") and found the following:

http://tinyurl.com/42g48

This was exactly what I had done. Luckily, I didn't delete the backups
like I normally do, and after re-merging them all back into the
registry my Control Panel's Add/Remove Programs module is "unhosed."

After this experience, I have to say that Regseeker can be very
dangerous in that it listed important entries as being superfluous.
Maybe a newer version has corrected this problem. The version on my
system is 1,35 beta build 1203.

At any rate, good luck on repairing your registry. Ironically, I've
had little trouble with WMP 7.1, but that's probably because I don't
use it very often.

--
Regards from John Corliss
No adware, cdware, commercial software, crippleware, demoware,
nagware, shareware, spyware, time-limited software, trialware, viruses
or warez please.

Because Andy Mabbett is stalking me in this group, I have him killfiled.
 
Quoting omega [[email protected]], that posted to alt.comp.freeware on Wed, 13 Oct
2004 09:27:56 -0700:
My worst choice on this machine, with msft downloads, it was WMP7. Ughh,
what a mess. There was a problem with it running. I didn't learn that the
cause of the problem I had was a corrupt skin file until too late. I kept
reinstalling on top, as well as repeatedly uninstalling-reinstalling. During
that activity, the size of my registry, it climbed and climbed and climbed.
New registry entries were getting created each time (involved keys being
added with incrementing numeric tails), during the repeated reinstalls of
that thing.
Click to expand...

The same thing had happened here with WMP9.

I have not managed to remove all traces of WMP yet, and I have already
uninstall it.
--
Chaos Master®, posting from Brazil.
"I'd rather be hated for who I am, than loved for who I am not." -- Kurt Cobain

Evanescence: http://marreka.no-ip.com | Lies: http://tinyurl.com/46vru |
/dev/null: http://renan182.no-ip.org
 
Back
Top