Installing my driver on another machine

NTDEV
1

While working on an ethernet driver I have reached a strange situation in which I can not install my driver on new machines with windows server 2003 sp2.

I have already installed my driver using the same code on another machines, but on this two new machines it just fails with error 87 (the parameter is incorrect). Setup API.log also doesn’t give much help.
I don’t see DriverEntery being called in this process.

Is my driver being used in this process or is this just the INF that shuld be checked?
I was able to install on another machines using the same INF

Here is the end of the setupapi.log file.

#I060 Set selected driver.
#-019 Searching for hardware ID(s): pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_15b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s): pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci\cc_0c06
#-019 Searching for hardware ID(s): pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_15b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s): pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci\cc_0c06
#-019 Searching for hardware ID(s): pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_15b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s): pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci\cc_0c06
#-019 Searching for hardware ID(s): pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_15b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s): pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci\cc_0c06
#I022 Found “PCI\VEN_15B3&DEV_6368” in q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf; Device: “Mellanox ConnectX 10Gb Ethernet Adapter”; Driver: “Mellanox ConnectX 10Gb Ethernet Adapter”; Provider: “Mellanox”; Mfg: “Mellanox”; Section name: “ConnectX.ndi”.
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001.
#I023 Actual install section: [ConnectX.ndi.NT]. Rank: 0x0000a001. Driver date: 05/05/2007. Version: 0.1.0.0.
#-124 Doing copy-only install of “PCI\VEN_15B3&DEV_6368&SUBSYS_636815B3&REV_A0\4&335208C7&0&0050”.
#W366 An unsigned, incorrectly signed, or Authenticode™ signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf” for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be installed (Policy=Warn, user said ok). Error 0xe000022f: The third-party INF does not contain digital signature information.
#W187 Install failed, attempting to restore original files.
#W362 An unsigned, incorrectly signed, or Authenticode™ signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf” for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be installed (Policy=Warn). Error 0xe000022f: The third-party INF does not contain digital signature information.
#-024 Copying file “q:\projeth\trunk\driver\5.1\kernel\objchk_wnet_x86\i386\ConnectX.sys” to “K:\WINDOWS\system32\DRIVERS\ConnectX.sys”.
#W362 An unsigned, incorrectly signed, or Authenticode™ signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf” for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be installed (Policy=Warn). Error 0xe000022f: The third-party INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ConnectX.ndi.NT.Interfaces] from “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#E161 Processing of call to class installer failed. Error 87: The parameter is incorrect.

thanks
Tzachi

2

Another thought that I have is this: Can the failure in install be
related to the hw I’m using.
That is, assuming that my driver entry is not being called, is it
possible that windows (pci.sys?)
is talking directly with my hardware ?

Thanks
Tzachi

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@mellanox.co.il
Sent: Monday, June 04, 2007 8:55 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Installing my driver on another machine

While working on an ethernet driver I have reached a strange
situation in which I can not install my driver on new
machines with windows server 2003 sp2.

I have already installed my driver using the same code on
another machines, but on this two new machines it just fails
with error 87 (the parameter is incorrect). Setup API.log
also doesn’t give much help.
I don’t see DriverEntery being called in this process.

Is my driver being used in this process or is this just the
INF that shuld be checked?
I was able to install on another machines using the same INF

Here is the end of the setupapi.log file.

