Trouble creating .sld from network driver .inf

  • Thread starter Thread starter Matt Ervin
  • Start date Start date
M

Matt Ervin

All,

I'm attempting to create a Component Designer .sld file from a network
adaptor's .inf file. Everything works except that I'm getting the following
two warnings from econvert.exe:

Warning:[SLYukCopGig.ndi]: cannot handle key "Characteristics".
Warning:[SLYukCopGig.ndi]: cannot handle key "BusType".

These keys reside in an install section that looks like this:

[SLYukCopGig.ndi]
DelReg = yk51x86.delreg
AddReg = yk51x86.reg, .
Characteristics = 0x84
BusType = 5
CopyFiles = yk51x86.CopyFiles

I looked in MSDN under "MSDN Library\Windows Development\Driver Development
Kit\Network Devices and Protocols\Design Guide\Installing and Upgrading
Network Components\Installing Network Components\Creating Network INF
Files\DDInstall Section" and discovered that these keys are necessary for
this type of driver, but I don't know how to complete the component created
by econvert.exe. Does anyone know what to do?

I looked at the registry of my test machine to see what the driver
installation did and it appears that it created REG_DWORD keys for
Characteristics and REG_SZ keys for BusType, but it's not clear to me how to
determine where in the registry these keys should be located from the .inf
file.

Thanks in advance,

Matt
 
Hi Sean,

The NIC is a Marvell Yukon chipset (88E8053) based device integrated into an
Itox G7L630-B motherboard. You can download the driver from
http://u1gaming.com/xpe/Marvell88E8053Driver.rar.

I'm fairly new to creating XPe components from driver inf files and Windows
device drivers in general so I'm not sure if I can omit the Characteristics
and BusType properties. I don't know how this will affect the driver
behavior. MSDN led me to believe that they are necessary for proper driver
operation.

Matt

Sean Liming (eMVP) said:
For the most part you can ignore these warnings. Whos network card is it?
Can you post it?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.


Matt Ervin said:
All,

I'm attempting to create a Component Designer .sld file from a network
adaptor's .inf file. Everything works except that I'm getting the
following two warnings from econvert.exe:

Warning:[SLYukCopGig.ndi]: cannot handle key "Characteristics".
Warning:[SLYukCopGig.ndi]: cannot handle key "BusType".

These keys reside in an install section that looks like this:

[SLYukCopGig.ndi]
DelReg = yk51x86.delreg
AddReg = yk51x86.reg, .
Characteristics = 0x84
BusType = 5
CopyFiles = yk51x86.CopyFiles

I looked in MSDN under "MSDN Library\Windows Development\Driver
Development Kit\Network Devices and Protocols\Design Guide\Installing and
Upgrading Network Components\Installing Network Components\Creating
Network INF Files\DDInstall Section" and discovered that these keys are
necessary for this type of driver, but I don't know how to complete the
component created by econvert.exe. Does anyone know what to do?

I looked at the registry of my test machine to see what the driver
installation did and it appears that it created REG_DWORD keys for
Characteristics and REG_SZ keys for BusType, but it's not clear to me how
to determine where in the registry these keys should be located from the
.inf file.

Thanks in advance,

Matt
Click to expand...
Click to expand...
 
Matt,

I don't know what a RAR file is, but I found a version from the Marvell
website. The INF file imports with a number of caution on Bus Type, etc.
like you mentions, but these can be ignored since FBA will file out this
information when it installs the driver.

The INF file has a number of PnP IDs since the driver supports a number of
cards. As a result the final import brings in quite a few components. The
components can be narrowed down a bit with the PnP ID found in the PMQ file
or the PMQ import log file.

I was able to create an SLD, but it is too big to post.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.

Matt Ervin said:
Hi Sean,

The NIC is a Marvell Yukon chipset (88E8053) based device integrated into
an
Itox G7L630-B motherboard. You can download the driver from
http://u1gaming.com/xpe/Marvell88E8053Driver.rar.

I'm fairly new to creating XPe components from driver inf files and
Windows
device drivers in general so I'm not sure if I can omit the
Characteristics
and BusType properties. I don't know how this will affect the driver
behavior. MSDN led me to believe that they are necessary for proper
driver
operation.

Matt

Sean Liming (eMVP) said:
For the most part you can ignore these warnings. Whos network card is it?
Can you post it?

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit.


Matt Ervin said:
All,

I'm attempting to create a Component Designer .sld file from a network
adaptor's .inf file. Everything works except that I'm getting the
following two warnings from econvert.exe:

Warning:[SLYukCopGig.ndi]: cannot handle key "Characteristics".
Warning:[SLYukCopGig.ndi]: cannot handle key "BusType".

These keys reside in an install section that looks like this:

[SLYukCopGig.ndi]
DelReg = yk51x86.delreg
AddReg = yk51x86.reg, .
Characteristics = 0x84
BusType = 5
CopyFiles = yk51x86.CopyFiles

I looked in MSDN under "MSDN Library\Windows Development\Driver
Development Kit\Network Devices and Protocols\Design Guide\Installing
and
Upgrading Network Components\Installing Network Components\Creating
Network INF Files\DDInstall Section" and discovered that these keys are
necessary for this type of driver, but I don't know how to complete the
component created by econvert.exe. Does anyone know what to do?

I looked at the registry of my test machine to see what the driver
installation did and it appears that it created REG_DWORD keys for
Characteristics and REG_SZ keys for BusType, but it's not clear to me
how
to determine where in the registry these keys should be located from the
.inf file.

Thanks in advance,

Matt
Click to expand...
Click to expand...
Click to expand...
 
Back
Top