winmm/midi tests and VMware

Lei Zhang thestig at google.com
Tue Mar 2 12:03:23 CST 2010


On Tue, Mar 2, 2010 at 3:07 AM, Paul Vriens <paul.vriens.wine at gmail.com> wrote:
> On 03/02/2010 11:47 AM, Julius Schwartzenberg wrote:
>>
>> Hi Paul,
>>
>> Paul Vriens wrote:
>>>
>>> There are 2 ways (I can see) to fix this issue:
>>>
>>> 1. Get rid of (or disable) the sound device on the failing boxes. This
>>> means of course far less coverage of tests.
>>> 2. There is an option in the Audio control panel to only use the
>>> default devices. This doesn't prevent the 'enumeration' from listing
>>> the failing device but we could have the tests skip 'non default'
>>> devices. The attached patch is a first attempt and does work on my XP
>>> box.
>>
>> A third option could be to try a different driver. The hardware VMware
>> emulates. SB PCI128, doesn't have any MIDI capabilities as far as I
>> know. The original Windows driver contained a software sequencer to
>> support MIDI. (Different from the one Windows started to include later
>> itself.)
>>
>> Maybe using a different driver from the Creative site could let things
>> work better.
>
> I already tried a few, any suggestions?. I'm stuck with drivers for either
> that PCI128 (also tried the Ensoniq driver). The strange thing is that is
> works fine on some OS's but fails on others (my XP fails for example, but
> W2K3 succeeds) with what appears to be the same driver.

VMware can also emulate a Soundblaster 16. Does that have the MIDI
capabilities needed? You need to change sound.virtualDev = "es1371" to
sound.virtualdev = "sb16" in the .vmx file.



More information about the wine-devel mailing list