Closed
Bug 167752
Opened 23 years ago
Closed 23 years ago
installation failure on windows xp after installing sp1
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 167515
People
(Reporter: eandersen, Assigned: dveditz)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705)
Build Identifier: all builds
Mozilla 1.0 was previously installed without any problems. I installed sp1
for XP Pro, then decided to try to install Mozilla 1.1. The installation dies
almost as soon as it begins. A few items are put in the registry along and
some files are copied over... I received a message saying there has been an
error in jar50.dll and I get a bug report and everything. So I uninstalled
Mozilla 1.0, cleaned the temp directories, cleaned the registry, deleted all
the files, and restarted....redownloaded the file and tried again....exact
same error - tried it on an xp machine without service pack one...and it
installed no problem....tried three different versions of mozilla...dies every
time
Reproducible: Always
Steps to Reproduce:
1.Install service pack one on an xp machine
2.download and attempt to install any version of mozilla
3.watch the frustration level rise as it dies and throws an exception
Actual Results:
The installation dies after writing registry entries and copying some files
Expected Results:
installed correctly
If you like, I have lots of files about this lovely crash....like the crash
report and the installation log....
Comment 1•23 years ago
|
||
This is a dupe of:
http://bugzilla.mozilla.org/show_bug.cgi?id=167515
Glad someone else was able to duplicate this..
Comment 2•23 years ago
|
||
Reporter, could you attach anything you have to bug 167515? (this bug is a
duplicate of that one).
*** This bug has been marked as a duplicate of 167515 ***
*** This bug has been marked as a duplicate of 167515 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•