out-of-process COM design

[Bill Medland]

Is there any chance of help here, please.

For one reason or another I need to help get the ole32/oleaut32/rpcrt4 working 
for our application (the REG_EXPAND_SZ issue means that we don't work with 
wine after 200409 because of the mix of native dlls we use)

I just tried running with the native ole32/oleaut32/rpcrt4 and the first thing 
I tripped over was (what I presume is) an out-of-process COM problem.

The actual stack dump is that:
_LocalServerThread (compobj.c)
    calls  StdMarshalImpl_MarshalInterface (...)
        which has mid.oxid = COM_CurrentApt()->oxid;
which throws a memory error because COM_CurrentApt is null
because, presumably the thread hasn't yet initialised an apartment.

Does anyone know anything about this?  e.g. when starting a new thread where 
does the apartment get initialized?

-- 
Bill Medland
mailto:billmedland at mercuryspeed.com
http://webhome.idirect.com/~kbmed