Prev: Bypass 16-point touch calibration
Next: USB device emulator
From: Ken Spikowski on 20 Apr 2010 21:03
If a USB-to-serial CDC ACM specification device using usbser.sys is not
classified as a modem, the New Hardware Wizard will not install the Virtual
COM Port unless the INF file AddService directive Flags parameter has a value
of 2 to set the SPSVCINST_ASSOCSERVICE bit. This causes both ChkInf and the
DTM "INFTest for a single .INF" to fail with error "(E.22.1302) Filter
drivers cannot be the controlling service (SPSVCINST_ASSOCSERVICE)." To
certifiy the driver for a device that otherwise passes WINQUAL testing but is
less complicated than a modem, is there any other way besides misclassifying
it as a modem or writing a custom driver?
From: Chris on 21 Apr 2010 09:54
I'm not sure I understand. If you're a USB modem, you're a lower
filter to Modem.sys and so the flag should be "2" as you say. If
you're a "COM port", you're simply a function driver for the entire
stack, so the flag should be "0".

On Apr 20, 8:03 pm, Ken Spikowski
<KenSpikow...(a)discussions.microsoft.com> wrote:

> If a USB-to-serial CDC ACM specification device using usbser.sys is not
> classified as a modem, the New Hardware Wizard will not install the Virtual
> COM Port unless the INF file AddService directive Flags parameter has a value
> of 2 to set the SPSVCINST_ASSOCSERVICE bit. This causes both ChkInf and the
> DTM "INFTest for a single .INF" to fail with error "(E.22.1302) Filter
> drivers cannot be the controlling service (SPSVCINST_ASSOCSERVICE)." To
> certifiy the driver for a device that otherwise passes WINQUAL testing but is
> less complicated than a modem, is there any other way besides misclassifying
> it as a modem or writing a custom driver?

 | 
Pages: 1
Prev: Bypass 16-point touch calibration
Next: USB device emulator