[wdmaudiodev] Re: How to sign up with MS with the Win10 driver no charge "attestment" option

  • From: Matthew van Eerde <Matthew.van.Eerde@xxxxxxxxxxxxx>
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Tue, 27 Oct 2015 00:47:21 +0000

Yup.

-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Titchener
Sent: Monday, October 26, 2015 5:37 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: How to sign up with MS with the Win10 driver no
charge "attestment" option

Matthew, we are a true virtual device so you approach looks intriguing.

Is the only modification required to our .inf is to add the correctly edited
lines below?

[DeviceInstall32]
AddDevice = ROOT\OurDevice\0000,,OurDevice_RootDevice_Inst

[OurDevice_RootDevice_Inst]
HardwareIds = ROOT\OurDevice

Thanks,

Paul Titchener


For a really-and-truly virtual driver, the best approach is to use a
[DeviceInstall32] section. This will tell Windows to create a fake virtual
audio "physical device object" with the hardware ID you specify. For an
example, see SysVad:

https://github.com/Microsoft/Windows-driver-samples/blob/master/audio/sysvad/tabletaudiosample.inf

[DeviceInstall32]
AddDevice =
ROOT\sysvad_TabletAudioSample\0000,,sysvad_TabletAudioSample_RootDevice_Inst

[sysvad_TabletAudioSample_RootDevice_Inst]
HardwareIds = ROOT\sysvad_TabletAudioSample


Then you can deploy the driver using "pnputil -a foo.inf" - the act of
importing the driver into the driver store will trigger the [DeviceInstall32]
section, and everything else happens automagically.

(For a driver that actually hooks up to physical hardware, DO NOT USE a
[DeviceInstall32] section. Instead, hook up to the physical device object
exposed by the bus driver.)

-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Titchener
Sent: Monday, October 26, 2015 5:15 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: How to sign up with MS with the Win10 driver no
charge "attestment" option

Tim, I tried out dspinst but it appears that since we are using a virtual
driver that it may not work for us.

When I run dspinst with our driver files it brings up the signing page and then
appears to complete the installation but our driver never appears in the Device
Manager so it appears it has installed the files but is then waiting for an
actual hardware device to appear.

We started with the devcon code as MS used that method in their MSVAD virtual
driver example.

Do you know if there is a way with dspinst (or some additional steps) to force
our device to appear after dspinst has installed it?

Thanks,

Paul Titchener


Well, I use "dpinst", which is a small tool from the WDK that pre-installs
whatever driver packages it finds in the directory where it lives. You use an
XML file to configure its activities. My NSIS installer copies my driver
package and DPInst.exe to the destination system, then runs DPInst.

DPInst uses the difxapi APIs to do the pre-installation, so you could create
your own version.

--
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/

X3&#0;P2

EZu ޲Ǭ> - ,j j)m fj b ׯ~ +- J r zf 0vf v*z ު笵 zX + ˛ -˛ m '
r zf 0vf v*z ު笵 zX + ˛ - 칻 & 2 ^ h f 0vf v*z u ڶ ~ +- Q `
@ 81  i 0 fj b ׯr

******************

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: