When I run M12 mozilla.exe I get a Dr. Watson error: Exception access violation (0xc000005), Address 0x609c0537 The profile configurator runs then the dos panel shows: WEBSHELL- = 0 WEBSHELL+ = 1 WEBSHELL+ = 2 then it crashes. Let me know what other info I can provide.
Assignee: ssu → nobody
Component: Installer → Browser-General
Crash starting mozilla, not the install. Would help to know exactly what configuration you installed, and whether you had installed a previous mozilla (old data laying around?)
from reporter: I just checked. NT 4.0 SP 3 Netscape 4.7 Mozilla 10 and 11 were installed before and worked. Per the deinstallation instructions I removed the old directories and profiles. Here are screen shots of what happens. The profile window does come up and work fine. [[ MAPI 1.0 storage : 3362 in WINMAIL.DAT ]] [[ MAPI 1.0 storage : 3363 in WINMAIL.DAT ]] Kevin Kwasniewski
email@example.com : If the the crash report is pointing at JS3250.DLL, then this is very likely bug #19165. Can you check the version numbers for MSVCRT.DLL and MSVCIRT.DLL (typically in C:\WinNT\System32 on NT, but that depends on how your OS was installed). The version numbers for the Microsoft C Runtime Libraries MSVCRT.DLL and MSVCIRT.DLL must be (at minimum) 6.0.8168.0. However, the installer will update these DLLs as required (but will require a reboot). Have you run the installer?
firstname.lastname@example.org : does this still crash for you, or have you run the installer and it works for you now? See the release notes (or bug #19165) for more information, but if your MSVCRT.DLL and MSVCIRT.DLL have version numbers below 8.0.8168.0, then this crash is a known problem that installer will resolve for you. Thanks.
Adding "crash" keyword to all known open crasher bugs.
ckkwas, Is this still a problem for you? Have you tried to install more recent builds? Grace
this bug was fixed. Please get latest build at: http://www.mozilla.org/projects/seamonkey/release-notes/ M13 is your answer :-)
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.