https://bugs.winehq.org/show_bug.cgi?id=37549 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- (In reply to Todd Chester from comment #1)
Additional information:
Using msls31.dll (143 KB) from my M$ (Microsoft) XP (eXPensive) Virtual Machine (VM) in place of Wine's msls31.dll (1.0 KB) does allow Crimson 3 to install.
I also have Crimson 3 installed in a VM and am able to use it over there, although it would be far more convenient to use it in Wine. (Eventually this will go on a computer with Linux "Motion" installed on it. Be nice if I did not have the complication of a Virtual Machine as they are over this customer's head. But this won't happen any time soon.)
Three questins:
Question 1: whilst this bug runs its course, for testing purpose, do you want me to go back to the Wine version of msls31?
Native is fine, the bug is known.
Question 2: Winetricks has a DLL for this: $ winetricks dlls list | grep -i msls31 msls31 MS Line Services (Microsoft, 2001) [downloadable] riched30 MS RichEdit Control version 3.0 (riched20.dll, msls31.dll) (Microsoft, 2001) [downloadable]
Again, do you want me to stay with the Wine's or M$'s DLL whilst this bug runs its course?
Not sure what you're question is..use native as a workaround.
And, Crimson 3 seems to work with my databases without issue, except Crimson 3 crashes when you try to exit with:
fixme:msvcrt:__clean_type_info_names_internal (0x1350dac) stub
Try native vcrun (winetricks).
Question 3: do you want a separate bug opened for the crash on exit issue?
Yes, please. *** This bug has been marked as a duplicate of bug 32335 *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.