April 2005 - Wine-Devel - list.winehq.org

Re: Nearly all Installshield installers fail

by Mike Hearn

On Fri, 01 Apr 2005 10:53:36 +0200, Uwe Bonnes wrote: > nearly all recent install shield installer fail for me, similar like: I debugged this a bit with Maxime Bellenge, she sent me a full trace which revealed that this is a known problem. Here is a quick hacky patch to work around it: Index: stubmanager.c =================================================================== RCS file: /home/wine/wine/dlls/ole32/stubmanager.c,v retrieving revision 1.19 diff -u -p -r1.19 stubmanager.c --- stubmanager.c 17 Mar 2005 10:26:20 -0000 1.19 +++ stubmanager.c 23 Mar 2005 21:51:08 -0000 @@ -477,7 +481,7 @@ BOOL stub_manager_notify_unmarshal(struc default: WARN("object OID %s already unmarshaled\n", wine_dbgstr_longlong(m->oid)); - ret = FALSE; + ret = TRUE; /* FIXME */ break; } But I suspect you will hit further problems later.

April 1, 2005

Re: Nearly all Installshield installers fail

by Mike Hearn

On Fri, 01 Apr 2005 12:03:46 +0200, Marcus Meissner wrote: >> nearly all recent install shield installer fail for me, similar like: Which InstallShield version is this?

April 1, 2005

Re: Nearly all Installshield installers fail

by Marcus Meissner

On Fri, Apr 01, 2005 at 10:53:36AM +0200, Uwe Bonnes wrote: > Hello, > > nearly all recent install shield installer fail for me, similar like: > ... > fixme:ole:RegisterTypeLib Registering non-oleautomation interface! > fixme:sync:SetNamedPipeHandleState 0x1f0 0x42ad30e0 (nil) (nil) > fixme:sync:SetNamedPipeHandleState 0x214 0x42ddc0e0 (nil) (nil) > fixme:ole:RpcChannelBuffer_GetDestCtx (0x42551d8c,0x42551d90), stub! > fixme:sync:SetNamedPipeHandleState 0x214 0x432080e0 (nil) (nil) > fixme:ole:NdrConvert (pStubMsg == ^0x406cca80, pFormat == ^0x431041ba): stub. > fixme:ole:NdrConvert (pStubMsg == ^0x42551d18, pFormat == ^0x431041ba): stub. > err:ole:get_unmarshaler_from_stream Failed to read common OBJREF header, 0x00000000 > fixme:ole:RpcChannelBuffer_GetDestCtx (0x42551d88,0x42551d8c), stub! > fixme:sync:SetNamedPipeHandleState 0x1e8 0x42ff00e0 (nil) (nil) > fixme:ole:NdrConvert (pStubMsg == ^0x406cca7c, pFormat == ^0x431041c8): stub. > fixme:ole:NdrConvert (pStubMsg == ^0x42551d14, pFormat == ^0x431041c8): stub. > fixme:sync:SetNamedPipeHandleState 0x1e4 0x432080e0 (nil) (nil) > fixme:sync:SetNamedPipeHandleState 0x1e4 0x42bd60e0 (nil) (nil) > fixme:sync:SetNamedPipeHandleState 0x1e4 0x42ad30e0 (nil) (nil) > fixme:sync:SetNamedPipeHandleState 0x1ec 0x42bd60e0 (nil) (nil) > fixme:ole:_copy_arg Should not use VariantChangeType here. (conversion from 0x4003 -> 0x8) 42de13b4 > > Do I have some bogus registry entries, did I miss some dll registration or > is this the expected behaviour? Its one of the versions that do not work yet. Have not explored why yet ;) There is also one with MSI support that needs native MSI still. Ciao, Marcus

April 1, 2005

Nearly all Installshield installers fail

by Uwe Bonnes

