Mozilla 1.7 final release doesn't run after install

RESOLVED WORKSFORME

Status

--
minor
RESOLVED WORKSFORME
15 years ago
13 years ago

People

(Reporter: CwazyBill, Unassigned)

Tracking

1.7 Branch
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040608
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040608

I previously ran Mozilla 1.7 RC2 and RC3 with no problems. After the 1.7 final
was released, I downloaded it but it didn't run after the install. The first
download was with Bittorrent so I re-downloaded with IE6. The file sizes were
somewhat different but after installing the new download from IE6, this second
download did not run either. I tried re-installing them both - with the same
results. Finally, I went back to my 1.7 RC3. It installed and is working fine. 

Reproducible: Always
Steps to Reproduce:
1.Download Mozilla 1.7 final.
2.Install, and note that it doesn't start after the install.
3.Optional - Re-install Mozilla RC3.... RC3 re-installs fine

Actual Results:  
When the install finished, the usual startup of Mozilla failed immediately.
After also trying both Mozilla icons, (on my desktop and in the toolbar), they
too failed to start it up. Ditto when I went into the directory and clicked on
mozilla.exe also

Expected Results:  
Mozilla 1.7 should have opened and run immediately after the install was complete.

Feedback agent, debugger, and inspector weren't installed on my latest Mozilla
1.7 final install.

Comment 1

15 years ago
Reporter, could you try to install Mozilla following the step by step
instructions contained in Bug 133476 Comment #12 and see if it works?
Product: Browser → Seamonkey

Comment 2

13 years ago
No responses, old version. Resolving. Please try the new upcoming Mozilla 1.7.12
or SeaMonkey 1.0a release.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
Version: Trunk → 1.7 Branch
You need to log in before you can comment on or make changes to this bug.