Tech Support > Computer Hardware > Desktops > 16-bit codecs under windows xp
16-bit codecs under windows xp
Posted by blah on August 12th, 2004


Anyone know of a way to make 16-bit codecs work under Windows 2000 or XP?
I'm particularly interested in getting Indeo 2.1 and ATI VCR1 to work.


P.S: This is what I already know:
Assuming your codec has fourcc 4cc and the driver that handles it is named
yourcodec.dll

Under Windows 95 and 98, you modify your system.ini file by putting the line
vidc.4cc=yourcodec.dll under the [drivers] section.

In Windows 2000 and XP, for 32-bit codecs only, you go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
and place a string value named vidc.4cc with value yourcodec.dll




Posted by Ken Maltby on August 12th, 2004



"blah" <blah@blah.blah> wrote in message
news:uSMSc.9145$uj5.7054@fe22.usenetserver.com...
I've been playing around with "GraphEdit", a little program
that lets you work with the "filters", including codecs, that programs
call to do various A/V "Multimedia" functions. You can even patch
together a working capture, streamer and/or playback function within
GraphEdit. I've made a few captures using various modified filters,
and have only scratched the surface of what's there. You can have it
acquire the filter graph of most any running capture or playback app.
You can even build one from scratch, using whatever components are
installed on your system.

Don't know if you can fix your problem this way but you can get a
lot of information on your installed codecs, including the 4C variety.
You may just need to up it's "Merit" number, which you can do with
GraphEdit.

Luck;
Ken



Posted by Bariloche on August 13th, 2004


On Thu, 12 Aug 2004 12:26:01 -0400, "blah" <blah@blah.blah> wrote:

Actually, under the [drivers32] section.

Posted by blah on August 13th, 2004


"Bariloche" <bariloche@bariloche.com> wrote in message
news:ifdph09b3durg40e0d94nbkvg412n667ls@4ax.com...
It's [drivers32] if it's a 32-bit codec. [drivers] if it's a 16-bit codec.
Sorry I should have been clearer.




Posted by Bariloche on August 14th, 2004


On Fri, 13 Aug 2004 16:09:09 -0400, "blah" <blah@blah.blah> wrote:

I think you are right. I was under a different impression after seeing
in my Win98 System.ini [drivers] section, entries like

wavemapper=*.drv
MSACM.imaadpcm=*.acm
MSACM.msadpcm=*.acm

but now I see there's also

VIDC.MJPG=CAPCDC.drv

which is the 16-bit capture driver of the DC10+ card.


Similar Posts