Re: winmm: Have MCI drivers handle notification for MCI_OPEN.

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=2193

Your paranoid android.

=== W98SE (32 bit mci) ===
mci.c:613: Test failed: Expect message 0001 from play to 250 wait notify
mci.c:620: Test failed: got 0004 instead of MCI_NOTIFY_xyz 0000 from command after close
mci.c:784: Test failed: mci pause wait returned MMSYSERR 5
mci.c:798: Test failed: mci pause (space) wait returned MMSYSERR 5
mci.c:801: Test failed: mci pause wait returned MMSYSERR 5
mci.c:815: Test failed: Expect message 0004 from play (aborted by close)

winmm: Have MCI drivers handle notification for MCI_OPEN.

Hi,
> http://testbot.winehq.org/JobDetails.pl?Key=2193
> While running your changed tests on Windows, I think I found new failures.

These are among the known set of 7 flaky tests (in vmware only?), e.g. see
http://test.winehq.org/data/f00d44f0f63a66b9157ff7334f6b54c8b079c1ee/98_wtb-...

while on the next day, everything succeeds:
http://test.winehq.org/data/658209b57164da96919500468114a6a7eb0bf7b5/98_wtb-...

Regards,
 Jörg Höhle