http://bugs.winehq.com/show_bug.cgi?id=752
*** shadow/752 Sat Jun 1 21:21:19 2002 --- shadow/752.tmp.7320 Tue Jun 4 11:37:49 2002 *************** *** 5,13 **** | Status: NEW Version: CVS | | Resolution: Platform: | | Severity: normal OS/Version: All | ! | Priority: P1 Component: wine-winelib | +----------------------------------------------------------------------------+ ! | Assigned To: wine-bugs@winehq.com | | Reported By: tazdev@altern.org | | CC list: Cc: | +----------------------------------------------------------------------------+ --- 5,13 ---- | Status: NEW Version: CVS | | Resolution: Platform: | | Severity: normal OS/Version: All | ! | Priority: P1 Component: wine-ole | +----------------------------------------------------------------------------+ ! | Assigned To: marcus@jet.franken.de | | Reported By: tazdev@altern.org | | CC list: Cc: | +----------------------------------------------------------------------------+ *************** *** 102,104 **** --- 102,117 ---- When I found the unpacked files and started Setup.exe I got the same Installshield window which hang indefinitely. It prints only fixme:ole:CoTreatAsClass. + + ------- Additional Comments From apa3a@yahoo.com 2002-06-04 11:37 ------- + After the first crash a few wine processes remain still in memory and the next + startup of the application hangs. It is necessary to kill all wine processes + afther the crash to reproduce the issue again. + Used for debugging the unpacked installer (see my previous comment) + + The crash happens in ole code. It seems the trouble starts after this fixme + message (should it be warn then?): + trace:ole:ITypeInfo_fnGetRefTypeInfo (0x403e43fc) hreftype 0x0000 loaded FAILURE + (0x13) + + Forwarding to Marcus, but anybody is free to take this bug. \ No newline at end of file