On Mon, 07 Nov 2005 02:56:18 +0100, Robert Shearman rob@codeweavers.com wrote:
I did install DCOM98 , is there anything above that makes you still think this is a dcom95 version of rpcrt4.dll? Here is a dependency tree for the status in RPC_StartRemoting: RPC_StartRemoting -> RpcServerUseProtseqEpW RpcServerUseProtseqEpW -> RpcServerUseProtseqEpExW RpcServerUseProtseqEpExW -> RPCRT4_use_protseq RPCRT4_use_protseq returns RPC_S_OK. Analysing all of the above functions shows that the *only* status that will be returned by builtin rpcrt4 is RPC_S_OK, therefore builtin rpcrt4 is not being used. (The fact that it doesn't return anything but RPC_S_OK is a bug though. )
Sorry, you are of course right. It was late and I had tried so many combinations I forgot what I had written in the original post.
I was encouraged by the fact that a lot of issues in oleaut32 had been fixed and wanted to push on with testing ole32 which is still problematic.
I had not realised that rpcrt4 was part of ole.
Is it still too early to expect much from wine ole and just add all ole related dlls to winecfg as native only?
Thanks for looking at this.