http://bugs.winehq.org/show_bug.cgi?id=17119
Andrew Nguyen arethusa26@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bunglehead@gmail.com
--- Comment #3 from Andrew Nguyen arethusa26@gmail.com 2009-07-31 08:29:57 --- With wine-1.1.26-231-gfe9d360, the problem currently appears to be an issue in comctl32, despite the bare backtrace seen most of the time. On a few runs, I have been able to see a backtrace in comctl32:
Backtrace: =>0 0x68623e62 PROPSHEET_SetCurSel+0x3e2(hwndDlg=0x1004a, index=4, skipdir=1, hpage=(nil)) [/home/abuild/rpmbuild/BUILD/wine-1.1.26.20090724/dlls/comctl32/propsheet.c:2099] in comctl32 (0x0030f6c0) 1 0x68626a7b PROPSHEET_DialogProc+0x19bb(hwnd=0x1004a, uMsg=<register ESI not in topmost frame>, wParam=4, lParam=0) [/home/abuild/rpmbuild/BUILD/wine-1.1.26.20090724/dlls/comctl32/propsheet.c:3600] in comctl32 (0x0030fa30) 2 0x683bdb8a WINPROC_wrapper+0x1a() in user32 (0x0030fa60) ...
Using winetricks comctl32 allows DiscSpeed to successfully start. The application can be obtained from http://www.videohelp.com/download/NeroDiscSpeed_41120.zip and a log which contains mostly irrelevant +aspi traces and the comctl32 backtrace is attached.