http://bugs.winehq.com/show_bug.cgi?id=1480
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2003-22-05 08:24 -------
First, a Windows pop-up appears with this message:
A newer version of DCOM95 or DCOM98 has been installed. To override, you must uninstall trhe current version first.
for this one you could try instructing wine to use native version of OLE32.DLL for dcom-update process, even if this DLL is missing in clean-wine install. I mean you can add "--dll ole32=n" to command line, as for example:
wine --dll ole32=n filemaker.exe
or you could try adding line "ole32" = "native" to your wine config-file, into that (possibly new) section:
[AppDefaults\install.exe\DllOverrides] "ole32" = "native"
there is "install.exe" used here because dcom98 updater (could be downloadded from MS web) I was experimenting with was spawning child processes and needed this dll-override only for "install.exe". though, dll-override from command line seems to be more strict.
Later, the install fails completely, with this message coming from wine: fixme:cabinet:FDICreate (pfnalloc == ^0x244f90b0, pfnfree == ^0x244f90be, pfnopen == ^0x244f90cc, pfnread == ^0x244f9294, pfnwrite == ^0x244f9401, pfnclose == ^0x244f956a, pfnseek == ^0x244f95f4, cpuType == -1, perf == ^0x2453fae8): stub
Please help.
eghm.. I think this one could be solved by such dll-override:
cabinet=n
and I would override cabinet.dll usage globally, for example by putting it to section:
[DllOverrides] "cabinet" = "native" ..
BTW, I cannot remember where did cabinet.dll come from. was it DCOM98 update, or was it MSI package? whatever, good luck with wine :)