winmm/midi tests and VMware

Julius Schwartzenberg julius.schwartzenberg at gmail.com
Tue Mar 2 06:33:05 CST 2010


Paul Vriens 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.

I think some versions of the drivers come with with the required 
wavesets for the software synthesizer, while with others you had to get 
it from the original CD. You should make sure this ecw file is also 
present I guess. There seems to be some more information here: 
http://en.wikipedia.org/wiki/Ensoniq_AudioPCI

If it turns out it's hard to get hold of these wavesets, I'll try to put 
them online.

Julius



More information about the wine-devel mailing list