Problems with Network Card device driver component

[RussR]

I am fairly new to the world of XPE, so please be patient
with me. I have spent a lot of time going through the
documentation and tips, but have been unable to resolve
this current issue.

I ran TAP.exe on my current machine, but somehow it did
not pick up my network card driver. The card is an Intel
Pro 1000/MT. While this driver is not included with XP
Pro, I do have drivers for it.

So I proceeded to create a component for this device from
the driver files. Here's what I did:
1)Used Component Designer to import .inf files
2)Created a Repository and set source path to driver files
3)Added repository to the component.
4)Added component to the Database.
5)Finally added component to my device configuration in TD

No errors at any step including build, however after FBA
finishes and I load up run time image, in device manager,
the network driver is not installed. I can at this point
manually install it, and that works, but that's besides
the point.

Do you guys have any idea why it is not being
automatically installed during PnP detection?

Thanks

 

[KM]

I haven't personally tried Intel Pro 100/MT card but since it seems to be
working on XP Pro it should work on XPe.
You mentioned "No errors at any step including build". Does it mean you have
checked FBALog.txt ?

Also, since you got it working manually on XPe (and XP Pro?) you may add all
the required registry settings to your custom driver component. That usually
promises that your driver will be working on XPe.

KM

 

[Joe Morris [MS]]

Check the destination path of the file resources for the component you
created. I have seen odd cases where the path of the catalog file name
(*.cat file) is incorrectly set to %66000%. If that's the case set it to the
actual destination path of the resource to match that of where it gets
installed in your XP Pro test machine.

 

[RussR]

Well in both XP Pro and XPe, the driver doesn't install
automatically. I have to point it to the folder where
the drivers are and then it works fine.

I do not understand why in XPe it does that when I've
created a component for it including all the files it
needs. In Component Designer, the file paths all seem to
be correct, including the one for the .cat file.

I must admit, I do not know what specifically to look for
in the FBALog.txt, but I have browsed through it and did
not see anything obvious.

I also do not know what registry keys to add to the
component for the driver as I don't believe the driver
adds any registry keys.

I'm really frustrated and stumped

 

[RussR]

All the files for the component seem to be correctly
pointed to the folder in which they exist. This includes
the .cat file.

Any other suggestion? Do I need to set a certain build
order dependency for a network adapter?

Thanks

-----Original Message-----
Check the destination path of the file resources for the component you
created. I have seen odd cases where the path of the catalog file name
(*.cat file) is incorrectly set to %66000%. If that's the case set it to the
actual destination path of the resource to match that of where it gets
installed in your XP Pro test machine.

--
Joe Morris [MS]

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

I am fairly new to the world of XPE, so please be patient
with me. I have spent a lot of time going through the
documentation and tips, but have been unable to resolve
this current issue.

I ran TAP.exe on my current machine, but somehow it did
not pick up my network card driver. The card is an Intel
Pro 1000/MT. While this driver is not included with XP
Pro, I do have drivers for it.

So I proceeded to create a component for this device from
the driver files. Here's what I did:
1)Used Component Designer to import .inf files
2)Created a Repository and set source path to driver files
3)Added repository to the component.
4)Added component to the Database.
5)Finally added component to my device configuration in TD

No errors at any step including build, however after FBA
finishes and I load up run time image, in device manager,
the network driver is not installed. I can at this point
manually install it, and that works, but that's besides
the point.

Do you guys have any idea why it is not being
automatically installed during PnP detection?

Thanks

.

 

[Lucvdv]

All the files for the component seem to be correctly
pointed to the folder in which they exist. This includes
the .cat file.

Any other suggestion? Do I need to set a certain build
order dependency for a network adapter?

There are "Intel Pro 1000" and "Intel Pro/1000 T" components included in
XPE, they're probably very similar to how yours for the Pro/1000 MT should
look.

If you add all three to an empty project and compare the resources of the
original ones to yours (double-click each resource to see the details), it
might point out what's wrong.

 

[Slobodan Brcin]

If you want I can send you modified inf file it should work on all Intel GB
adapters (I have tested in only on two types)

Contact me offline.

