Sound driver autodetection
chrismorgan at rcn.com
chrismorgan at rcn.com
Tue Jan 7 16:19:23 CST 2003
So the external tool would try to load each driver and put the detected one into the appropriate location in the registry?
Chris
>
> From: Eric Pouech <eric.pouech at wanadoo.fr>
> Date: 2003/01/07 Tue PM 05:09:02 EST
> To: cmorgan at alum.wpi.edu
> CC: wine-devel at winehq.com
> Subject: Re: Sound driver autodetection
>
> chrismorgan at rcn.com wrote:
> > I've been thinking about implementing sound driver autodetection in wine. On startup wine would try to open a device with each of the drivers until one was opened successfully. This seems pretty simple to implement, I was wondering if there was a dynamic way of detecting the list of drivers to try or whether this list would have to be hardcoded in a c file. Eric, any hints?
>
> I don't think this belongs to wine. What we could need is:
> 1/ an external tool that lists all available drivers
> 2/ then creates the corrects initialization of the registry. this would
> also include defining the default driver
> 3/ then all MM DLLs would get their configuration from the registry
>
> of course, 1/ will get complicated with different wine drivers outputing
> to the same physical device, but we could infer some of the rules here
> 1 & 2 could be implemented as a control panel (for better user
> performance), but also as a pure command line tool so that it can be
> invoked at wine initialisation (at least for 2/)
>
> as a matter of fact, I already have 3/ implemented, but never committed
> it because of the lack of 1&2
>
> A+
> --
> Eric Pouech
>
>
>
More information about the wine-devel
mailing list