#I060 Set selected driver.
#-019 Searching for hardware ID(s):
pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s):
pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
#-019 Searching for hardware ID(s):
pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s):
pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
#-019 Searching for hardware ID(s):
pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s):
pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
#-019 Searching for hardware ID(s):
pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
#-018 Searching for compatible ID(s):
pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
#I022 Found “PCI\VEN_15B3&DEV_6368” in
q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf; Device:
“Mellanox ConnectX 10Gb Ethernet Adapter”; Driver: “Mellanox
ConnectX 10Gb Ethernet Adapter”; Provider: “Mellanox”; Mfg:
“Mellanox”; Section name: “ConnectX.ndi”.
#I087 Driver node not trusted, rank changed from 0x00002001
to 0x0000a001.
#I023 Actual install section: [ConnectX.ndi.NT]. Rank:
0x0000a001. Driver date: 05/05/2007. Version: 0.1.0.0.
#-124 Doing copy-only install of
“PCI\VEN_15B3&DEV_6368&SUBSYS_636815B3&REV_A0\4&335208C7&0&0050”.
#W366 An unsigned, incorrectly signed, or Authenticode™
signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be
installed (Policy=Warn, user said ok). Error 0xe000022f: The
third-party INF does not contain digital signature information.
#W187 Install failed, attempting to restore original files.
#W362 An unsigned, incorrectly signed, or Authenticode™
signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be
installed (Policy=Warn). Error 0xe000022f: The third-party
INF does not contain digital signature information.
#-024 Copying file
“q:\projeth\trunk\driver\5.1\kernel\objchk_wnet_x86\i386\Conne
ctX.sys” to “K:\WINDOWS\system32\DRIVERS\ConnectX.sys”.
#W362 An unsigned, incorrectly signed, or Authenticode™
signed file “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will be
installed (Policy=Warn). Error 0xe000022f: The third-party
INF does not contain digital signature information.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ConnectX.ndi.NT.Interfaces] from
“q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”.
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#E161 Processing of call to class installer failed. Error 87:
The parameter is incorrect.

thanks
Tzachi

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer

3

Tzachi Dar wrote:

Another thought that I have is this: Can the failure in install be
related to the hw I’m using.
That is, assuming that my driver entry is not being called, is it
possible that windows (pci.sys?)
is talking directly with my hardware ?

Your driver entry is not being called because your driver is not being
loaded, because the installation failed, because the “class
co-installer” returned an error.

Perhaps you should post your INF file. My gut suspicion is that the
problem lies there.

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

4

Thanks for your help, but I have tried using the inf file that comes
with the Intel sample (with minimum changes) and there is still no
change.

I have looked at the winmsd and found that there is a memory conflict
for my device on the machines that I can not install, and I wander if
that can be the problem (on the machines were the installation succeeds
I don’t have such a problem). I’m not able to change this conflicts
through the device manager that shows “no conflict” for the device that
is in conflict.

I wander if that can be the problem.

Thanks again.
Tzachi

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Tuesday, June 05, 2007 12:23 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Installing my driver on another machine

Tzachi Dar wrote:
> Another thought that I have is this: Can the failure in install be
> related to the hw I’m using.
> That is, assuming that my driver entry is not being called, is it
> possible that windows (pci.sys?) is talking directly with
my hardware
> ?
>

Your driver entry is not being called because your driver is
not being loaded, because the installation failed, because
the “class co-installer” returned an error.

Perhaps you should post your INF file. My gut suspicion is
that the problem lies there.

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

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer

5

Can someone from ms tell me what Assert(FIsValidNetClass (Class)) means?
File d:\nt\net\config\netcfg\engine\compdefs.h, line 71:

It seems from the assembly that the code expects to get the value 5
while the value I have is 6. this is probably where my problem starts.

Some more info:
I have attached windbg to the device manager and got an access violation
in netcfgx.dll. So I have replaced that file with the debug version and
got the assert that what was mentioned above.

I have tried to make this dll print some more and have found that I have
to create a file called netcfg.ini.
In this file I have something like this:

; The debug flags section enables or disables
; individual debug flags that control various things
; like the debug output format.
;
; Set to a non-zero value (e.g. “1”) to enable an
; individual debug flag, otherwise set to zero to
; disable it.
[DebugFlags]

From this text I didn’t quite understand if there is some key that will
make it print more data.
(from the assembly it seems that not, but …)

Thanks again
Tzachi

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tzachi Dar
Sent: Tuesday, June 05, 2007 12:05 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Installing my driver on another machine

Another thought that I have is this: Can the failure in
install be related to the hw I’m using.
That is, assuming that my driver entry is not being called,
is it possible that windows (pci.sys?) is talking directly
with my hardware ?

