Reinstall_With_IO_Before_And_After failed in hck testing

Mahesh_bera · April 3, 2014, 5:13am

Hi ,

I am doing testing for the pci driver in whql process. i have installed the driver and hardware in the client machine disabling the driver signature enforcement. i have got some successful results for pci compliance test for single device and pci root port surprise remove test. but when i am trying to run Reinstall_With_IO_Before_And_After the error is coming like " WDTF_DRIVER_SETUP_DEVICE : DriverSetupDevice::Install() call class installer HRESULT=0x800F0228 - There are no compatible drivers for this device". anyone got this kind of error ? … please help me out to crack this.
and in the parameter box in HCK studio i am getting Wpa2PskAeSsid, kittestssid, Wpa2PskPassword. what are these things?

thanks in advance.

Tim_Roberts · April 3, 2014, 12:37pm

xxxxx@gmail.com wrote:

I am doing testing for the pci driver in whql process. i have installed the driver and hardware in the client machine disabling the driver signature enforcement.

Exactly how did you install the driver? Did you pre-install the package
into the driver store? I’m guessing you didn’t. Just copying the files
into \Windows\System32 and \Windows\INF is not good enough. The
“Reinstall_With_IO_Before_And_After” test uninstalls your driver, then
does a scan-for-new-hardware to make sure the driver can be
automatically installed. Your driver failed that re-install, suggesting
that the driver package could not be found.

and in the parameter box in HCK studio i am getting Wpa2PskAeSsid, kittestssid, Wpa2PskPassword. what are these things?

What kind of device are you testing? Is it a wireless network adapter?
Those are all wireless network parameters.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Mahesh_bera · April 4, 2014, 1:29am

I am just installed by using “disabling the driver signature enforcement”
by pressing F8 at restarting time. now i will try to install it by doing
test signing . and my device is pci device. so based on your reply i don’t
need to run the tests which are not related to pci device. am i correct? if
so can you suggest me what are the tests i need to run for a pci
device(certification tests)?
Thanks…

On Thu, Apr 3, 2014 at 10:08 PM, Tim Roberts wrote:

> xxxxx@gmail.com wrote:
> > I am doing testing for the pci driver in whql process. i have installed
> the driver and hardware in the client machine disabling the driver
> signature enforcement.
>
> Exactly how did you install the driver? Did you pre-install the package
> into the driver store? I’m guessing you didn’t. Just copying the files
> into \Windows\System32 and \Windows\INF is not good enough. The
> “Reinstall_With_IO_Before_And_After” test uninstalls your driver, then
> does a scan-for-new-hardware to make sure the driver can be
> automatically installed. Your driver failed that re-install, suggesting
> that the driver package could not be found.
>
>
> > and in the parameter box in HCK studio i am getting Wpa2PskAeSsid,
> kittestssid, Wpa2PskPassword. what are these things?
>
> What kind of device are you testing? Is it a wireless network adapter?
> Those are all wireless network parameters.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>

Tim_Roberts · April 4, 2014, 2:15pm

bera mahi wrote:

I am just installed by using “disabling the driver signature
enforcement” by pressing F8 at restarting time.

That’s not what I asked at all. HOW did you install it? How did you
get the files into place? Did you create a package with an INF, SYS and
CAT file? Did you use the Device Manager “update driver” button? Did
you use DPInst? Did you force the files into Windows\System32 and
Windows\INF?

Also remember that the HCK process reboots the machine many times, and
pressing F8 only suppresses the KMCS check once.

now i will try to install it by doing test signing . and my device is
pci device. so based on your reply i don’t need to run the tests which
are not related to pci device. am i correct? if so can you suggest me
what are the tests i need to run for a pci device(certification tests)?

You need to run all of the tests for whatever device class you intend to
claim when you submit. If you are a network device, then you have to
run all of the network tests. If you are a video capture device, then
you have to run all of the video capture tests. If you do not fall into
any of the pre-defined classes, then you choose “unclassified”, and it
will only run the PCI tests and the generic driver tests.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Mahesh_bera · April 9, 2014, 3:35am

Ok Tim, here i am putting the installation process i followed

before installing i have test signed the driver as per kmcs walkthrogh

Steps for loading the driver

