[Bug 13726] handycafe.com installer unpacker hangs

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

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                URL|                            |http://www.handycafe.com
           Severity|enhancement                 |normal
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
           Keywords|                            |download, Installer
            Summary|Xp programs and games issues|handycafe.com installer
                   |with wine                   |unpacker hangs

--- Comment #1 from Dan Kegel   2008-06-06 06:39:54 ---
Let's make this bug report be about the handycafe.com installer hang.
Please file individual bug reports for the other problems.

I downloaded and ran the installer, handysetup.exe.
It's really a downloader that downloads the real installer, HandySetupSeEN.exe,
and offers to run it.  The downloader works fine.

HandySetupSeEN.exe is really just a self-extracting archive that gives
you a choice of whether to unpack and run the client or server installers.
If you say yes to either, it will happily unpack and start them,
but will then hang in the "Installing" screen that shows the progress
of unpacking the desired installer.  It seems to be hung in mid-animation;
the little fluttering page showing a document copy is stuck at the top of
its arc.
To see where it's hanging, look for the last call to CreateProcess
in +relay, then see what that thread does later.  Here's the sequence
of events, I think:

001b:Call user32.CreateWindowExA(00000000,003340c0
"AnimateWindow",00000000,50000000,000000a3,0000000d,00000119,00000032,0001002c,00000000,00330000,00000000)
ret=00331b49
001a:Ret  KERNEL32.CreateThread() retval=00000070 ret=003312e4
...
001a:Call KERNEL32.WaitForSingleObject(00000070,ffffffff) ret=003316f0
...
001b:Call user32.PostQuitMessage(00000000) ret=00331bbe
...
001b:Call PE DLL (proc=0x7ec1bc9c,module=0x7eb50000
L"user32.dll",reason=THREAD_DETACH,res=(nil))

At this point thread 001b is supposed to exit, and this is supposed
to wake up thread 001a so it can exit, but it doesn't for some reason.
Or something like that.