* where is it written on a Microsoft document that the Device Manager
provides obsolete driver installation procedure
Here you go:
https://technet.microsoft.com/en-us/library/ee851685.aspx
The Windows 7 driver store includes a small collection of drivers for legacy
devices, mostly older printers, modems, scanners, infrared ports, PCMCIA
controllers, and other oddball devices that don’t use Plug and Play
connections. As you might suspect, Windows will not automatically set up such
devices, and you’re rolling the dice if you find one of these old but still
worthwhile devices and try to install an old driver.
SysVad is not a legacy device in this sense.
Also, in Device Manager itself, when you click “add legacy hardware”, the first
page of the wizard says “This wizard helps you install driver software to
support older devices that do not support Plug-and-Play and which are not
automatically recognized by Windows. You should only use this wizard if you are
an advanced user or you have been directed here by technical support”
* You have surely read 2 messages from me
OK, so you’re citing yourself<https://www.smbc-comics.com/comic/2011-08-07>;
fair enough. Please read my responses to those email messages you sent and
reply on those threads if appropriate.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Tuesday, July 24, 2018 10:46:25 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Yes, citation please !
where is it written on a Microsoft document that the Device Manager provides
obsolete driver installation procedure ?
On my side, you have surely read 2 messages from me on this list:
One to say that SYSVAD WASAPI Exclusive playback mode does not work.
One to say that SYSVAD driver was not passing all HLK Certification test.
(first problem explaining why it cannot be successful for example on
KSPosition Test and Audio Logo Test – Glitch)
So I ask again:
How are we expected to produce a certifiable audio driver if the Microsoft
example cannot be certified ?
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 24 juillet 2018 17:04
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
“Add Legacy Hardware” isn’t the right way to install anything anymore, really,
but we have to leave it in because there’s probably something out there that
still uses it, and we don’t want to break it, whatever it is.
Ø the fact that this SYSVAD driver has not been neither validated nor certified
Citation please.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Tuesday, July 24, 2018 6:54:48 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
I used the main workfow given by Windows O/S,
Why it should not be the right way ?
Next time I will use
c:\tools\devcon install sysvad.inf *ROOT\sysvad_TabletAudioSample
but I don’t think it will change something about the fact that this SYSVAD
driver has not been neither validated nor certified.
VB
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 24 juillet 2018 15:26
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
“Add Legacy Hardware” is not the correct way to install Sysvad – see the readme.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Monday, July 23, 2018 11:34:04 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
I have simply used the windows procedure: Device Manager -> Add Legacy Hardware
So, If I resume :
No one validated the SYSVAD Driver (we saw in previous message that it is
"inefficient by design").
No one installed the SYSVAD driver yet.
No one tested the Certification process on it.
Don’t understand…
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Tim Roberts
Envoyé : mardi 24 juillet 2018 03:07
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Vincent Burel (VB-Audio) wrote:
Installation note: Windows Hardware Installation procedure proposes 2 Audio
Tablet Drivers with 2 different versions.
Even if selecting latest version, Windows installs 2x audio tablet drivers (one
is set as non working driver and must be de-installed).
How did you install it? If you used "devcon install", then on Windows 10 you
do get two devices. They changed the non-PnP device installation process in
Windows 10 so that the installation process itself creates a fake device, and
the "devcon" tool creates another one. "pnputil" now seems to be the proper
tool.
--
Tim Roberts, timr@xxxxxxxxx<mailto:timr@xxxxxxxxx>
Providenza & Boekelheide, Inc.
