pressing on the "compose" button will freeze entire Mozilla after installing/using FaxTalk Pro 6.0

RESOLVED WORKSFORME

Status

SeaMonkey
MailNews: Message Display
--
critical
RESOLVED WORKSFORME
16 years ago
14 years ago

People

(Reporter: Jean Beaudet, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

({hang})

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/200212??

The first time I installed FaxTalk 4.5.5, I had no problem to run Mozilla. Then,
I installed trial version of FaxTalk Pro 6.0. After a while of using this new
software, entire Mozilla would freeze when I clicked on the "send" button on the
email composition window. 

I uninstalled FaxTalk, reinstalled Mozilla (I did these operation a few times)
and then Mozilla started to work again. I finally reinstalled FaxTalk 4.5.5 and
I had no problem with Mozilla Mail until I got my first message with FaxTalk.
This time, uninstalling FaxTalk and uninstalling/reinstalling Mozilla 1.2.1
didn't do it.

I installed mozilla 1.3a and now my mail client works fine until now. However, I
really need to install a phone/fax answering software. 

Reproducible: Always

Steps to Reproduce:
1. Install FaxTalk 6.0 Pro
2. Use FaxTalk 6.0 Pro (receive a couple of messages)
3. Try to send a mail with Mozilla

Actual Results:  
Whole mozilla freezes

Expected Results:  
!!!

Comment 1

16 years ago
Reporter: Search your PC for "xul.mfl"   
Rename it...   Does that fix your problem?

Comment 2

15 years ago
reporter, try these steps:
1. uninstall FaxTalk Pro
2. back up mapi32.dll
3. reinstall FaxTalk Pro
4. restore mapi32.dll

does the problem still occur?
Severity: normal → critical
Keywords: hang
Product: Browser → Seamonkey
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.