Regards,
Slobodan

All the files for the component seem to be correctly
pointed to the folder in which they exist. This includes
the .cat file.

Any other suggestion? Do I need to set a certain build
order dependency for a network adapter?

Thanks

-----Original Message-----
Check the destination path of the file resources for the component you
created. I have seen odd cases where the path of the catalog file name
(*.cat file) is incorrectly set to %66000%. If that's the case set it to the
actual destination path of the resource to match that of where it gets
installed in your XP Pro test machine.

--
Joe Morris [MS]

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

I am fairly new to the world of XPE, so please be patient
with me. I have spent a lot of time going through the
documentation and tips, but have been unable to resolve
this current issue.

I ran TAP.exe on my current machine, but somehow it did
not pick up my network card driver. The card is an Intel
Pro 1000/MT. While this driver is not included with XP
Pro, I do have drivers for it.

So I proceeded to create a component for this device from
the driver files. Here's what I did:
1)Used Component Designer to import .inf files
2)Created a Repository and set source path to driver files
3)Added repository to the component.
4)Added component to the Database.
5)Finally added component to my device configuration in TD

No errors at any step including build, however after FBA
finishes and I load up run time image, in device manager,
the network driver is not installed. I can at this point
manually install it, and that works, but that's besides
the point.

Do you guys have any idea why it is not being
automatically installed during PnP detection?

Thanks

.

 

[RussR]

Lucvdv,

I followed your advice and created a new blank project in
TD and then added the Intel Pro/1000 T and Intel Pro/1000
built in XPe driver components and then looked at
their "Resources" in TD. They both seemed to
have "Resources" and they were two sets of fields. The
first one was:
1)of type Service Data and seemed to be the device name
2)the others were PnP Device ID and had some strings
with "PCI\VEN_...."

The component I created from the driver for my Intel
Pro/1000 MT does not have any resources.

Any ideas?

 

[RussR]

Thanks to Slobodan who helped me offline, we finally figured out what the
problem was. I'm posting it here so it will be beneficial for others.

The problem is that not every import of a .inf file from a device driver
results in the correct path in the file resources under Component Designer.
For ex: in my case, the NIC driver set the path of all the files to the
repository directory on the target machine, but in reality, the .inf file
should be set to %17% and .sys to %12% and most other files to %11%
depending on where they reside on the XP Pro machine.

So after setting the paths for the file resources correctly, the driver was
added to NIC during PnP detection of the FBA process.

The paths can be set by clicking on the Files section under the Component.
Making sure that each file is pointed to the correct place it would reside
on the target machine when installed is key to getting it to work.

You don't have to manually do this all the time as some imports of .inf
files automatically set this.

-RussR

 

[Lucvdv]

Lucvdv,

I followed your advice and created a new blank project in
TD and then added the Intel Pro/1000 T and Intel Pro/1000
built in XPe driver components and then looked at
their "Resources" in TD. They both seemed to
have "Resources" and they were two sets of fields. The
first one was:
1)of type Service Data and seemed to be the device name
2)the others were PnP Device ID and had some strings
with "PCI\VEN_...."

The component I created from the driver for my Intel
Pro/1000 MT does not have any resources.

The service data resource contains the registry setting necessary to start
the driver (for the driver key under
HKLM\System\CurrentControlSet\Services\)

The PCI\VEN_... value is the network adapter's plug & play ID. Without the
correct value corresponding to the hardware here, the driver will never be
started even if it is installed.

This may not work, but the first thing I would try is look for this ID in
the Pro1000/MT's INF file and add it to the Pro/1000 T component after
adding it to the configuration. The Pro/1000 and 1000 T use the same
driver, only their PNP ID's differ, so if you're lucky the MT works with
this driver too.

If that doesn't work, I would try to create an MT component that mimics the
T as closely as possible, but with the correct driver (.sys) file and PNP
ID.

 

[RussR]

Lucvdv, see my final post in this thread titled "Finally got it working".
The solution had nothing to do with the resources and the service data
resources or the PnP ID, but with the placement of the .inf, .sys, and other
driver files in the appropriate place on the target machine.