[wdmaudiodev] Re: I need to use my driver instead of wdmaud.drv
- From: Larry Osterman <Larry.Osterman@xxxxxxxxxxxxx>
- To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Mon, 21 Sep 2009 20:51:10 +0000
The information I've seen says that we continue to support the old driver model
for MIDI software synths. In addition, we support as much of the old wave
interfaces as are needed to support unimodem drivers.
It may be possible for Igor to get his solution working on Windows XP but he's
going to face significantly more challenges moving forward for Windows Vista
and beyond.
I've said this before on wdmaudiodev and I'll reiterate it here: IMHO driver
developers shouldn't spend a significant amount of time engineering solutions
that are known to have forward compatibility issues. Instead I'd concentrate
my development resources towards solutions that will work and be supported on
both Windows XP AND Windows Vista/7.
As far as I can see, Windows XP's market share is only going to decrease as
time moves forward. By designing a solution that works only on XP, you may be
painting yourself in a corner.
Larry Osterman
This posting is provided "AS IS" with no warranties, and confers no rights
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Roberts
Sent: Monday, September 21, 2009 12:38 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: I need to use my driver instead of wdmaud.drv
Larry Osterman wrote:
> You're going to have some challenges replacing wdmaud.drv. You're trying to
> use what I call the NT4 driver model which has been deprecated for non-MIDI
> audio drivers since sometime around 1998 (with the advent of the WDM driver
> model). In particular, starting with Windows Vista the hooks for the mixer
> driver aren't supported at all (and the wave hooks are only supported because
> the TAPI component in Windows depends on it for certain classes of telephony
> applications).
>
It's interesting to hear you say that. One of my clients (who does TAPI
stuff) was told by a PSS representative that all support for the
installable driver model had been dropped as of Windows Server 2008.
They had me write a drop-in replacement for winmm.dll (at least the
waveIn and waveOut portions), which turned out to demonstrate how
trivial that layer is.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
Other related posts:
