[Bug 2864] New: Intel Indeo5 video playback fails: "MCI:Could not create or use window"

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2864

Summary: Intel Indeo5 video playback fails: "MCI:Could not create
                    or use window"
           Product: Wine
           Version: CVS
          Platform: PC
               URL: http://www.winehq.org/appview.php?appid=502
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: wine-multimedia
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

The error occurs with the in game cut scenes for the game  
Kings Quest 8 by Sierra-Online/Vevindi Universal.

First of all, the file containing the data is called "w32opn_1.dll",  
which confuses wines MCI selection, since it doesn't know what to  
to with .dll files.  
Launching the game as "WINEDEBUG=+mci wine Mask.exe" gives the following  
output:  
...  
trace:mci:MCI_GetDevTypeFromFileName No ...\MCI Extensions entry for L".dll"  
found.  
...

I've added the following key to the registry to bypass this problem:  
system.reg:  
 [Software\Microsoft\Windows NT\CurrentVersion\MCI Extensions] 1112712291  
  "dll"="AVIVideo"

Loading the game now it recognises the AVIVIDEO entry.  
...  
trace:mci:MCI_LoadMciDriver Loaded driver 0x77cb1548 (L"AVIVIDEO"), type is  
520, cmdTable=00000001  
...

Unfortunately the video doesn't start playing:  
...  
trace:mci:MCI_Open Failed to open driver (MCI_OPEN_DRIVER) [0000015b], closing  
...

It seems asif winmm recognised that the video file is encoded in Indeo5:  
...  
0009:Call msvfw32.ICLocate(63646976,30357669,77cb3cc0,00000000,00000002)  
ret=73cd7a9f  
0009:Call winmm.OpenDriver(77abd018 L"vidc.iv50",779bcf84  
L"drivers32",77abcfe8) ret=779b5e9e  
0009:Call advapi32.RegOpenKeyExW(80000002,7798f440  
L"Software\Microsoft\Windows NT\CurrentVersion",00000000,00000001,77abcd78)  
ret=77940e19  
0009:Ret  advapi32.RegOpenKeyExW() retval=00000000 ret=77940e19  
0009:Call advapi32.RegOpenKeyExW(000000a8,779bcf84  
L"drivers32",00000000,00000001,77abcd74) ret=77940e48  
0009:Ret  advapi32.RegOpenKeyExW() retval=00000002 ret=77940e48  
0009:Call advapi32.RegCloseKey(000000a8) ret=77940e5c  
0009:Ret  advapi32.RegCloseKey() retval=00000000 ret=77940e5c  
0009:Call PE DLL (proc=0x10073e60,module=0x10000000  
L"ir50_32.dll",reason=PROCESS_ATTACH,res=(nil))  
0009:Ret  PE DLL (proc=0x10073e60,module=0x10000000  
L"ir50_32.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1  
0009:Call advapi32.RegOpenKeyExA(80000002,10098460  
"HARDWARE\DESCRIPTION\System\FloatingPointProcessor",00000000,00020019,77abcc28)  
ret=100349c7  
0009:Ret  advapi32.RegOpenKeyExA() retval=00000000 ret=100349c7  
0009:Call advapi32.RegCloseKey(000000a8) ret=100349dc  
0009:Ret  advapi32.RegCloseKey() retval=00000000 ret=100349dc  
0009:Call advapi32.RegOpenKeyExA(80000001,10098abc  
"Software\Intel\Indeo\5.0",00000000,000f003f,77abcba4) ret=10043c6f  
0009:Ret  advapi32.RegOpenKeyExA() retval=00000002 ret=10043c6f  
0009:Ret  winmm.OpenDriver() retval=77cc6610 ret=779b5e9e  
0009:Call winmm.GetDriverFlags(77cc6610) ret=779b5cc9  
0009:Ret  winmm.GetDriverFlags() retval=80000000 ret=779b5cc9  
0009:Call winmm.SendDriverMessage(77cc6610,0000400b,77cb3cc0,00000000)  
ret=779b713d  
0009:Ret  winmm.SendDriverMessage() retval=00000000 ret=779b713d  
0009:Ret  msvfw32.ICLocate() retval=00000001 ret=73cd7a9f  
0009:Call  
msvfw32.ICGetDisplayFormat(00000001,77cb3cc0,77ce4ae8,00000000,00000000,00000000)  
ret=73cd7bd6  
0009:Call winmm.SendDriverMessage(77cc6610,0000400b,77cb3cc0,00000000)  
ret=779b713d  
0009:Ret  winmm.SendDriverMessage() retval=00000000 ret=779b713d  
0009:Call winmm.SendDriverMessage(77cc6610,0000400a,77cb3cc0,77ce4ae8)  
ret=779b713d  
0009:Ret  winmm.SendDriverMessage() retval=00000000 ret=779b713d  
0009:Ret  msvfw32.ICGetDisplayFormat() retval=00000001 ret=73cd7bd6  
0009:Call msvfw32.ICSendMessage(00000001,0000400c,77cb3cc0,77ce4ae8)  
ret=73cd7cc5  
0009:Call winmm.SendDriverMessage(77cc6610,0000400c,77cb3cc0,77ce4ae8)  
ret=779b713d  
0009:Ret  winmm.SendDriverMessage() retval=00000000 ret=779b713d  
0009:Ret  msvfw32.ICSendMessage() retval=00000000 ret=73cd7cc5  
0009:Call window proc 0x73cd87d0  
(hwnd=0x1002c,msg=WM_GETMINMAXINFO,wp=00000000,lp=77abcc18)  
0009:Ret  window proc 0x73cd87d0  
(hwnd=0x1002c,msg=WM_GETMINMAXINFO,wp=00000000,lp=77abcc18) retval=00000000  
0009:Call window proc 0x73cd87d0  
(hwnd=0x1002c,msg=WM_NCDESTROY,wp=00000000,lp=00000000)  
0009:Ret  window proc 0x73cd87d0  
(hwnd=0x1002c,msg=WM_NCDESTROY,wp=00000000,lp=00000000) retval=00000000  
0009:Call winmm.mmioClose(00000001,00000000) ret=73cd3b18  
0009:Ret  winmm.mmioClose() retval=00000000 ret=73cd3b18  
0009:Call msvfw32.ICClose(00000001) ret=73cd3cc1  
0009:Call winmm.CloseDriver(77cc6610,00000000,00000000) ret=779b86c8  
0009:Call PE DLL (proc=0x10073e60,module=0x10000000  
L"ir50_32.dll",reason=PROCESS_DETACH,res=(nil))  
0009:Ret  PE DLL (proc=0x10073e60,module=0x10000000  
L"ir50_32.dll",reason=PROCESS_DETACH,res=(nil)) retval=1  
0009:Ret  winmm.CloseDriver() retval=00000001 ret=779b86c8  
0009:Ret  msvfw32.ICClose() retval=00000000 ret=73cd3cc1  
...

If need be I can post more detailed logs. Just drop a note.

Regards, 
-frikkie thirion