From: 0dbell on
I need to create a device driver that is not really tied to hardware
but rather to a input/output buffers provided by an external
application.

I was hoping to implement it using UMDF, but according to sample
sources in C:\WinDDK\6000\src\audio it seems that my only recourse is
to use WDM.

So, my questions are:

1. Is my understanding correct? Is it true that an audio driver cannot
be implemented using UMDF, even if there really isn't any hardware
involved? (my goal is to support only XP/Vista)

2. Can I still use KMDF (relatively easier than WDM) to write a driver
that is based on the samples in C:\WinDDK\6000\src\audio\msvad? Or do
I have to stick to WDM if I want to simplify my life by basing my
device driver on on of the samples in C:\WinDDK\6000\src\audio\msvad?

Many thanks in advance,
Don

From: 0dbell on
OK - I think that I found the correct answers by myself:

On Mar 19, 12:10 pm, 0db...(a)gmail.com wrote:
> I need to create a device driver that is not really tied to hardware
> but rather to a input/output buffers provided by an external
> application.
>
> I was hoping to implement it using UMDF, but according to sample
> sources in C:\WinDDK\6000\src\audio it seems that my only recourse is
> to use WDM.
>
> So, my questions are:
>
> 1. Is my understanding correct? Is it true that an audio driver cannot
> be implemented using UMDF, even if there really isn't any hardware
> involved? (my goal is to support only XP/Vista)
>

Yes. UMDF is not available for audio devices.

> 2. Can I still use KMDF (relatively easier than WDM) to write a driver
> that is based on the samples in C:\WinDDK\6000\src\audio\msvad? Or do
> I have to stick to WDM if I want to simplify my life by basing my
> device driver on on of the samples in C:\WinDDK\6000\src\audio\msvad?

No - the samples in the msvad section are WDM only. As of now, there
are no known audio samples that are implemented using KMDF.




From: Tim Roberts on
0dbell(a)gmail.com wrote:
>
>I need to create a device driver that is not really tied to hardware
>but rather to a input/output buffers provided by an external
>application.
>
>I was hoping to implement it using UMDF, but according to sample
>sources in C:\WinDDK\6000\src\audio it seems that my only recourse is
>to use WDM.

Right. Audio drivers adhere to other driver models (port class, stream
class, AVStream) with their own wrappers and handlers. They can't be
written in UMDF or KMDF.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Mark Heath on
I take it this means I can't write a MIDI serial port driver in UMDF?

thanks
Mark

"Tim Roberts" wrote:

> 0dbell(a)gmail.com wrote:
> >
> >I need to create a device driver that is not really tied to hardware
> >but rather to a input/output buffers provided by an external
> >application.
> >
> >I was hoping to implement it using UMDF, but according to sample
> >sources in C:\WinDDK\6000\src\audio it seems that my only recourse is
> >to use WDM.
>
> Right. Audio drivers adhere to other driver models (port class, stream
> class, AVStream) with their own wrappers and handlers. They can't be
> written in UMDF or KMDF.
> --
> Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.
>
From: Doron Holan [MS] on
if you need to link against avstream or some other class driver, UMDF is
currently out of hte picture.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Mark Heath" <MarkHeath(a)discussions.microsoft.com> wrote in message
news:3FBD347A-758F-4E39-8A9C-DBD733B525E3(a)microsoft.com...
>I take it this means I can't write a MIDI serial port driver in UMDF?
>
> thanks
> Mark
>
> "Tim Roberts" wrote:
>
>> 0dbell(a)gmail.com wrote:
>> >
>> >I need to create a device driver that is not really tied to hardware
>> >but rather to a input/output buffers provided by an external
>> >application.
>> >
>> >I was hoping to implement it using UMDF, but according to sample
>> >sources in C:\WinDDK\6000\src\audio it seems that my only recourse is
>> >to use WDM.
>>
>> Right. Audio drivers adhere to other driver models (port class, stream
>> class, AVStream) with their own wrappers and handlers. They can't be
>> written in UMDF or KMDF.
>> --
>> Tim Roberts, timr(a)probo.com
>> Providenza & Boekelheide, Inc.
>>