"cannot handle key" of BusType or Characteristics, during driver import

J

jimt

I am using the supplied .INF to componentize a Broadcom ethernet driver.
During the Component Designer import the logfile catches multiple
occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:
These two keys are not normally parsed by the inf importer because they
do not represent standard keywords used in PnP INF files. The warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see the
XPe Help says to add a registry key manually. How does one convert these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg keys
during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at
broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go ahead and
try the imported driver with a XPe image next with the hope the above
warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 
K

KM

jimt,

You probably saw this one but just to reiterate:
"Cannot handle key (Characteristics)/(BusType)": These keys are not normally parsed because they do not represent standard
keywords used in plug and play (PnP) INF files. You need to determine if that section of the INF is required in order to make to the
device work. If so, do a custom import of the INF.
Source: http://msdn2.microsoft.com/en-us/embedded/aa731191.aspx

Obviously, you are trying to install a physical adapter on PCIBus that supports a user interface. (Characteristics = 0x84,
BusType=5). Those values are default for PnP manager. Hence, if the same values are used, they can be ignored and left out from the
INF file.
Otherwise you'd need to match/setup the right values in registry. You showed the path in registry yourself.

--
=========
Regards,
KM
I am using the supplied .INF to componentize a Broadcom ethernet driver. During the Component Designer import the logfile catches
multiple occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:
These two keys are not normally parsed by the inf importer because they
do not represent standard keywords used in PnP INF files. The warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see the XPe Help says to add a registry key manually. How does
one convert these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg keys during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go ahead and try the imported driver
with a XPe image next with the hope the above warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 
J

jimt

Hi KM,

Yup, I had seen the msdn note that you quoted; it was part of the "the XPe
Help" that I mentioned. The phrase "determine if that section of the INF is
required" was a little vague to me.

Thanks for mentioning that default PnP were causing the messages. That
should settle the issue. BTW where does one go to read more about default
values for the PnP manager?

I'll go ahead and resume my image build with the imported SLD file, assuming
the defaults are ok. As always, thanks a bunch !

--
jimt

KM said:
jimt,

You probably saw this one but just to reiterate:
"Cannot handle key (Characteristics)/(BusType)": These keys are not
normally parsed because they do not represent standard keywords used in
plug and play (PnP) INF files. You need to determine if that section of
the INF is required in order to make to the device work. If so, do a
custom import of the INF.
Source: http://msdn2.microsoft.com/en-us/embedded/aa731191.aspx

Obviously, you are trying to install a physical adapter on PCIBus that
supports a user interface. (Characteristics = 0x84, BusType=5). Those
values are default for PnP manager. Hence, if the same values are used,
they can be ignored and left out from the INF file.
Otherwise you'd need to match/setup the right values in registry. You
showed the path in registry yourself.

--
=========
Regards,
KM
I am using the supplied .INF to componentize a Broadcom ethernet driver.
During the Component Designer import the logfile catches multiple
occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:
These two keys are not normally parsed by the inf importer because they
do not represent standard keywords used in PnP INF files. The warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see
the XPe Help says to add a registry key manually. How does one convert
these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg keys
during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at
broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go ahead
and try the imported driver with a XPe image next with the hope the above
warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 
K

KM

jimt,
Thanks for mentioning that default PnP were causing the messages. That should settle the issue. BTW where does one go to read
more about default values for the PnP manager?


Good question. I don't have a good anwer though.
MSDN, MS KB, Google - that's pretty much all we have.
I like Device Installation section on MSDN. It gives lots of info to think about:
http://msdn2.microsoft.com/en-us/library/ms791083.aspx

--
=========
Regards,
KM
KM said:
jimt,

You probably saw this one but just to reiterate:
"Cannot handle key (Characteristics)/(BusType)": These keys are not normally parsed because they do not represent standard
keywords used in plug and play (PnP) INF files. You need to determine if that section of the INF is required in order to make to
the device work. If so, do a custom import of the INF.
Source: http://msdn2.microsoft.com/en-us/embedded/aa731191.aspx

Obviously, you are trying to install a physical adapter on PCIBus that supports a user interface. (Characteristics = 0x84,
BusType=5). Those values are default for PnP manager. Hence, if the same values are used, they can be ignored and left out from
the INF file.
Otherwise you'd need to match/setup the right values in registry. You showed the path in registry yourself.

--
=========
Regards,
KM
I am using the supplied .INF to componentize a Broadcom ethernet driver. During the Component Designer import the logfile catches
multiple occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:

These two keys are not normally parsed by the inf importer because they
do not represent standard keywords used in PnP INF files. The warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see the XPe Help says to add a registry key manually. How
does one convert these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg keys during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go ahead and try the imported driver
with a XPe image next with the hope the above warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 
J

