Me & sound driver stuff

[Andrew "Silver Blade" Greenwood]

I've been taking a break from working on sound support under ReactOS
recently, for various reasons.

Mainly, I'm waiting for Steven Edwards to port winmm.dll from WINE over.
Once this is ported, I can implement a couple of stub drivers for audio and
MIDI, and then flesh out my Sound Blaster drivers. I'm still unsure if I
should incorporate both audio and MIDI handling into a single driver or not,
since I read something about IRQs for Sound Blaster cards and it confused me
(MIDI uses IRQ 2 while audio uses IRQ 5, usually, but the MS driver does
some weird stuff with the interrupt handler...)

Another reason is just because I've been having personal issues I've had to
deal with recently, so I haven't been getting as much done as I normally
would, and I've got other things I need to be doing.

But eventually I hope to get sound working under ReactOS, even if it is just
a command-line program to play WAV and MID files!

-Andrew

[Steven Edwards]

--- "Andrew "Silver Blade" Greenwood" [e-mail]
wrote:
> Mainly, I'm waiting for Steven Edwards to port winmm.dll from WINE
> over. 
> Once this is ported, I can implement a couple of stub drivers for
> audio and
> MIDI, and then flesh out my Sound Blaster drivers. I'm still unsure
> if I
> should incorporate both audio and MIDI handling into a single driver
> or not,
> since I read something about IRQs for Sound Blaster cards and it
> confused me
> (MIDI uses IRQ 2 while audio uses IRQ 5, usually, but the MS driver
> does
> some weird stuff with the interrupt handler...)

Its going to take quite a while to get WINEs Winmm building cleanly
with the w32api headers at the rate I am going. I can go ahead and make
builds of Winmm using the WINE headers avalible to you or I can help
you setup a Mingw+MSYS enviroment that will let you build the dll
yourself.

Thanks
Steven

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com