[Bug 15981] New: Rhapsody 3 and 4 crash at end of autoupdate install

http://bugs.winehq.org/show_bug.cgi?id=15981

Summary: Rhapsody 3 and 4 crash at end of autoupdate install
           Product: Wine
           Version: 1.1.7
          Platform: Other
               URL: http://service.real.com/rhapsody/download/version4/
        OS/Version: other
            Status: NEW
          Keywords: download, Installer
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

A user in
http://real.lithium.com/real/board/message?board.id=InstallingRhapsody&m...
asked about Rhapsody, so I had a look at all the freely
downloadable versions I ran into.  (Bug 15980 is about version 2.)

Installing the Listen version of Rhapsody, either
http://service.real.com/rhapsody/download/version3/
http://service.real.com/rhapsody/download/version4/
succeeds; on startup, it autoupdates to the
newest version (and you have to avoid accepting the
autoupdate prompt more than once, or you'll start
multiple concurrent autoupdate installs).
Sadly, though, the autoupdater crashes on completion:

Unhandled exception: page fault on read access to 0x62ee1340 in 32-bit code
(0x62ee1340).
Backtrace:
=>1 0x62ee1340 (0x0033ecc0)
  2 0x7ec07b9a call_window_proc+0x6a(hwnd=<?>, msg=<?>, wp=0, lp=3404588,
result=0x33ed94, arg=0x62ee1340) [dlls/user32/winproc.c:458] in user32
(0x0033ed00)
  3 0x7ec0cec7 WINPROC_call_window+0xf7(hwnd=<?>, msg=129, wParam=0,
lParam=3404588, result=0x33ed94, unicode=0, mapping=WMCHAR_MAP_SENDMESSAGE)
[dlls/user32/winproc.c:2218] in user32 (0x0033ed40)
  4 0x7ebcc631 call_window_proc+0x91(hwnd=<?>, msg=<?>, wparam=0,
lparam=3404588, unicode=0, same_thread=1, mapping=WMCHAR_MAP_SENDMESSAGE)
[dlls/user32/message.c:1634] in user32 (0x0033eda0)
  5 0x7ebd1875 send_message+0x1d5(info=<?>, res_ptr=0x33ee3c, unicode=0)
[dlls/user32/message.c:2465] in user32 (0x0033ee00)
  6 0x7ebd1d33 SendMessageA+0x53(hwnd=0x60062, msg=129, wparam=0,
lparam=3404588) [dlls/user32/message.c:2610] in user32 (0x0033ee40)
  7 0x7ebff0a0 WIN_CreateWindowEx+0x1450(cs=0x33f32c, className=0x8002,
flags=32) [dlls/user32/win.c:1190] in user32 (0x0033f100)
  8 0x7ec0030a CreateWindowExA+0x6a(exStyle=1, className=*** invalid address
0x8002 ***, windowName="", style=2160591040, x=357, y=81, width=278,
height=105, parent=0x600e4, menu=(nil), instance=0x10000000, data=(nil))
[dlls/user32/win.c:1391] in user32 (0x0033f360)
  9 0x7eb97159 DIALOG_CreateIndirect+0x6a9(hInst=0x10000000, dlgTemplate=<?>,
owner=0x600e4, dlgProc=0x100146e5, param=0, unicode=0, modal=1)
[dlls/user32/dialog.c:621] in user32 (0x0033f530)
  10 0x7eb99a38 DialogBoxParamA+0x78(hInst=<?>, name=*** invalid address 0x72
***, owner=0x600e4, dlgProc=0x100146e5, param=0) [dlls/user32/dialog.c:808] in
user32 (0x0033f550)

I have a feeling our DialogBoxParam isn't doing the right thing
with that name parameter...