jimt

FYI. I'm not sure how I missed this before, but MS has documented these
here:

http://msdn2.microsoft.com/en-us/library/aa937905.aspx

--
jimt


KM said:
jimt,
Thanks for mentioning that default PnP were causing the messages. That
should settle the issue. BTW where does one go to read more about
default values for the PnP manager?


Good question. I don't have a good anwer though.
MSDN, MS KB, Google - that's pretty much all we have.
I like Device Installation section on MSDN. It gives lots of info to think
about: http://msdn2.microsoft.com/en-us/library/ms791083.aspx

--
=========
Regards,
KM
KM said:
jimt,

You probably saw this one but just to reiterate:
"Cannot handle key (Characteristics)/(BusType)": These keys are not
normally parsed because they do not represent standard keywords used in
plug and play (PnP) INF files. You need to determine if that section of
the INF is required in order to make to the device work. If so, do a
custom import of the INF.
Source: http://msdn2.microsoft.com/en-us/embedded/aa731191.aspx

Obviously, you are trying to install a physical adapter on PCIBus that
supports a user interface. (Characteristics = 0x84, BusType=5). Those
values are default for PnP manager. Hence, if the same values are used,
they can be ignored and left out from the INF file.
Otherwise you'd need to match/setup the right values in registry. You
showed the path in registry yourself.

--
=========
Regards,
KM

I am using the supplied .INF to componentize a Broadcom ethernet driver.
During the Component Designer import the logfile catches multiple
occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:

These two keys are not normally parsed by the inf importer because
they
do not represent standard keywords used in PnP INF files. The
warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see
the XPe Help says to add a registry key manually. How does one convert
these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg
keys during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at
broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go
ahead and try the imported driver with a XPe image next with the hope
the above warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 
K

KM

Yup. Nice link.
I always had that info in the local DDK documentation but missed the online link. Thanks!

--
=========
Regards,
KM


jimt said:
FYI. I'm not sure how I missed this before, but MS has documented these here:

http://msdn2.microsoft.com/en-us/library/aa937905.aspx

--
jimt


KM said:
jimt,
Thanks for mentioning that default PnP were causing the messages. That should settle the issue. BTW where does one go to read
more about default values for the PnP manager?


Good question. I don't have a good anwer though.
MSDN, MS KB, Google - that's pretty much all we have.
I like Device Installation section on MSDN. It gives lots of info to think about:
http://msdn2.microsoft.com/en-us/library/ms791083.aspx

--
=========
Regards,
KM
jimt,

You probably saw this one but just to reiterate:
"Cannot handle key (Characteristics)/(BusType)": These keys are not normally parsed because they do not represent standard
keywords used in plug and play (PnP) INF files. You need to determine if that section of the INF is required in order to make
to the device work. If so, do a custom import of the INF.
Source: http://msdn2.microsoft.com/en-us/embedded/aa731191.aspx

Obviously, you are trying to install a physical adapter on PCIBus that supports a user interface. (Characteristics = 0x84,
BusType=5). Those values are default for PnP manager. Hence, if the same values are used, they can be ignored and left out from
the INF file.
Otherwise you'd need to match/setup the right values in registry. You showed the path in registry yourself.

--
=========
Regards,
KM

I am using the supplied .INF to componentize a Broadcom ethernet driver. During the Component Designer import the logfile
catches multiple occurrences errors:

Info:Creating: Broadcom NetLink (TM) Gigabit Ethernet
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "Characteristics".
Warning:[BCM5789.XpInst.NTx86]: cannot handle key "BusType".

I see that Arnie Brackett of MS posted this back on 30Oct02:

These two keys are not normally parsed by the inf importer because they
do not represent standard keywords used in PnP INF files. The warnings
you see are for your reference so you can determine if that section is
required for you to make the devices work.

How do we determine this? And what do we do if it is required? I see the XPe Help says to add a registry key manually. How
does one convert these:

Characteristics = 0x84 ; NCF_HAS_UI | NCF_PHYSICAL
BusType = 5

into registry entries?

This driver works on XP Pro. Inctrl5 shows these 2 new related reg keys during an XP Pro install under
HLM\SYSTEM\ControlSet001\Control\Class\{guidnumber}\0008:
"BusType" = (REG_SZ)5
"Characteristics" = (REG_DWORD) 0x00000084 (decimal 132)

The driver can be found at broadcom.com/support/ethernet_nic/netxtreme_server.php. I will go ahead and try the imported
driver with a XPe image next with the hope the above warnings are ignorable. All this on XPe SP2 w/FP2007.

Thanks, --jimt
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top