Closed Bug 83488 Opened 23 years ago Closed 23 years ago

Mozilla won't start after Office 2000 install

Categories

(SeaMonkey :: General, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: srt, Assigned: asa)

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
BuildID:    20010505 (?)

Post-installation of Office 2K on my Windows NT machine, Mozilla won't start.  
A look in the Task Manager shows a mozilla process hanging around but using no 
CPU.

I was hoping there was some way to start Mozilla from the command line to 
produce verbose debugging output so that I could determine where the hang is 
occuring, but if so I can't find it.  If someone will enlighten me, I'll be 
happy to try it.
 

Reproducible: Didn't try
Steps to Reproduce:
1. Install Mozilla 0.9
2. Install Office 2000
3.
Some more info.

I downloaded and installed the latest nightly build.  That got a little farther 
when I started it -- I got to see the splash screen -- but eventually crashed 
and generated a talkback report.  During startup I got a popup complaining of a 
missing entry point in xpcom.dll, but I don't know if that's related.

After that I downloaded and reinstalled the 0.9 release, and it continues to 
fail as I originally described it.  I'm going to try eliminating the entire 
directory and installing fresh to see if that has any affect.
It looks to me you might have hit bug 53952 (fixed on 5/15) *and* a separate bug
with the nightly build. The fact that you did not have the splash screen while
now you have is a strong hint. 

Could you check this with another nightly build? Deleting the c:\Program
Files\mozilla.org directory before you install the is really a good idea.

Also, try to unload all the Office applets that start with the system
(FastStart, the Office bar etc.) and than try to run Mozilla0.9. Same thing
withnthe nightly.
The problem with the missing entry point should be solved if you delete
your mozilla/bin directory.
Delte your old profile if you have more problems. (run "mozilla -profilemanager")
Deleting my old profile fixed the problem.  I guess it's still a bug, but it's
good to have a work-around.
Marking WORKSFORME as per comments.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified worksforme
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.