Open "Device Manager"
Right Click on "Nitrox Device"
Select "Update Driver"
Select "Browse my computer for driver software"
Select "Let me pick from a list of device drivers on my computer"
Select "Have a disk"
Browse to
"C:\windows_driver\driver\x64\Win8Debug\Package\nitrox1-64.inf" and click
OK
Select "Nitrox3/PX SSL/CRYPTO/IPSEC Acc Version:1.0.0.1"
Select "Next".
This will install the driver.

i found that this will automatically copies the .sys file from the driver
package into the windows/system32/drivers. i am failed in almost 13 test
cases and every case test failed at the DeviceStatusCheck step(each test
has other sub tests init, but unable to run them because of
DevicestatusCheck failure). giving the error messages like

Error 4/8/2014 7:56:36.833 AM WDTF_TEST : Found a device that has a
non-zero problem code or is phantom. Logging device info

Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DeviceID:
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020

Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DisplayName: Network and
Computing Encryption/Decryption ControllerError 4/8/2014 7:56:36.833
AM WDTF_TEST
: Status: Status Flags=0x1802400 (DN_HAS_PROBLEM DN_DISABLEABLE
DN_NT_ENUMERATOR DN_NT_DRIVER) Problem Code=1c
(CM_PROB_FAILED_INSTALL)Error 4/8/2014
7:56:36.833 AM WDTF_TEST : IsPhantom: False

for almost every case related to pnp tests are giving the same error..
and what i found is after running all the tests if i look at into the
client machine device manager the device is uninstalled with an yellow
symbol. i think after rebooting the device it is not automatically
installing drievr.. am i correct?
yes, we have a package for the driver contains .sys files, inf files,
.cat file, supporting files.

Thanks.
Mahesh

On Fri, Apr 4, 2014 at 11:45 PM, Tim Roberts wrote:

> bera mahi wrote:
> > I am just installed by using "disabling the driver signature
> > enforcement" by pressing F8 at restarting time.
>
> That's not what I asked at all. HOW did you install it? How did you
> get the files into place? Did you create a package with an INF, SYS and
> CAT file? Did you use the Device Manager "update driver" button? Did
> you use DPInst? Did you force the files into Windows\System32 and
> Windows\INF?
>
> Also remember that the HCK process reboots the machine many times, and
> pressing F8 only suppresses the KMCS check once.
>
>
> > now i will try to install it by doing test signing . and my device is
> > pci device. so based on your reply i don't need to run the tests which
> > are not related to pci device. am i correct? if so can you suggest me
> > what are the tests i need to run for a pci device(certification tests)?
>
> You need to run all of the tests for whatever device class you intend to
> claim when you submit. If you are a network device, then you have to
> run all of the network tests. If you are a video capture device, then
> you have to run all of the video capture tests. If you do not fall into
> any of the pre-defined classes, then you choose "unclassified", and it
> will only run the PCI tests and the generic driver tests.
>
> --
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> ---
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See Careers – OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> OSR Seminars – OSR
>
> To unsubscribe, visit the List Server section of OSR Online at
> ListServer/Forum
>

Mark_Roddy · April 9, 2014, 7:11am

Use Dpinst to install the driver package into the driver store.

Mark Roddy

On Wed, Apr 9, 2014 at 3:36 AM, bera mahi wrote:

