Closed
Bug 172428
Opened 22 years ago
Closed 22 years ago
cannot install after applying MS HTML Help security fix
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 167515
People
(Reporter: kifo, Assigned: dveditz)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) Build Identifier: Mozilla After apply the latest Microsoft Windows XP Security Fix (link here: http://www.microsoft.com/technet/treeview/default.asp? url=/technet/security/bulletin/MS02-055.asp ), I cannot install Mozilla! I tried both 1.2a and 1.1. I unwisely uninstalled Mozilla 1.1 when I couldn't install Mozilla 1.2a over it. Now, I don't have a working Mozilla installation! Reproducible: Always Steps to Reproduce: 1.Install the MS HTML Help Unchecked Buffer Security Fix 2.Try to install a new Mozilla build using Mozilla Setup 3. Actual Results: The standard MS error pop-up will appear, offering to send the error to MS.
Comment 1•22 years ago
|
||
see also bug 172356
Assignee | ||
Comment 2•22 years ago
|
||
Try running the install in "compatibility" mode -- right click on the executable, select the compatibility tab, and set the compatibility to Win98. If that workaround fixes the problem then this is a duplicate of bug 167515 otherwise we'll have to dig deeper.
Assignee | ||
Comment 3•22 years ago
|
||
How far into the install do you get before it crashes? Is it the install part that's crashing, or Mozilla itself crashing at startup after the install.
The problem did go away with the suggestion to set the installer to compatibility mode. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Comment 5•22 years ago
|
||
reopen the dupe...
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 6•22 years ago
|
||
dupe *** This bug has been marked as a duplicate of 167515 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 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
•