Hi,
I’m testing my virtual com port written in UMDF 1.9,
testing with pnpdtest in 7000.0 tools folder is passing fine, but the new pnpdtest run in win logo test support new feature “/skipinstall”, and when using it I get the following error :
Updating debug params
Start: Remove, TUID=(null)
Device using WUDF as a controlling service.
Running Removal Test on node with hwid:
UMDF\vsp
Assert: Test Error: Failed to find the device.
File=d:\5289\base\pnp\tools\pnpd2\user\pnpdtest.cpp, Line=288
Assert: Device node status not ok: problem code 43
File=d:\5289\base\pnp\tools\pnpd2\user\pnpdtest.cpp, Line=288
End: Fail, Remove, TUID=, Repro=Remove the device
I didn’t find any documentation about what skipinstall checks and how to fix it.
any ideas ?
Thanks …
As I understand I need pnpfiltr.sys before I run the test (/skipinstall measn don’t install the pnpfiltr driver)
I have the file, how do I install it ?
OK I found out how to install it. just use /preinstall
I get the following error now:
Assert: Test Error: Could not find any devices with the test filter installed.
while still without /skipinstall everything works fine.
Hi Igal, I don’t know why my previous replies didn’t get delievered. This isssue is known and will be fixed. Till then you can use the below workaround;
Add DWORD values UpperDriverOK=1 and KernelModeClientPolicy=1 to the device’s hardware key:
HKLM\system\CurrentControlSet\Enum\USB (or bus)<hardwareid>*\Device Parameters\WUDF
Thanks!
Neslihan
> -----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@microsoft.com
Sent: Friday, June 19, 2009 11:32 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] UMDF: Not passing pnpdtest
Hi Igal, I don’t know why my previous replies didn’t get
delievered. This isssue is known and will be fixed. Till then
you can use the below workaround;
Add DWORD values UpperDriverOK=1 and KernelModeClientPolicy=1
to the device’s hardware key:
HKLM\system\CurrentControlSet\Enum\USB (or
bus)<hardwareid>*\Device Parameters\WUDF
Both? I was under impression KernelModeClientPolicy replaces
UpperDriverOK (encountered this problem WLKing UMDF driver).
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
Both not needed. Either one should be fine.
“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of
>> xxxxx@microsoft.com
>> Sent: Friday, June 19, 2009 11:32 PM
>> To: Windows System Software Devs Interest List
>> Subject: RE:[ntdev] UMDF: Not passing pnpdtest
>>
>> Hi Igal, I don’t know why my previous replies didn’t get
>> delievered. This isssue is known and will be fixed. Till then
>> you can use the below workaround;
>>
>> Add DWORD values UpperDriverOK=1 and KernelModeClientPolicy=1
>> to the device’s hardware key:
>> HKLM\system\CurrentControlSet\Enum\USB (or
>> bus)<hardwareid>*\Device Parameters\WUDF
>
> Both? I was under impression KernelModeClientPolicy replaces
> UpperDriverOK (encountered this problem WLKing UMDF driver).
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>
I don’t think so. UpperDriverOK alone stopped working for us with the
WLK 1.4 release and we had to use KernelModeClientPolicy. So the only
question is if UpperDriverOK can be omitted. I’m not quite sure if we
finally used both or KernelModeClientPolicy only.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Abhishek R
Sent: Monday, June 22, 2009 6:05 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] UMDF: Not passing pnpdtest
Both not needed. Either one should be fine.
“Michal Vodicka” wrote in message
> news:xxxxx@ntdev…
> >> -----Original Message-----
> >> From: xxxxx@lists.osr.com
> >> [mailto:xxxxx@lists.osr.com] On Behalf Of
> >> xxxxx@microsoft.com
> >> Sent: Friday, June 19, 2009 11:32 PM
> >> To: Windows System Software Devs Interest List
> >> Subject: RE:[ntdev] UMDF: Not passing pnpdtest
> >>
> >> Hi Igal, I don’t know why my previous replies didn’t get
> >> delievered. This isssue is known and will be fixed. Till then
> >> you can use the below workaround;
> >>
> >> Add DWORD values UpperDriverOK=1 and KernelModeClientPolicy=1
> >> to the device’s hardware key:
> >> HKLM\system\CurrentControlSet\Enum\USB (or
> >> bus)<hardwareid>*\Device Parameters\WUDF
> >
> > Both? I was under impression KernelModeClientPolicy replaces
> > UpperDriverOK (encountered this problem WLKing UMDF driver).
> >
> > Best regards,
> >
> > Michal Vodicka
> > UPEK, Inc.
> > [xxxxx@upek.com, http://www.upek.com]
> >
> >
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>
We (UMDF team at MS) tried this out on some UMDF sample drivers from the
WDK. We were able to get UpperDriverOK alone to work.
So the only
question is if UpperDriverOK can be omitted. I’m not quite sure if we
finally used both or KernelModeClientPolicy only.
With UMDF 1.9, you should be fine either way. With UMDF 1.7, you do need
UpperDriverOK.
Also, I just want to clarify that this is just a workaround for a bug in
PnpDTest. Once it is fixed, you shouldn’t need to set any of these registry
values.
“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
> I don’t think so. UpperDriverOK alone stopped working for us with the
> WLK 1.4 release and we had to use KernelModeClientPolicy. So the only
> question is if UpperDriverOK can be omitted. I’m not quite sure if we
> finally used both or KernelModeClientPolicy only.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Abhishek R
>> Sent: Monday, June 22, 2009 6:05 PM
>> To: Windows System Software Devs Interest List
>> Subject: Re:[ntdev] UMDF: Not passing pnpdtest
>>
>> Both not needed. Either one should be fine.
>>
>> “Michal Vodicka” wrote in message
>> news:xxxxx@ntdev…
>> >> -----Original Message-----
>> >> From: xxxxx@lists.osr.com
>> >> [mailto:xxxxx@lists.osr.com] On Behalf Of
>> >> xxxxx@microsoft.com
>> >> Sent: Friday, June 19, 2009 11:32 PM
>> >> To: Windows System Software Devs Interest List
>> >> Subject: RE:[ntdev] UMDF: Not passing pnpdtest
>> >>
>> >> Hi Igal, I don’t know why my previous replies didn’t get
>> >> delievered. This isssue is known and will be fixed. Till then
>> >> you can use the below workaround;
>> >>
>> >> Add DWORD values UpperDriverOK=1 and KernelModeClientPolicy=1
>> >> to the device’s hardware key:
>> >> HKLM\system\CurrentControlSet\Enum\USB (or
>> >> bus)<hardwareid>*\Device Parameters\WUDF
>> >
>> > Both? I was under impression KernelModeClientPolicy replaces
>> > UpperDriverOK (encountered this problem WLKing UMDF driver).
>> >
>> > Best regards,
>> >
>> > Michal Vodicka
>> > UPEK, Inc.
>> > [xxxxx@upek.com, http://www.upek.com]
>> >
>> >
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online
>> at http://www.osronline.com/page.cfm?name=ListServer
>>
>
> -----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Abhishek R
Sent: Wednesday, June 24, 2009 9:06 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] UMDF: Not passing pnpdtest
We (UMDF team at MS) tried this out on some UMDF sample
drivers from the
WDK. We were able to get UpperDriverOK alone to work.
It worked for us with all pre-release 1.4 WLKs. With UMDF 1.9 at Win7.
With 1.4 release it stopped work as we had to open support case and got
KernelModeClientPolicy from another member of your team 
Which solved
the problem.
Maybe you should use your work address instead of yahoo.com 
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]