https://bugs.winehq.org/show_bug.cgi?id=37549
--- Comment #1 from Todd Chester ToddAndMargo@zoho.com --- 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?
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?
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 fixme:msvcrt:__clean_type_info_names_internal (0x384dbec) stub fixme:msvcrt:__clean_type_info_names_internal (0x37750f4) stub fixme:msvcrt:__clean_type_info_names_internal (0x22b91ec) stub fixme:msvcrt:__clean_type_info_names_internal (0x37207dc) stub fixme:msvcrt:__clean_type_info_names_internal (0x23a73bc) stub fixme:msvcrt:__clean_type_info_names_internal (0x1d9dc84) stub fixme:msvcrt:__clean_type_info_names_internal (0x21e64b4) stub fixme:msvcrt:__clean_type_info_names_internal (0x2013d2c) stub fixme:msvcrt:__clean_type_info_names_internal (0x1ff3584) stub fixme:msvcrt:__clean_type_info_names_internal (0xbe474c) stub fixme:msvcrt:__clean_type_info_names_internal (0xe56aa4) stub fixme:msvcrt:__clean_type_info_names_internal (0xe794c4) stub fixme:msvcrt:__clean_type_info_names_internal (0x3e76d4) stub fixme:msvcrt:__clean_type_info_names_internal (0x4f225c) stub fixme:msvcrt:__clean_type_info_names_internal (0x3adbcc) stub fixme:msvcrt:__clean_type_info_names_internal (0x15036344) stub fixme:msvcrt:__clean_type_info_names_internal (0x14018444) stub fixme:msvcrt:__clean_type_info_names_internal (0x1302b9b4) stub fixme:msvcrt:__clean_type_info_names_internal (0x367ddc) stub fixme:msvcrt:__clean_type_info_names_internal (0x12009714) stub fixme:msvcrt:__clean_type_info_names_internal (0x1101f6ec) stub
Question 3: do you want a separate bug opened for the crash on exit issue?
-T