[Bug 1376] InstallShield 6 hangs after Wizard setup.

[Wine Bugs]

http://bugs.winehq.com/show_bug.cgi?id=1376

------- Additional Comments From [e-mail]  2003-28-06 10:48 -------
Bug comments restored from Gmane.org:

While trying to install an app that uses InstallShield 6 (Watchtower Library
2001), the installation process hangs after the "Wizard setup" window closes.

The following message appear on the console:

fixme:seh:check_resource_write Broken app is writing to the resource data,
enabling work-around
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})
))))cannot set text "InstallShield Wizard" of other process window (nil)
fixme:ole:_copy_arg argument was coerced in-place (0x3 -> 0xb); source data has
been modified!!!
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{00000000-0000-0000-0000-000000000000})
fixme:ole:_xread Read only 0 of 4 bytes from 0x48.
fixme:ole:_StubReaderThread Failed with hres 80004005

This appears on a build done from an uptodate cvs checkout (April 8 2003). The
install was being done to a fake-windows directory tree.

------- Additional Comments From [e-mail]  2003-04-09 04:21 -------
Do you have stdole32.tlb? Try installing DCOM98, that may help

------- Additional Comments From [e-mail]  2003-04-09 11:37 -------
Yep, DCOM98 is installed and stdole32.tlb is at
/usr/share/wine-c/windows/system/stdole32.tlb.

------- Additional Comments From [e-mail] 
2003-05-07 15:55 -------
Marcus did some work on
_copy_arg argument was coerced in-place

Did you try a recent version?

------- Additional Comments From [e-mail]  2003-05-07 17:48 -------
I've been testing with updated builds from my cvs checkout every 2-5 days
(thought today was the first time in a week or so). Just tried with a current
checkout. I now get the following output on console:

fixme:seh:check_resource_write Broken app is writing to the resource data,
enabling work-around
FIXME:pthread_cond_init
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})
FIXME:pthread_cond_init
FIXME:pthread_cond_init
fixme:ole:CoTreatAsClass
({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-4432-b3ed-a9dca3604594})

Instead of just hanging, I now get an error message after the "Wizard setup"
window closes. The window states: "An error occurred while launching the seupt.
(0x80004002)" After clicking "Ok" on the error message, the installation hangs.

Not very informative to me, but . . .

------- Additional Comments From [e-mail]  2003-05-07 19:23 -------
80004002L is E_NOINTERFACE, which says you could have a problem
with the matching InstallShield dll, Ilog.dll.

A quick look in regedit shows :
C:\Program Files\Common Files\InstallShield\engine\6\Intel 32\ILog.dll
C:\Program Files\Common Files\InstallShield\engine\6\Intel 32\iKernel.exe