DirectKS will allow direct access to drivers under XP. It is roughly equivalent to exclusive mode in Vista, though considerably more understanding is required to use it effectively. http://www.microsoft.com/whdc/device/audio/DirectKS.mspx http://download.microsoft.com/download/1/8/f/18f8cee2-0b64-41f2-893d-a6f2295 b40c8/DW04022_WINHEC2004.ppt http://www.hydrogenaudio.org/forums/lofiversion/index.php/t8635.html Good luck, David Roach Optimal Sound www.optimalsound.net -----Original Message----- From: FreeLists Mailing List Manager [mailto:ecartis@xxxxxxxxxxxxx] Sent: Thursday, November 22, 2007 1:43 AM To: wdmaudiodev digest users Subject: wdmaudiodev Digest V4 #204 wdmaudiodev Digest Wed, 21 Nov 2007 Volume: 04 Issue: 204 In This Issue: [wdmaudiodev] driver/app binding ---------------------------------------------------------------------- From: "Larry Menasco" <menasco@xxxxxxxxxxxxxx> Subject: [wdmaudiodev] driver/app binding Date: Wed, 21 Nov 2007 00:43:21 -0800 Hey All, I spent a half a day looking for some knowledgeable people familiar with audio drivers, and I must say I think my looking has paid off! Here's my question: Does anyone know of a way to "bind" a particular audio device to a particular app in such a way that no other app can have access to that particular audio device while the first app is active? And oh yes, I need to be able to do it on an XP os. I'm aware that the Vista Core Audio API has an exclusive-mode for audio streaming that does essentially what I'd like to do, but my particular app. needs to work with an XP based program, so I need to stick with XP (for the moment). The particular audio device happens to be a USB audio device (micronas based) that when plugged in brings up a generic composite driver, to which I am able to use waveIn and waveOut. Is there any way, other than writing a dedicated driver for the usb audio devices (and at some point I plan to be using two USBs at a time) to prevent other apps from having access? I know if I don't elect it as the default, then the other apps (unless specifically pointed to the device) will leave it alone, but I would prefer not even having that as a possibility. And if it can't be done without a driver, then at least you've saved me the time of finding that out on my own, and I'll then be back for help writing a driver. Thanks! Larry Menasco ------------------------------ End of wdmaudiodev Digest V4 #204 ********************************* ****************** 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/