> Ok Tim, here i am putting the installation process i followed
>
> before installing i have test signed the driver as per kmcs walkthrogh
>
> Steps for loading the driver
> ============================
> - Open “Device Manager”
> - Right Click on “Nitrox Device”
> - Select “Update Driver”
> - Select “Browse my computer for driver software”
> - Select “Let me pick from a list of device drivers on my computer”
> - Select “Have a disk”
> - Browse to
> “C:\windows_driver\driver\x64\Win8Debug\Package\nitrox1-64.inf” and click
> OK
> - Select “Nitrox3/PX SSL/CRYPTO/IPSEC Acc Version:1.0.0.1”
> - Select “Next”.
> - This will install the driver.
>
> i found that this will automatically copies the .sys file from the driver
> package into the windows/system32/drivers. i am failed in almost 13 test
> cases and every case test failed at the DeviceStatusCheck step(each test
> has other sub tests init, but unable to run them because of
> DevicestatusCheck failure). giving the error messages like
>
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : Found a device that has a
> non-zero problem code or is phantom. Logging device info
>
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DeviceID:
> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020
>
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DisplayName: Network and
> Computing Encryption/Decryption ControllerError 4/8/2014 7:56:36.833 AM WDTF_TEST
> : Status: Status Flags=0x1802400 (DN_HAS_PROBLEM DN_DISABLEABLE
> DN_NT_ENUMERATOR DN_NT_DRIVER) Problem Code=1c (CM_PROB_FAILED_INSTALL)
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : IsPhantom: False
>
>
> 1) for almost every case related to pnp tests are giving the same error…
> and what i found is after running all the tests if i look at into the
> client machine device manager the device is uninstalled with an yellow
> symbol. i think after rebooting the device it is not automatically
> installing drievr… am i correct?
> 2) yes, we have a package for the driver contains .sys files, inf files,
> .cat file, supporting files.
>
> Thanks.
> Mahesh
>
>
> On Fri, Apr 4, 2014 at 11:45 PM, Tim Roberts wrote:
>
>> bera mahi wrote:
>> > I am just installed by using “disabling the driver signature
>> > enforcement” by pressing F8 at restarting time.
>>
>> That’s not what I asked at all. HOW did you install it? How did you
>> get the files into place? Did you create a package with an INF, SYS and
>> CAT file? Did you use the Device Manager “update driver” button? Did
>> you use DPInst? Did you force the files into Windows\System32 and
>> Windows\INF?
>>
>> Also remember that the HCK process reboots the machine many times, and
>> pressing F8 only suppresses the KMCS check once.
>>
>>
>> > now i will try to install it by doing test signing . and my device is
>> > pci device. so based on your reply i don’t need to run the tests which
>> > are not related to pci device. am i correct? if so can you suggest me
>> > what are the tests i need to run for a pci device(certification tests)?
>>
>> You need to run all of the tests for whatever device class you intend to
>> claim when you submit. If you are a network device, then you have to
>> run all of the network tests. If you are a video capture device, then
>> you have to run all of the video capture tests. If you do not fall into
>> any of the pre-defined classes, then you choose “unclassified”, and it
>> will only run the PCI tests and the generic driver tests.
>>
>> –
>> Tim Roberts, xxxxx@probo.com
>> Providenza & Boekelheide, Inc.
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>>
>> OSR is HIRING!! See http://www.osr.com/careers
>>
>> 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
>>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers 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
>

Tim_Roberts · April 9, 2014, 12:37pm

bera mahi wrote:

before installing i have test signed the driver as per kmcs walkthrogh

How did you do that? I can see that you’re using the Win 8 WDK, and the
Win 8 WDK will test-sign your package for you automatically. The
“Package” directory should contain a test-signed package with a CAT
file. You shouldn’t have to do anything more.

Did you turn on “test signing” in your HCK client machine?

Steps for loading the driver

Open “Device Manager”

Right Click on “Nitrox Device”

Select “Update Driver”

Select “Browse my computer for driver software”

Select “Let me pick from a list of device drivers on my computer”

Select “Have a disk”

Browse to
“C:\windows_driver\driver\x64\Win8Debug\Package\nitrox1-64.inf” and
click OK

Select “Nitrox3/PX SSL/CRYPTO/IPSEC Acc Version:1.0.0.1”

Select “Next”.

This will install the driver.

i found that this will automatically copies the .sys file from the
driver package into the windows/system32/drivers.

That’s not the important part. The important thing is whether you got
pre-installed in the driver store. See if your driver package is
present somewhere in \Windows\System32\DriverStore. The whole package
should be there – CAT, INF, and SYS.

i am failed in almost 13 test cases and every case test failed at the
DeviceStatusCheck step(each test has other sub tests init, but unable
to run them because of DevicestatusCheck failure). giving the error
messages like

Error 4/8/2014 7:56:36.833 AM WDTF_TEST : Found a device that has a
non-zero problem code or is phantom. Logging device info

Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DeviceID:
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020

You should go look in \Windows\Inf\Setup.Dev.Log to see what it says
about the installation failure.

for almost every case related to pnp tests are giving the same
error… and what i found is after running all the tests if i look at
into the client machine device manager the device is uninstalled with
an yellow symbol. i think after rebooting the device it is not
automatically installing drievr… am i correct?

It looks like that’s what is happening. It’s your responsibility to
make sure that works, which is why they test it.

yes, we have a package for the driver contains .sys files, inf
files, .cat file, supporting files.

What supporting files? The pre-install is only going to copy the files
mentioned in the CAT, and the CAT is only going to cover files mentioned
in the INF. If your driver is depending on other files, then you need
to refer to them in the INF.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Mahesh_bera · April 10, 2014, 6:27am

