Closed Bug 82430 Opened 24 years ago Closed 24 years ago

missing module in xpcom.dll

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect)

x86
Windows NT
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: benson.guthrie, Assigned: slogan)

Details

Attachments

(1 file)

I get the following message when I start mozilla: The procedure entry point ??_7nsLocalString@@6B@ could not be located in the dynamic link library xpcom.dll I press ok, mozilla loads. I am getting crashes when I "press" "buttons" on a web page, such as the login button on bugzilla - filling this out using NS 4.76 Build ID: 2001052304 Windows NT Version 4.0 ( Build 1381: Service pack 4)
forgot to mention, talkbacks were generated & sent on the mentiond button push crashes
crashes are probably dupe of 82359
Not sure, why is this a bug in the xp installer engine?
What are we playing with here? Did you build this? Is it a specific build you pulled from the nightlies (if so, which?). My guess is that we have some linker issue, there is nothing about installer that would cause this. Give me some more information, and some dates and version numbers, so I can figure out what to do.
further info: last dl was from http://ftp.mozilla.org/pub/mozilla/nightly/latest/ I've DL'd & installed twice now just incase the problem was with the DL the file is mozilla-win32-installer-sea-talkback.exe which was saved to my hard drive at 5:28 PM EDT the browser bar says Build ID: 2001052304 - as noted above
I'm still getting this with mozilla-win32-installer-sea-talkback.exe 23-May-2001 23:55 8.4M and now mozilla-win32-installer-sea-talkback.exe 24-May-2001 07:22 8.4M
I fell back to my last know good build: mozilla-win32-installer-sea-talkback.exe 23-May-2001 07:48 8.4M and got the recurring error, so I deleted prog. files\mozilla & all it's subs and reinstalled. problem did NOT appear. now running mozilla-win32-installer-sea-talkback.exe 24-May-2001 07:22 8.4M with no problems. sorry, I should have deleted mozilla completely when the problem first occured
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
No worries. Marking Verified.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: