Closed Bug 22682 Opened 26 years ago Closed 26 years ago

M12 can't start

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lld.girard, Unassigned)

Details

(Whiteboard: DUPLICATE of the JS3250.DLL M12 msvcrt.dll crash (?))

I'm using Windows 98 (French edition). It is impossible to start M12. I reboot on Windows NT (4.0 - French edition) and I have the same problem. Here is the message I get : MOZILLA a causé une défaillance de page dans le module JS3250.DLL à 015f:609c0537. Registres : EAX=140480d9 CS=015f EIP=609c0537 EFLGS=00010282 EBX=000000d0 SS=0167 ESP=0063f5dc EBP=0063f5e8 ECX=0000001a DS=0167 ESI=0063f83c FS=0f37 EDX=0063f8d0 ES=0167 EDI=00000000 GS=0000 Octets à CS : EIP : 88 18 0f b6 99 84 b5 9e 60 85 db 7e 1a 6a 00 56 État de la pile : 008e27d0 0063f83c 006f90e0 0063f6e8 609bdd7d 008e27d0 0063f83c 0000001a 008e27d0 0063f83c 006f90e0 0063f8c4 006e8bb0 0063f650 00000000 609d4d1d I hope this could help. didier
Whiteboard: DUPLICATE of the JS3250.DLL M12 msvcrt.dll crash (?)
http://www.mozilla.org/projects/seamonkey/release-notes/m12-detail.html#WIN32_IN STALL | Important: You must run the Seamonkey installer at least once when | installing M12. The installer updates some system DLLs that the zip file | cannot change. These updated system DLLs are necessary to prevent a crash | on launch of Seamonkey. Have you run this installer? If not, you will get exactly the crash that you note.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Solve by running Seamonkey installer (This soft is hard to find...)
Status: RESOLVED → VERIFIED
lld.girard@wanadoo.fr : I agree [based on the number of similar bug reports] that this requirement is not sufficiently clear, and it's also not clear enough (apparently) which package need to download. I am going to file a bug on this point -- the M13 Release Notes must make this clearer. Thanks for resolving this bug report. Marking VERIFIED.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.