How did you do that? I can see that you’re using the Win 8 WDK, and the
Win 8 WDK will test-sign your package for you automatically. The “Package”
directory should contain a test-signed package with a CAT file. You
shouldn’t have to do anything more.

Did you turn on “test signing” in your HCK client machine?

yes. i turn on the test signing mode and i can see Test Mode on the desktop.
as you said i am using wdk 8 , i knew that test signing can be done. but we
have got the unsigned catalog files so we have manually generated a
certificate for test signing and signed with the catalog file with this
certificate.

That’s not the important part. The important thing is whether you got
pre-installed in the driver store. See if your driver package is present
somewhere in \Windows\System32\DriverStore. The whole package should be
there – CAT, INF, and SYS.

well, i have checked in the path
C:\Windows\System32\DriverStore\FileRepository\
there all files are there in a folder nitrox1-64.inf_amd64_8a298fa2a3ad0e7f.
so every file is copied to this folder. the files are .inf, .sys, .cat,
.out files which are microcode files (supporting files).

You should go look in \Windows\Inf\Setup.Dev.Log to see what it says
about the installation failure.

yes, i have seen this file and found the below things

[DIF_SELECTBESTCOMPATDRV -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]

>> Section start 2014/04/03 11:30:56.625
dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
dvi: No CoInstallers found
dvi: Default installer: Enter 11:30:56.625
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<< Section end 2014/04/03 11:30:56.641
<<< [Exit status: FAILURE(0xe0000228)]

What supporting files? The pre-install is only going to copy the files
mentioned in the CAT, and the CAT is only going to cover files mentioned in
the INF. If your driver is depending on other files, then you need to
refer to them in the INF.

supporting files are microcode output files and they are clearly addressed
in the inf file. no problem with them as they are getting copied into
the C:\Windows\System32\DriverStore\FileRepository
with the inf instructions.

now ,
a) i am in a confusion difference between manual installation which i
followed and DPinstall?
b) if u follow the DP package creation steps after forming, the package
will be containing the same files that i have in a folder right now. but if
u follow the DPinst method we need to have the class installer and co
installer entries in the inf file. exactly the same errors i have
found(above mentioned). why its happening aven i am not using the DPinst
method? should i use the DPinst thing to install the package ? if so how
can i convert my current package into DPinstallable package(i have searched
but it’s bit confusing)?

Thanks Tim in advance…

On Wed, Apr 9, 2014 at 10:08 PM, Tim Roberts wrote:

> bera mahi wrote:
>
>
> before installing i have test signed the driver as per kmcs walkthrogh
>
>
> How did you do that? I can see that you’re using the Win 8 WDK, and the
> Win 8 WDK will test-sign your package for you automatically. The “Package”
> directory should contain a test-signed package with a CAT file. You
> shouldn’t have to do anything more.
>
> Did you turn on “test signing” in your HCK client machine?
>
>
>
> Steps for loading the driver
> ============================
> - Open “Device Manager”
> - Right Click on “Nitrox Device”
> - Select “Update Driver”
> - Select “Browse my computer for driver software”
> - Select “Let me pick from a list of device drivers on my computer”
> - Select “Have a disk”
> - Browse to
> “C:\windows_driver\driver\x64\Win8Debug\Package\nitrox1-64.inf” and click
> OK
> - Select “Nitrox3/PX SSL/CRYPTO/IPSEC Acc Version:1.0.0.1”
> - Select “Next”.
> - This will install the driver.
>
> i found that this will automatically copies the .sys file from the
> driver package into the windows/system32/drivers.
>
>
> That’s not the important part. The important thing is whether you got
> pre-installed in the driver store. See if your driver package is present
> somewhere in \Windows\System32\DriverStore. The whole package should be
> there – CAT, INF, and SYS.
>
>
>
> i am failed in almost 13 test cases and every case test failed at the
> DeviceStatusCheck step(each test has other sub tests init, but unable to
> run them because of DevicestatusCheck failure). giving the error messages
> like
>
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : Found a device that has a
> non-zero problem code or is phantom. Logging device info
>
> Error 4/8/2014 7:56:36.833 AM WDTF_TEST : DeviceID:
> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020
>
>
> You should go look in \Windows\Inf\Setup.Dev.Log to see what it says about
> the installation failure.
>
>
>
> 1) for almost every case related to pnp tests are giving the same
> error… and what i found is after running all the tests if i look at into
> the client machine device manager the device is uninstalled with an yellow
> symbol. i think after rebooting the device it is not automatically
> installing drievr… am i correct?
>
>
> It looks like that’s what is happening. It’s your responsibility to make
> sure that works, which is why they test it.
>
>
>
> 2) yes, we have a package for the driver contains .sys files, inf
> files, .cat file, supporting files.
>
>
> What supporting files? The pre-install is only going to copy the files
> mentioned in the CAT, and the CAT is only going to cover files mentioned in
> the INF. If your driver is depending on other files, then you need to
> refer to them in the INF.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>

