Wine avitools/aviplay fails with CO_E_NOTINITIALIZED for any
AVI file
Robert Shearman
rob at codeweavers.com
Fri Jul 1 15:50:28 CDT 2005
Marcus Meissner wrote:
>On Thu, Jun 30, 2005 at 03:09:35PM -0500, Alex Villacís Lasso wrote:
>
>
>>>It worked in the past. When pclsidHandler is set to NULL it performs
>>>a registry lookup as the native version does it. If these registry
>>>entries are missing it has a problem and could perhaps return the
>>>mentioned error - don't know as I have never tested it.
>>>
>>>In the past these informations were part of the default registry of
>>>wine but with the addition of the self-registration of many libraries
>>>this has been removed. Don't ask me how to get the library to
>>>register itself - guess it has to do with regsrv32.exe, but I am not
>>>sure. I am already too long out of the substance.
>>>
>>>
>>>
>>>
>>Based on a certain verification in the source code, I made aviinfo to
>>work by adding the following to the registry:
>>
>>
>
>I atually fixed avifil32 now, by adding an OleINitialize() to
>AVIFileInit().
>
>
You probably don't want OleInitialize as it also creates a lot of other
stuff that you don't need like resources for supporting OLE drag-n-drop.
Also, why didn't you call the correspoding uninitialize function? I've
seen some nasty deadlocks that are caused by not calling CoUninitialize
at the right time (with marshaled objects still active).
--
Rob Shearman
More information about the wine-devel
mailing list