Closed
Bug 195112
Opened 21 years ago
Closed 21 years ago
Installing 2003-02-26-05-1.3 (branch) failed on Windows 98. Error loading xpistub.dll.
Categories
(SeaMonkey :: Installer, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 195060
People
(Reporter: stig, Assigned: ssu0262)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: ftp://ftp.mozilla.org/pub/mozilla/nightly/2003-02-26-05-1.3/mozilla-win32-installer-sea.exe Installing Win32 1.3 branch build on my Windows 98 failed. I got the following error: "1157: Could not load C:\TEMP\ns_temp\xpcom.ns\bin\xpistub.dll" After the failed installation my TEMP-directory included a sub-directory called ns_temp2, but *not* one called ns_temp. Also there was a few files in C:\TEMP\ns_temp2\xpcom.ns\bin\, but no xpistub.dll. Reproducible: Didn't try Steps to Reproduce: 1. Uninstalling my Mozilla 1.2.1 2. Reboot 3. Install mozilla-win32-installer-sea.exe (branch 2003-02-26-05-1.3) I've done just as I use to when installing a new Mozilla, and have done it with every almost every new "milestone", beta or final version in the last two years. So I don't think I didn't install it the right way. Actual Results: The described error message after some "installation-work". Some files in C:\TEMP\ns_files2, but I don't think any files was copied to my target of installation (D:\Program Files\Mozilla). No desktop icons or other signs of installation. I could succesfully reinstall the "old" Mozilla 1.2.1 afterwards. I also have another nigtly installed on my E-drive (with a seperate profile)
Reporter | ||
Updated•21 years ago
|
Version: Trunk → Other Branch
Probably the same as bug 195060 (based on information in bug 19220).
Comment 2•21 years ago
|
||
CC'ing some installer people. Same issue?
Comment 3•21 years ago
|
||
I saw this before- see bug 135570 and its many duplicates
bug 135570 errored out with 1114. this bug refers to error 1157: 1114: an initialization routine failed in the dll 1157: one of the dependent dlls was not found. reporter, can you download the dependency walker: Microsoft's free dependency walker is available from http://www.dependencywalker.com and also in various larger free packs from microsoft itself. Also available from http://download.cnet.com/ and do the following test: 1) Run "mozilla-win32-installer-sea.exe -u xpcom.xpi" from an empty dir This will extract xpcom.xpi into the current dir. 2) unzip xpcom.xpi from this same dir 3) copy msvcirt.dll and msvcrt.dll to bin\ 4) cd into bin\ 5) run the dependency walker on xpistub.dll in the bin\ dir. Can you see which file it is failing to load on?
Reporter | ||
Comment 5•21 years ago
|
||
I'll do the "dependency walker" test as soon as possible. I suspect I won't get the time today, but hopefully else tommorow night (FYI: In my timezone it is thursday morning now).
Comment 6•21 years ago
|
||
Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.3?
Comment 7•21 years ago
|
||
Both Seamonkey and the net installer are broken.
*** Bug 195200 has been marked as a duplicate of this bug. ***
this bug is a dupe of bug 195060. The 1.3 branch build from 2003-02-26-05 is a debug build. Today's build seems to be fixed. *** This bug has been marked as a duplicate of 195060 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Flags: blocking1.3?
Reporter | ||
Comment 10•21 years ago
|
||
Reg. comment #4. I assume running the "dependency walker" is a waste of time now, since rumours says its been fixed already? I'll try a newer branch-build instead as soon as I spot one for Win32.
Comment 11•21 years ago
|
||
reg. comment #9. Don´t agree, windows builds are about 40 MB. Todays windows builds are having more than 3 times their normal size. It´s either sourcecode (self-compiling?) or full instrumented debbugging code. I would be very disappointed, if after a long download mozilla wouldn´t run because I don´t have Microsoft Visual Studio.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•