Hello, nearly all recent install shield installer fail for me, similar like: ... fixme:ole:RegisterTypeLib Registering non-oleautomation interface! fixme:sync:SetNamedPipeHandleState 0x1f0 0x42ad30e0 (nil) (nil) fixme:sync:SetNamedPipeHandleState 0x214 0x42ddc0e0 (nil) (nil) fixme:ole:RpcChannelBuffer_GetDestCtx (0x42551d8c,0x42551d90), stub! fixme:sync:SetNamedPipeHandleState 0x214 0x432080e0 (nil) (nil) fixme:ole:NdrConvert (pStubMsg == ^0x406cca80, pFormat == ^0x431041ba): stub. fixme:ole:NdrConvert (pStubMsg == ^0x42551d18, pFormat == ^0x431041ba): stub. err:ole:get_unmarshaler_from_stream Failed to read common OBJREF header, 0x00000000 fixme:ole:RpcChannelBuffer_GetDestCtx (0x42551d88,0x42551d8c), stub! fixme:sync:SetNamedPipeHandleState 0x1e8 0x42ff00e0 (nil) (nil) fixme:ole:NdrConvert (pStubMsg == ^0x406cca7c, pFormat == ^0x431041c8): stub. fixme:ole:NdrConvert (pStubMsg == ^0x42551d14, pFormat == ^0x431041c8): stub. fixme:sync:SetNamedPipeHandleState 0x1e4 0x432080e0 (nil) (nil) fixme:sync:SetNamedPipeHandleState 0x1e4 0x42bd60e0 (nil) (nil) fixme:sync:SetNamedPipeHandleState 0x1e4 0x42ad30e0 (nil) (nil) fixme:sync:SetNamedPipeHandleState 0x1ec 0x42bd60e0 (nil) (nil) fixme:ole:_copy_arg Should not use VariantChangeType here. (conversion from 0x4003 -> 0x8) 42de13b4 Do I have some bogus registry entries, did I miss some dll registration or is this the expected behaviour? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

April 1, 2005

Re: WineConf Agenda

by Jakob Eriksson

Brian Vincent wrote: >I think a full agenda would be about 11 items. If you would like to >present something let me know - there's definitely space available. >If you've been wondering, "There's a neat project I'd like to do if I >could only get a few more people interested", well, this is the >perfect time to bring it up. If there's something strategic to Wine >development, this is a great time to discuss it. > > I don't know if I can find the time to prepare a proper presentation, but if I do, I'd like talk about and get some input from you on the subject of testing. 1) I want the conformance tests done faster. (I have a clear idea how.) 2) What's almost never been brought up on wine-devel is the unit testing in the XP sense. 1 has been discussed on wine-devel quite a bit, so I'll skip it in this mail. regarding 2: CXTest is like application testing. This is good, high-level testing. The conformance tests test the Windows API. But in the case of a complicated API (and Windows is complicated) maybe we need to test the smaller units behind the API. So, the conformance tests often are somewhere between application testing and unit testing. Can we have an infrastructure for running unit tests of small units of code private to the implementation? I.e. these tests, we could call them "private tests", would not run on Windows, but during build of Wine. Would it be acceptable to just include extra test code in the implementation c file, surrounded by #ifdef COMPILE_PRIVATE_TESTS ? regards, Jakob

April 1, 2005

Fwd: Re: [Wine]winetest and winrash

by Mitchell Mebane

Ivan Leo Puoti wrote: > Mitchell Mebane wrote: > >> Hey there, >> >> I ran it on my XP Pro SP2 desktop and Windows Server 2003 under >> VMWare just fine, but when I ran it on Win2K Pro SP4 under VMWare, it >> told me the log was too large (6.4 MB > 1 MB) and it would only send >> partial results. Is there any reason this log would be almost an >> order of magnitude larger than the others? >> > From the log it appears to be a problem with the PathIsValidCharA API, > you may want to report this to wine-devel. > > Ivan. > > . > OK, I'll do so. Results are on this page: http://test.winehq.com/data/200503311000/ Specifically, this: http://test.winehq.com/data/200503311000/2000_mmebane/shlwapi:path.txt The OS setup I ran the test under is pretty much a bare-bones Win2K Pro SP4 install. If you want any more information about it, let me know. --Mitchell -- The roots of education are bitter, but the fruit is sweet. --Aristotle

April 1, 2005