Thanks
Tzachi

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@mellanox.co.il
> Sent: Monday, June 04, 2007 8:55 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Installing my driver on another machine
>
> While working on an ethernet driver I have reached a
strange situation
> in which I can not install my driver on new machines with windows
> server 2003 sp2.
>
> I have already installed my driver using the same code on another
> machines, but on this two new machines it just fails with error 87
> (the parameter is incorrect). Setup API.log also doesn’t give much
> help.
> I don’t see DriverEntery being called in this process.
>
> Is my driver being used in this process or is this just the
INF that
> shuld be checked?
> I was able to install on another machines using the same INF
>
> Here is the end of the setupapi.log file.
>
> #I060 Set selected driver.
> #-019 Searching for hardware ID(s):
> pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
> 6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
> #-018 Searching for compatible ID(s):
> pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
> #-019 Searching for hardware ID(s):
> pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
> 6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
> #-018 Searching for compatible ID(s):
> pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
> #-019 Searching for hardware ID(s):
> pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
> 6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
> #-018 Searching for compatible ID(s):
> pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
> #-019 Searching for hardware ID(s):
> pci\ven_15b3&dev_6368&subsys_636815b3&rev_a0,pci\ven_15b3&dev_
> 6368&subsys_636815b3,pci\ven_15b3&dev_6368&cc_0c0600,pci\ven_1
5b3&dev_6368&cc_0c06
> #-018 Searching for compatible ID(s):
> pci\ven_15b3&dev_6368&rev_a0,pci\ven_15b3&dev_6368,pci\ven_15b
3&cc_0c0600,pci\ven_15b3&cc_0c06,pci\ven_15b3,pci\cc_0c0600,pci>
\cc_0c06
> #I022 Found “PCI\VEN_15B3&DEV_6368” in
> q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf; Device:
> “Mellanox ConnectX 10Gb Ethernet Adapter”; Driver:
“Mellanox ConnectX
> 10Gb Ethernet Adapter”; Provider: “Mellanox”; Mfg:
> “Mellanox”; Section name: “ConnectX.ndi”.
> #I087 Driver node not trusted, rank changed from 0x00002001 to
> 0x0000a001.
> #I023 Actual install section: [ConnectX.ndi.NT]. Rank:
> 0x0000a001. Driver date: 05/05/2007. Version: 0.1.0.0.
> #-124 Doing copy-only install of
> “PCI\VEN_15B3&DEV_6368&SUBSYS_636815B3&REV_A0\4&335208C7&0&0050”.
> #W366 An unsigned, incorrectly signed, or Authenticode™
signed file
> “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
> for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will
be installed
> (Policy=Warn, user said ok). Error 0xe000022f: The third-party INF
> does not contain digital signature information.
> #W187 Install failed, attempting to restore original files.
> #W362 An unsigned, incorrectly signed, or Authenticode™
signed file
> “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
> for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will
be installed
> (Policy=Warn). Error 0xe000022f: The third-party INF does
not contain
> digital signature information.
> #-024 Copying file
> “q:\projeth\trunk\driver\5.1\kernel\objchk_wnet_x86\i386\Conne
ctX.sys” to “K:\WINDOWS\system32\DRIVERS\ConnectX.sys”.
> #W362 An unsigned, incorrectly signed, or Authenticode™
signed file
> “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”
> for driver “Mellanox ConnectX 10Gb Ethernet Adapter” will
be installed
> (Policy=Warn). Error 0xe000022f: The third-party INF does
not contain
> digital signature information.
> #-166 Device install function: DIF_REGISTER_COINSTALLERS.
> #I056 Coinstallers registered.
> #-166 Device install function: DIF_INSTALLINTERFACES.
> #-011 Installing section [ConnectX.ndi.NT.Interfaces] from
> “q:\projeth\trunk\driver\5.1\kernel\mtnic51.inf”.
> #I054 Interfaces installed.
> #-166 Device install function: DIF_INSTALLDEVICE.
> #E161 Processing of call to class installer failed. Error 87:
> The parameter is incorrect.
>
> thanks
> Tzachi
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer