Closed Bug 30711 Opened 25 years ago Closed 25 years ago

Installer fails to install when Net2Phone installed

Categories

(SeaMonkey :: Installer, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: amasri, Assigned: ssu0262)

Details

(Whiteboard: [PDT+] 3/8)

with Seamonkey March 6 build (not a new problem): Steps to reproduce: 1. Install Net2Phone 2. Relaunch so that Net2Phone window appears. 3. Close Net2Phone window. 4. Run NetscapeSetup Result: Error message appears "Setup has detected an instance of Net2Phone is currently running. Please quit Net2Phone before continuing setup" Problem is, I did quit Net2Phone, or at least thought I did. Netscape 6 will not install unless I remove Net2Phone from System Tray.
This is correct behavior. Net2Phone in system try means net2phone is still running. Perhaps the wording of the warning message needs to be changed? if anyone can provide a different/better one, I'll be happy to change it. Marking this bug as invalid for now.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Well, the message is misleading, and it certainly won't get better if we close the bug. In order to "quit" from Net2Phone, the user must: 1. Remove Net2Phone from the system tray. 2. Restart Windows. The best solution would be: 1. Fix Net2Phone so it actually exits when you select the exit item on the window. If we can't do that, what about the following wording on the error message: "Setup has detected an instance of Net2Phone is currently running. Please remove Net2Phone from the system tray, restart Windows, and run Setup again."
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
*** Bug 30858 has been marked as a duplicate of this bug. ***
marking this for Beta1 (also see comments to bug deplicate of this one, #30858). This bug is only requesting a simple string change to be more informative.
Status: REOPENED → ASSIGNED
Keywords: beta1
Target Milestone: M14
Not sure I understand. Are we requesting a change in the Net2Phone client? Sean please email Greg Greenberg directly at Net2Phone to get this change quickly.
The proper solution here from the user perspective is to offer to shut down all the services that the client installed previously if we detect them running at install.
the string change is for our installer. We are the ones detecting Net2Phone running. What chofmann was requesting was for Net2Phone to remove itself from the system tray whenever the Net2Phone (with the dial pad) dialog is quit. I don't think that's necessary. It the way Net2Phone is quitting itself is correct. We just need a clearer message for the user.
PDT+ Can we skip over Net2Phone if it's already running?
Whiteboard: [PDT+]
To be extra clear: If Net2Phone is running, it is an acceptable solution to *NOT* even install Net2Phone. Can this be put in place soon? Any better solutions? The PDT was more than willing to have that "bypass" used as a resolution. If you can, please add a landing date to the status whiteboard.
We can't by pass the installation of Net2Phone if it is detected running. The reason to tell the user to quite Net2Phone before continuing, is to not require the user to reboot at the end of the installation. The right solution is to tell the user to quit Net2Phone all together. A change to the message string requesting this is needed to be more descriptive. I will be putting the string change to be what amasri requested (see is suggestion above). This change will be in today.
Whiteboard: [PDT+] → [PDT+] 3/8
Is this fix checked in?
There is a fix that will be in today's build. The fix (after discussing with Mr. PDT+ himself) is to *not* check to see if Net2Phone is running or not. But just simply install it regardless. I have verified that this will not cause a reboot dialog to show up at the end of the install. Net2Phone's installer handles Net2Phone running during installation.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
build 2000030909
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.