http://bugs.winehq.org/show_bug.cgi?id=17403
--- Comment #18 from diafero@arcor.de 2012-12-20 12:03:56 CST --- (In reply to comment #17)
diafero or Gyb, please show md5sums of at least one file generated by Decompress.Exe a) on a native box or with a native winmm.dll (identical according to comment #7) and b) with Wine's winmm.dll. That'll allow others, e.g. Rosanne to assess what sort of file they got.
md5sums of broken files: f773fa6cb852a1baf6b6fbd7f2851a6f xLink-Stereo.wav a20e6a6b0d91a475003b81616f3c688e xLink.wav
md5sums of correct files (copied from a Windows installation): 99288161b22accc823e910757765e3c2 xLink-Stereo.wav 1ce28dee24d8dcc1a49342f9f4586a4e xLink.wav
winepulse should make no difference in an original winmm bug. It may make a difference w.r.t. the crash initially reported in comment #11. BTW, attaching a backtrace (from Wine compiled from source incl. debug info) may help with crashes, together with a short log of the last calls prior to the crash.
How do I catch such a backtrace? When the crash happened, the application still had the X cursor grabbed, so I had to Ctrl-Alt-Backspace to get rid of it... I can of course try to redirect all output to some file, but will the default output contain all necessary information? Also, I have no idea whether my compiled-from-source wine has debug information, but I guess I will be able to tell from the backtrace^^