Perry, Chris wrote: > Tim, > > I'm not sure I agree with you on this one. Doesn't the answer depend on > the way the vendor implemented their custom commands? > > For instance I have implemented a control point in USB firmware to accept > custom commands and an interrupt endpoint to send back custom events and > all I have to do from the Windows side is open the USB device and issue > read and write commands. > The key phrase in your reply is "open the USB device". You must have a custom driver that you control, so that you could add ioctls to issue the read and write commands. KS said that he is using stock Microsoft drivers. The stock drivers do not expose any general purpose "vendor command" ioctls. -- 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/