Closed Bug 182473 Opened 23 years ago Closed 23 years ago

startup errors messages about procedure entry points and preferences not working

Categories

(Core :: XPCOM, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: mozilla, Assigned: dougt)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 when i startup mozilla i get the following messages as modal popup windows: The procedure entry point ?ToNewCString@nsString@@QBEPADXZ could not be located in the dynamic link library xpcom.dll The procedure entry point ?ToNewUnicode@nsString@@QBEPAGXZ could not be located in the dynamic link library xpcom.dll The procedure entry point ??OnsOutputConsoleStream@@QAE@Xz could not be located in the dynamic link libreary xpcom.dll The procedure entry point ?AssignFromReadable@nsAString@@IAEXABV1@@Z could not be located in the dynamic link libreary xpcom.dll I then click ok to them all and the browser starts. When i then open the preferences page, then it doesn't work... i can only se the first page it opens, and cannot choose any of the others from the menu on the left, it doesn't matter how much i click the mouse on the menu, nothing happens. Reproducible: Always Steps to Reproduce: 1. click the mozilla logo 2. type ok to all the erros 3. open the preferences window 4. try to click on the left side menu Actual Results: nothing - thats the problem Expected Results: mozilla shoulnd't have given error messages, and the preferences window should have worked by responding to my mouseclicks on the elft side menu
-> invalid Please install mozilla 1.2 in a clean and empty directory. Please reopen if this is true : You used the installer build You have no third-party applications like spellchecker/enigmail installed in your old build You installed over an older mozilla build (and not Netscape..)
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.