http://bugs.winehq.org/show_bug.cgi?id=29199
Bug #: 29199 Summary: iexplore: Crashing when opening with DLL overrides Product: Wine Version: 1.3.33 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: supimbao@gmail.com Classification: Unclassified
Created attachment 37696 --> http://bugs.winehq.org/attachment.cgi?id=37696 Complete error log
I installed some DLL overrides: gdiplus, msvcr100, msvcr80, msvcr90, msvcrt, msxml3, msxml4, msxml6, riched20 and riched32 so I can use Office 2007 and now the built-in iexplore won't run. I believe it's a regression, because it used to run fine in wine 1.2.3.
http://bugs.winehq.org/show_bug.cgi?id=29199
supimbao@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #37696|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=29199
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |jacek@codeweavers.com Resolution| |INVALID
--- Comment #1 from Jacek Caban jacek@codeweavers.com 2011-11-29 14:52:56 CST --- Most likely msvcrt is to blame, but this bug is invalid. You're running in an unsupported environment. The right fix is not to use native overrides.
http://bugs.winehq.org/show_bug.cgi?id=29199
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #2 from Austin English austinenglish@gmail.com 2011-11-29 15:47:56 CST --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=29199
--- Comment #3 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2011-11-29 19:29:49 CST ---
Unhandled exception: unimplemented function msvcrt.dll._localtime64 called in 32-bit code (0x7bc4a000).
To clarify, you using either too old version of msvcrt, or the one from a wrong platform. In either case, the bug is still invalid.