Tim_Roberts · April 10, 2014, 12:19pm

bera mahi wrote:

well, i have checked in the
path C:\Windows\System32\DriverStore\FileRepository\ there all files
are there in a folder nitrox1-64.inf_amd64_8a298fa2a3ad0e7f. so every
file is copied to this folder. the files are .inf, .sys, .cat, .out
files which are microcode files (supporting files).

That’s good.

You should go look in \Windows\Inf\Setup.Dev.Log to see what it
says about the installation failure.

yes, i have seen this file and found the below things

[DIF_SELECTBESTCOMPATDRV -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>>> Section start 2014/04/03 11:30:56.625
dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
dvi: No CoInstallers found
dvi: Default installer: Enter 11:30:56.625
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this
device.
<<< Section end 2014/04/03 11:30:56.641
<<< [Exit status: FAILURE(0xe0000228)]

That’s curious. I don’t see how it could have found a class name if it
didn’t find the driver package. If you want to send me your driver
package by private email, I will look over the INF and the CAT and see
if there is anything unusual.

I notice you said you have microcode. This isn’t one of those devices
that changes its device ID after microcode is loaded, is it?

a) i am in a confusion difference between manual installation which i
followed and DPinstall?
b) if u follow the DP package creation steps after forming, the
package will be containing the same files that i have in a folder
right now. but if u follow the DPinst method we need to have the class
installer and co installer entries in the inf file.

No, only if your driver needs a class installer and/or a co-installer.
You’ll note that those are not marked as errors in the log – it’s just
information.

Your statement is correct – as far as I can tel, it looks like you got
the files in the right places, so DPInst is not going to change
anything. There is something else going on.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Mahesh_bera · April 11, 2014, 2:14am

ohh… i made a mistake in sending the error message…

[DIF_SELECTBESTCOMPATDRV -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]

>> Section start 2014/04/03 11:30:56.625
dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
dvi: No CoInstallers found
dvi: Default installer: Enter 11:30:56.625
dvi: {Select Best Driver}
! dvi: Selecting driver failed(0xe0000228)
dvi: {Select Best Driver - exit(0xe0000228)}
! dvi: Default installer: failed!
! dvi: Error 0xe0000228: There are no compatible drivers for this device.
<<< Section end 2014/04/03 11:30:56.641
<<< [Exit status: FAILURE(0xe0000228)]

we have got this on 3rd april i.e by making" disabling driver signature
enforcement"… i am so sorry Tim.

this is what is i have got on 8th april by doing test signing. the message
is

[DIF_PROPERTYCHANGE -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]

>> Section start 2014/04/08 18:42:23.538
cmd:
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
/ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
/role=TestExecution
/wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
/wexcommunication_protocol=ncalrpc
/wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
/stackframecount=50
dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
dvi: No CoInstallers found
dvi: Default installer: Enter 18:42:23.538
dvi: {Change State}
dvi: Device Instance =
‘PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020’.
dvi: {DICS_DISABLE, DICS_FLAG_CONFIGSPECIFIC}
dvi: {Change State}
dvi: Device Instance =
‘PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020’.
dvi: {Change State exit (0x00000000)}
dvi: {Change State - exit}
dvi: Default installer: Exit
<<< Section end 2014/04/08 18:42:23.710
<<< [Exit status: SUCCESS]

