[wdmaudiodev] Re: Developing a "simple" user mode installable MIDI driver.
- From: Tim Roberts <timr@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Wed, 13 Jun 2018 10:16:04 -0700
Chris Hubbard wrote:
My driver now seems to working quite nicely, but I have noticed the
following:
Whenever any MIDI based application starts, calls are made to
DriverProc for "load", "enable" and "open".
However, no calls ever seem to be made to DriverProc for "close",
"disable" or "unload".
In other words, once started, the driver stays there until the next
reboot.
Well, not exactly. Your "driver" is an ordinary DLL that gets loaded
into the application's process space. When the application terminates,
your DLL will cease to exist. I'm surprised you don't see "close" and
"unload" calls, but since the whole installable driver subsystem is no
longer supported, there's nowhere to complain.
--
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/
Other related posts:
