Trouble importing Intel .inf file

[Doug Gordon]

Our OEM switched us from the Intel Pro/100 S Ethernet card that I had
working under XPE to a Pro/100 M. Seems like a simple change, but my first
warning was when I brought up XP Pro and it could not find a driver. I
downloaded the basic drivers from Intel, put them on a floppy, and the XP
Pro New Hardware wizard found the .inf file and installed the drivers. The
interface works fine now on the target h/w under XP Pro.

I reran TAP on the target and imported the .pmq into Component Designer and
verified that CD also tells me that it can't find a driver in the XPE SP1
database. OK, I'll make my own. I imported the same .inf file that I had
used on XP Pro into CD and it eventually issued the following warning and
did not create any components:

"Warning:D:\xpe\component\pro100m\files\e100b325.inf: [Intel] is missing."

This sounds like a missing section from the .inf. I don't know much about
.inf files, but looking at the file in a text editor I noted the following
lines:

[Manufacturer]
%V_INTEL% = Intel, NTx86

and later the section:

[Intel.NTx86]
; DisplayName Section DeviceID
; ----------- ------- --------
; ich
%PCIE100EMBLON.DeviceDesc% = XP_D110K.ndi, PCI\VEN_8086&DEV_2449

and a long list of other devices. XP Pro had no trouble with this, but it
looks like the importer is looking for a section named "[Intel]" instead of
"[Intel.NTx86]".

Does anyone know how this works? Should I try editing some lines in this
file to see if I can get it to import?

Doug Gordon

[Andy Allred [MS]]

Yeah, there is bug in the inf importer where it will not interpret an
obscure condition of some infs though it works with setup api. so this is
not an issue with the inf but rather our tool

notice in the manufacturer section it lists this:
"Intel, NTx86"

see the comma in that string above?

Now go down to your device section, note that it says:
"[Intel.NTx86]"

no comma, it's been replaced with a decimal, so the inf importer process
doesn't see a matching reference. this is very rare and affects very very
few infs that i've seen compared to the 9,000+ drivers in the database.

to fix this you can either do a custom import in CD to parse the section
called "intel.ntx86" so it will see the section anyways, or as a last resort
modify the inf so that the manufacturer sections doesn't have a comma but a
decimal instead so the inf importer will find the correct section later on.

Andy

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

"Doug Gordon" <gord...@nospamfrc.com> wrote in message
news:#tb$8R$EDHA...@TK2MSFTNGP12.phx.gbl...

[Doug Gordon]

I figured as much :-). Anyway, replacing the comma with a period breaks a
bunch of other stuff in the file and I had to cancel the import to stop the
error messages in the log. The custom section import would be nice, but I am
sure that I need multiple sections from the file and this is a huge file
with dozens of sections. What I'd like is for it to parse the entire file
automatically *plus* that specific [intel.ntx86] section.

I'm really stuck unless I can get past this roadblock. Any other ideas?

Doug Gordon

"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message
news:OhwIda$EDHA...@TK2MSFTNGP10.phx.gbl...

[Andy Allred [MS]]

are you sure the warnings you're seeing aren't expected, like runonce reg
keys that will not be added, etc...?

if you're sure you're stuck, which I know may seem a little frustrating if
you don't know how to interpret infs, then attach the inf to the thread and
i'll take a look at it tonight, but the custom process works. if the inf has
many components in it, simply identify the one you need by correlating the
vendev id of your HW to the section of the inf and simply process that one.

also, if there are multiple references to the string with the comma you need
to do a bulk replace on them all.
--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

"Doug Gordon" <gord...@nospamfrc.com> wrote in message

news:u87LYs$EDHA...@TK2MSFTNGP11.phx.gbl...

[Andy Allred [MS]]

Oh, and btw, if you're referring to some of the networking keys like 'bus
type' and 'characteristics', then this is probably expected and can be
ignored, i believe the class installer takes care of that during fba. i've
seen some of those same warnings when componentizing some other intel new
net inf for the 82xxx or something similar to that, the net driver worked
fine.

--

This posting is provided "AS IS" with no warranties, and confers no rights.
==========================================================

"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message

news:OX7DR3$EDHA...@TK2MSFTNGP11.phx.gbl...

[Doug Gordon]

I think I got it working by editing the keywords and removing the ntx86
stuff altogether. I got a bunch of warnings, but they were all the same and
I probably would have gotten them anyway. There were lines in the inf file
such as:

Characteristics = 0x84
BusType = 5

That were generating warnings:

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

There were just so many that I thought the whole process was blowing chunks.
Anyway, I got what looks like a good component defined and imported. Thanks
for the help and the offer to look at the file!

Doug Gordon

"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message

news:OX7DR3$EDHA...@TK2MSFTNGP11.phx.gbl...

[Doug Gordon]

The driver files that I downloaded from Intel are a "unified driver" for all
their cards, so it is a huge INF file that basically defines every network
card that Intel has ever made or ever will :-). When I imported the INF, it
created a SLD with about 3 dozen components -- one for each card. I then
went in and deleted all the components except the Pro/100M Desktop card that
I was trying to support. The XPE build is now working and I am all set!

Doug Gordon

"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message

news:Ou7$UBAFDH...@TK2MSFTNGP11.phx.gbl...