Closed Bug 228295 Opened 22 years ago Closed 22 years ago

Trying to start mozilla.exe results in a crash (everytime)

Categories

(SeaMonkey :: General, defect)

x86
OS/2
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: os2fan, Unassigned)

Details

User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; de-DE; rv:1.3) Gecko/20030616 Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6b/mozilla-os2-1.6b.zip My popuplog.os2 contains the following report: 12-12-2003 17:35:53 SYS3175 PID 0040 TID 0001 Slot 0082 Y:\OS2APPS\MOZILLA\MOZILLA.EXE c0000005 18fd0156 P1=00000001 P2=00000001 P3=XXXXXXXX P4=XXXXXXXX EAX=003f0200 EBX=18fd014c ECX=00000002 EDX=003f0200 ESI=00000001 EDI=00000000 DS=0053 DSACC=f0f3 DSLIM=ffffffff ES=0053 ESACC=f0f3 ESLIM=ffffffff FS=150b FSACC=00f3 FSLIM=00000030 GS=0000 GSACC=**** GSLIM=******** CS:EIP=005b:18fd0156 CSACC=f0df CSLIM=ffffffff SS:ESP=0053:0013feb8 SSACC=f0f3 SSLIM=ffffffff EBP=0013ff08 FLG=00012246 NSPR4.DLL 0003:00000156 Reproducible: Always Steps to Reproduce: 1. start mozilla. Actual Results: Nothing happened for some econds, then I was back at the command line I started mozilla from Expected Results: run... System Enviromnent: eComStation 1.1, AMD Duron 800, mobo QDI Kinetiz 7E, 768MB SDR-RAM, nic Intel Pro 100/s
OS: other → OS/2
Do you have IBM Web Browser installed? Can you set BEGINLIBPATH= the place where you put Mozilla before starting it?
Yep, you're perfectly right. I searched my disk for occurences of nspr4.dll and found it at the location where the IBM browser is installed. Seems Mozilla didn't load its own special copy. The LIBPATH line in config.sys didn't contain the '.' at its start any more, so going to Mozilla's dir and starting it there didn't do the trick. I set it with BEGINLIBPATH and this made it working. Thanks for the advice. On the other hand I seem to only get the IBM Browser *or* Mozilla to run, not both of them. Even BEGINLIBPATH doesn't work every time. Still, this is an OS problem rather than a browser problem. Might be worth mentioning in the OS/2 specific documentation, though. 'Bug' fixed;-)
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
nothing broken, so nothing fixed
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
reresolving according to reporter comments
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.