>> [DIF_PROPERTYCHANGE -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>> Section start 2014/04/08 18:42:23.710
cmd:
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
/ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
/role=TestExecution
/wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
/wexcommunication_protocol=ncalrpc
/wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
/stackframecount=50
dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
dvi: Default installer: Enter 18:42:23.726
dvi: {Change State}
dvi: Device Instance =
‘PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020’.
dvi: {DICS_ENABLE, DICS_FLAG_CONFIGSPECIFIC}
dvi: {Change State}
dvi: Device Instance =
‘PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020’.
dvi: {Change State exit (0x00000000)}
dvi: {Change State - exit}
dvi: Default installer: Exit
<<< Section end 2014/04/08 18:42:53.571
<<< [Exit status: SUCCESS]

Well, i am consulting my boss for sending the .cat and sys, inf files to
you.

sorry for the mistake and thanks a lot…

On Thu, Apr 10, 2014 at 9:50 PM, Tim Roberts wrote:

> bera mahi wrote:
>
>
> well, i have checked in the path C:\Windows\System32\DriverStore\FileRepository<br>> there all files are there in a folder nitrox1-64.inf_amd64_8a298fa2a3ad0e7f.
> so every file is copied to this folder. the files are .inf, .sys, .cat,
> .out files which are microcode files (supporting files).
>
>
> That’s good.
>
>
>
> 3) You should go look in \Windows\Inf\Setup.Dev.Log to see what it says
> about the installation failure.
>
> yes, i have seen this file and found the below things
>
> [DIF_SELECTBESTCOMPATDRV -
> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
> >>> Section start 2014/04/03 11:30:56.625
> dvi: No class installer for ‘Nitrox3/PX SSL/Crypto/IPSec Acc’
> dvi: No CoInstallers found
> dvi: Default installer: Enter 11:30:56.625
> dvi: {Select Best Driver}
> ! dvi: Selecting driver failed(0xe0000228)
> dvi: {Select Best Driver - exit(0xe0000228)}
> ! dvi: Default installer: failed!
> ! dvi: Error 0xe0000228: There are no compatible drivers for this
> device.
> <<< Section end 2014/04/03 11:30:56.641
> <<< [Exit status: FAILURE(0xe0000228)]
>
>
> That’s curious. I don’t see how it could have found a class name if it
> didn’t find the driver package. If you want to send me your driver package
> by private email, I will look over the INF and the CAT and see if there is
> anything unusual.
>
> I notice you said you have microcode. This isn’t one of those devices
> that changes its device ID after microcode is loaded, is it?
>
>
>
> a) i am in a confusion difference between manual installation which i
> followed and DPinstall?
> b) if u follow the DP package creation steps after forming, the package
> will be containing the same files that i have in a folder right now. but if
> u follow the DPinst method we need to have the class installer and co
> installer entries in the inf file.
>
>
> No, only if your driver needs a class installer and/or a co-installer.
> You’ll note that those are not marked as errors in the log – it’s just
> information.
>
> Your statement is correct – as far as I can tel, it looks like you got
> the files in the right places, so DPInst is not going to change anything.
> There is something else going on.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>

Tim_Roberts · April 11, 2014, 1:38pm

bera mahi wrote:

