After install of 1.4rc2, browser will NOT start and Abends.

RESOLVED INVALID

Status

SeaMonkey
General
--
blocker
RESOLVED INVALID
15 years ago
13 years ago

People

(Reporter: Zvi I Weiss, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:1.3) Gecko/20030313
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4rc2/mozilla-os2-vacpp-1.4rc2-installer.exe

I just downloaded the latest version of Mozilla for OS/2 (listed as 1.4rc2 with
the full designation of mozilla-os2-vacpp-1.4rc2).  I downloaded the "built-in
installer" version.  The install went smoothly.  However, when I tried to start
up the Browser, I received the following message: The system could not load
application segment.  MYSPELL -> XPCOM.3386 is in error.  For more information,
type HELP SYS182.  When I did that, I received an explanation to the effect that
the application cannot run on this version of teh OS/2 Operating System.
I am currently using WARP 4 at FP 9 (which -- for me -- has been VERY stable). 
Right now, Version 1.3 works.

Reproducible: Always

Steps to Reproduce:
1. Start up dialer to access internet.
2. Establish connection
3. Click on Icon to start up Browser (or type in command line invocation).

Actual Results:  
Almost immediately, the "abend" window comes up indicating that program could
not start.  When I click for "more details", I receive the additional data
documented above.

Expected Results:  
Should have come right up!

Updated

15 years ago
OS: other → OS/2

Comment 1

15 years ago
RC2 doesn't have the spellchecker, but it is trying to load spellchecker DLLs -
you installed it over an install that had spellchecker.

Remove myspell.dll and spellchk.dll from the components directory and restart.

This won't be a problem in 1.4 final which will have spellchecker.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.