http://bugs.winehq.org/show_bug.cgi?id=13194
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.ne | |t
--- Comment #8 from Jörg Höhle hoehle@users.sourceforge.net 2011-04-16 03:55:12 CDT --- There are reasons to believe this is (again) a case-sensitivity issue. I did not try out the mentioned apps, but looked at the xvid.org source DRV_OPEN : if (icopen != NULL && icopen->fccType != ICTYPE_VIDEO) // 'vidc', not 'VIDC' return DRVCNF_CANCEL; // NULL Juan Lang's trace snippet in comment #2 shows that VIDC (upper case) is being used to attempt to open the driver, but it wants a lower case "vidc".
dlls/msvfw/tests/mvfw.c demonstrates that ICOpen is case-insensitive (at least with msvideo now, iccvid originally). Back then we changed both ICOpen and the lower-level Wine drivers to be case-insensitive. However, I since found out that at a lower-level, there's case-sensitivity involved. IIRC, ICLocate is case-sensitive, oddly I find no mention of my test in my copious notes. So there's still work to be done to exactly mimic native behaviour.
Meanwhile, you can check whether c:/windows/system.ini and [HKLM\Software\Microsoft\Windows NT\CurrentVersion\Drivers32] contain lower-case mention of vidc only, i.e. is this an installation issue? I suspect the codec will open if you manage to see lower-case 'vidc' in msvideo:ICOpen and driver:OpenDriver, driver:DRIVER_GetLibName traces.
You may wish to hack msvideo_main.c:ICOpen to force VIDC to vidc to verify my hypothesis. if (fccType == mmioFOURCC('V', 'I', 'D', 'C')) fccType=ICTYPE_VIDEO;
BTW, I'm thankful for any pointers to open source MCI or audio drivers (msacm or VFW drivers are not in my focus yet).