[DIF_PROPERTYCHANGE -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>>> Section start 2014/04/08 18:42:23.538
cmd:
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
/ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
/role=TestExecution
/wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
/wexcommunication_protocol=ncalrpc
/wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
/stackframecount=50
…
<<< Section end 2014/04/08 18:42:23.710
<<< [Exit status: SUCCESS]

>>> [DIF_PROPERTYCHANGE -
PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>>> Section start 2014/04/08 18:42:23.710
cmd:
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
/ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
/role=TestExecution
/wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
/wexcommunication_protocol=ncalrpc
/wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
/stackframecount=50
…
<<< Section end 2014/04/08 18:42:53.571
<<< [Exit status: SUCCESS]

Well, i am consulting my boss for sending the .cat and sys, inf files
to you.

sorry for the mistake and thanks a lot…

There are no errors in these snippets. If you do send the driver
package, be sure to send \windows\inf\setup.api.log and
\windows\inf\setup.dev.log, so I can look at the whole thing.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Mahesh_bera · April 14, 2014, 3:03am

Hi Tim, can you send me your personal email id, so that i can share the
files. and i am not able to find the \windows\inf\setup.dev.log specific
file . i have got \windows\inf\setup.api.log file.
Thanks.

On Fri, Apr 11, 2014 at 11:07 PM, Tim Roberts wrote:

> bera mahi wrote:
>
>
>
> [DIF_PROPERTYCHANGE -
> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
> >>> Section start 2014/04/08 18:42:23.538
> cmd:
> C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
> /ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
> /role=TestExecution
> /wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
> /wexcommunication_protocol=ncalrpc
> /wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
> /stackframecount=50
> …
> <<< Section end 2014/04/08 18:42:23.710
> <<< [Exit status: SUCCESS]
>
>
> >>> [DIF_PROPERTYCHANGE -
> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
> >>> Section start 2014/04/08 18:42:23.710
> cmd:
> C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
> /ThreadingModel=“Sta” /DefaultAppDomain=“false” /DpiAware=“false”
> /role=TestExecution
> /wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
> /wexcommunication_protocol=ncalrpc
> /wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
> /stackframecount=50
> …
> <<< Section end 2014/04/08 18:42:53.571
> <<< [Exit status: SUCCESS]
>
>
> Well, i am consulting my boss for sending the .cat and sys, inf files to
> you.
>
> sorry for the mistake and thanks a lot…
>
>
> There are no errors in these snippets. If you do send the driver package,
> be sure to send \windows\inf\setup.api.log and \windows\inf\setup.dev.log,
> so I can look at the whole thing.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> 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
>

Tim_Roberts · April 14, 2014, 2:57pm

bera mahi wrote:

Hi Tim, can you send me your personal email id, so that i can share
the files. and i am not able to find the \windows\inf\setup.dev.log
specific file . i have got \windows\inf\setup.api.log file.

Well, wait a minute. Neither of those are right. What operating system
are you using for your testing? If it is Vista or later, then you
should find
\windows\inf\setupapi.app.log
\windows\inf\setupapi.dev.log
as well as several others that aren’t so important. If you are running
XP or Server 2003, then it is called
\windows\setupapi.log.

I am somewhat amused by your request for my email address. It is in my
signature, which is in every message I send, and it is even in the very
first line of the message you just sent.

On Fri, Apr 11, 2014 at 11:07 PM, Tim Roberts > mailto:xxxxx> wrote:
>
> bera mahi wrote:
>>
>>
>> [DIF_PROPERTYCHANGE -
>> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>> >>> Section start 2014/04/08 18:42:23.538
>> cmd:
>> C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
>> /ThreadingModel=“Sta” /DefaultAppDomain=“false”
>> /DpiAware=“false” /role=TestExecution
>> /wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
>> /wexcommunication_protocol=ncalrpc
>> /wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
>> /stackframecount=50
>> …
>> <<< Section end 2014/04/08 18:42:23.710
>> <<< [Exit status: SUCCESS]
>>
>>
>> >>> [DIF_PROPERTYCHANGE -
>> PCI\VEN_177D&DEV_0011&SUBSYS_0011177D&REV_00\4&10B7D861&0&0020]
>> >>> Section start 2014/04/08 18:42:23.710
>> cmd:
>> C:\WLK\JobsWorkingDir\Tasks\WTTJobRun1CDF6D0C-2EC8-44EB-B2D7-D399D889C4DC\te.processhost.exe
>> /ThreadingModel=“Sta” /DefaultAppDomain=“false”
>> /DpiAware=“false” /role=TestExecution
>> /wexcommunication_connectionid=86914efc-4dce-4147-ae2e-edd6d60603ae
>> /wexcommunication_protocol=ncalrpc
>> /wexlogger_connectiondata={wexcommunication_connectionid=846b67f4-b689-473f-89a8-7c93ed08ea97,wexcommunication_connecttimeout=60000,wexcommunication_protocol=ncalrpc,wexlogger_parent_thread_id=2012}
>> /stackframecount=50
>> …
>> <<< Section end 2014/04/08 18:42:53.571
>> <<< [Exit status: SUCCESS]
>>
>>
>> Well, i am consulting my boss for sending the .cat and sys, inf
>> files to you.
>>
>> sorry for the mistake and thanks a lot…
>
> There are no errors in these snippets. If you do send the driver
> package, be sure to send \windows\inf\setup.api.log and
> \windows\inf\setup.dev.log, so I can look at the whole thing.
>
> –
> Tim Roberts, xxxxx@probo.com mailto:xxxxx
> Providenza & Boekelheide, Inc.
>

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.</mailto:xxxxx></mailto:xxxxx>

David_R_Cattley · April 14, 2014, 3:00pm

> I am somewhat amused by your request for my email address.

I think the forum interface still effaces e-mail addresses, even in signatures.

[quote] –

Tim Roberts, xxxxx@probo.com

Providenza & Boekelheide, Inc.

[/quote]