> > > Is anybody else using the Indeo5 Codec under wineLib besides me?
> >
> > Not me.
> >
> > > I am having a problem where if I Initialize the Indeo Codec
> > > more than four
> > > times it starts throwing exceptions. c0000005
> >
> > I probably misunderstood you but:
> > Why do you try to initialize it FOUR times?
> > It doesn't make any sense.
> >
>
> I am writing a server that streams live video. Each
> connected client can
> choose which Codec to use for compression.
OK.
> The Indeo5 codec can only be in use four times. One for each
> client. Any
> subsequent calls will fail and WINE will throw an exception.
Has each client connection a separate thread or a separate process?
If it has a separate thread perhaps it only need to be initialized
once in either of the threads. If not perhaps the Indeo5 Codec is
broken (or deliberately limited). Are you _really_ sure this works
on Windows?
If it has a separate process, I have no idea. If the Codec works under NT
(does it?), it really can't share any memory between the processes as
easily as it can under Windows 9x.
> > > Wine also reports this error three times: "err:
> > > module:BUILTIN32_dlopen
> > > failed to load libir50_lcs.so: /root/wine/cvs/libir50_lcs.so:
> > > cannot open
> > > shared object file"
> >
> > It needs a DLL called IR50_LCS.DLL. This is not a standard DLL
> > so I presume it is part of Indeo 5. Just copy it to the
> > Wine System directory.
> >
>
> That's just it. There is no IR50_LCS.DLL. The Codec will
> work just fine
> without it so I didn't worry about it to much.
> All that Indeo has is: Ir50_32.dll, Ir50_qc.dll, and Ir50_qcx.dll.
Perhaps it just something optional that it tries to load and this
fails just as it in such case must do for your Windows installation
as well.
