winmm: MCI system commands are not eligible for auto-open. (try 2)

Joerg-Cyril.Hoehle at t-systems.com Joerg-Cyril.Hoehle at t-systems.com
Mon Apr 12 07:11:30 CDT 2010


Hi,

>Also it fails here:
>mci.c:808: Test failed: got 0008 instead of MCI_NOTIFY_xyz 0000 from command sound notify
That's what I deserve for changing the order of patches in my git
tree without re-testing every one anew.  I'm sorry.

Here's a version where I pulled the notification patches out of
another patch of mine.  That later patch makes MCI_STRING work, but
must wait until after the 64bit MCI parser patches are somehow accepted,
as I'm not going to submit a patch that reads data[8]=(DWORD_PTR)abc;

For now I don't plan a rewrite of the parser because I've not yet thought
about it enough to be sure to handle all corner cases -- and last but not
least, we still don't know what magic constants the resources inside a 64bit
winmm.dll or mciavi.dll use.

Regards,
 Jörg Höhle.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-winmm-MCI-system-commands-are-not-eligible-for-auto.patch
Type: application/octet-stream
Size: 2844 bytes
Desc: 0002-winmm-MCI-system-commands-are-not-eligible-for-auto.patch
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20100412/acbd25cd/attachment-0001.obj>


More information about the wine-patches mailing list