Third Party Drivers

I have printed and read just about all the tutorials MS had published,
watched all the videos, read the WXPE step by step book and read all the
related messages posted on this newsgroup and have not yet found any
solution (Step By Step Procedure) for importing and resolving issues with
oem inf files (device drivers) listed under inf directory for devices such
as video, sound NIC, etc. There are a lot of wonderful ideas but non that
have actually been working. I have tried many of the links regarding
componentizing 3rd party drivers but most of them have skipped over steps
and the final procedure had not worked. I was wondering if anyone has
actually created an embedded image and imported inf files for an oem device
into the Target Designer and got it working? If so would you please share
your knowledge with us. We have now been working on this project for over a
month with no hope in sight. I greatly appreciate your suggestions. I will
gladly compensate any direct instruction to resolve my problem. Thank You.

I have created several components from INF files. There are some tricks for
some device driver components, but this can't easily be posted to a news
group. What problems are you running into?

Regards,

Sean Liming
XP Embedded Manager
www.a7eng.com
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step





"CSI Support" <support@cyberviewsystems.com> wrote in message
news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
> I have printed and read just about all the tutorials MS had published,
> watched all the videos, read the WXPE step by step book and read all the
> related messages posted on this newsgroup and have not yet found any
> solution (Step By Step Procedure) for importing and resolving issues with
> oem inf files (device drivers) listed under inf directory for devices such
> as video, sound NIC, etc. There are a lot of wonderful ideas but non that
> have actually been working. I have tried many of the links regarding
> componentizing 3rd party drivers but most of them have skipped over steps
> and the final procedure had not worked. I was wondering if anyone has
> actually created an embedded image and imported inf files for an oem
device
> into the Target Designer and got it working? If so would you please share
> your knowledge with us. We have now been working on this project for over
a
> month with no hope in sight. I greatly appreciate your suggestions. I
will
> gladly compensate any direct instruction to resolve my problem. Thank
You.
>
>

I don't understand why you have so many problems.
You are not trying to do anything unusual.

Fist some basics.
If you only copy inf dll, sys files in inf, system32 and system32\drivers
directories PNP will do in most cases all the work of installation.
This is good place to start.
In windows directory there are log files that will tell you if driver
installation was rejected.

Also using CD for componentizing driver from inf file will do the job of
making component in most cases without your, or with little intervention.
You can try even to manually install driver to see if it requires some
additional dependencies.
Most reasons why driver want to reject installation is because inf files are
polluted with references to dll files that are used for control panel
support, etc that are not real part of driver and to install they need heavy
support of other components than are not related to your project. The only
solution I have fount to this is to customize inf files and to carefully
remove all entries that are not needed for driver to function properly.

You should tell us what driver is giving you trouble. And if it is not some
standard driver you should attach inf file to post in this NG, so we can
take a look at it.


Best regards,
Slobodan



"CSI Support" <support@cyberviewsystems.com> wrote in message
news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
> I have printed and read just about all the tutorials MS had published,
> watched all the videos, read the WXPE step by step book and read all the
> related messages posted on this newsgroup and have not yet found any
> solution (Step By Step Procedure) for importing and resolving issues with
> oem inf files (device drivers) listed under inf directory for devices such
> as video, sound NIC, etc. There are a lot of wonderful ideas but non that
> have actually been working. I have tried many of the links regarding
> componentizing 3rd party drivers but most of them have skipped over steps
> and the final procedure had not worked. I was wondering if anyone has
> actually created an embedded image and imported inf files for an oem
device
> into the Target Designer and got it working? If so would you please share
> your knowledge with us. We have now been working on this project for over
a
> month with no hope in sight. I greatly appreciate your suggestions. I
will
> gladly compensate any direct instruction to resolve my problem. Thank
You.
>
>

I incorporated 4 third party drivers just this week. What specific problems
are you running into?

The most confusing problem I ran into was seeing something to the effect of
"blah blah [BROADCOM] is empty" error message. That turns out to be a
situation where you need to use a custom parser when importing the .inf into
component designer. In my case, I had to set the Manufacturer to "BROADCOM,
NTx86.5.1".

Did you consult
http://www.microsoft.com/windows/em...rivererrors.asp
?

--Gordon Smith (eMVP)


"CSI Support" <support@cyberviewsystems.com> wrote in message
news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
> I have printed and read just about all the tutorials MS had published,
> watched all the videos, read the WXPE step by step book and read all the
> related messages posted on this newsgroup and have not yet found any
> solution (Step By Step Procedure) for importing and resolving issues with
> oem inf files (device drivers) listed under inf directory for devices such
> as video, sound NIC, etc. There are a lot of wonderful ideas but non that
> have actually been working. I have tried many of the links regarding
> componentizing 3rd party drivers but most of them have skipped over steps
> and the final procedure had not worked. I was wondering if anyone has
> actually created an embedded image and imported inf files for an oem
device
> into the Target Designer and got it working? If so would you please share
> your knowledge with us. We have now been working on this project for over
a
> month with no hope in sight. I greatly appreciate your suggestions. I
will
> gladly compensate any direct instruction to resolve my problem. Thank
You.
>
>

Hi Gordon,

I was interested in the steps you took to get those 3rd party drivers
working. I have been to the site you mentioned and followed the steps but
was not successful. There are areas that was not clear on the link's
instructions. The drivers I am working are all Intel based. The 845G
video, Chipset inf, Intel AA, Avance AC97 sound and Intel 100pro NIC. Any
ideas?

Thanks
Mike


"Gordon Smith (eMVP)" <Gordon.Smith@nospam.avnet.com> wrote in message
news:#xcwlbClDHA.2732@TK2MSFTNGP11.phx.gbl...
> I incorporated 4 third party drivers just this week. What specific
problems
> are you running into?
>
> The most confusing problem I ran into was seeing something to the effect
of
> "blah blah [BROADCOM] is empty" error message. That turns out to be a
> situation where you need to use a custom parser when importing the .inf
into
> component designer. In my case, I had to set the Manufacturer to
"BROADCOM,
> NTx86.5.1".
>
> Did you consult
>
http://www.microsoft.com/windows/em...rivererrors.asp
> ?
>
> --Gordon Smith (eMVP)
>
>
> "CSI Support" <support@cyberviewsystems.com> wrote in message
> news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
> > I have printed and read just about all the tutorials MS had published,
> > watched all the videos, read the WXPE step by step book and read all the
> > related messages posted on this newsgroup and have not yet found any
> > solution (Step By Step Procedure) for importing and resolving issues
with
> > oem inf files (device drivers) listed under inf directory for devices
such
> > as video, sound NIC, etc. There are a lot of wonderful ideas but non
that
> > have actually been working. I have tried many of the links regarding
> > componentizing 3rd party drivers but most of them have skipped over
steps
> > and the final procedure had not worked. I was wondering if anyone has
> > actually created an embedded image and imported inf files for an oem
> device
> > into the Target Designer and got it working? If so would you please
share
> > your knowledge with us. We have now been working on this project for
over
> a
> > month with no hope in sight. I greatly appreciate your suggestions. I
> will
> > gladly compensate any direct instruction to resolve my problem. Thank
> You.
> >
> >
>
>

The 845G drivers have already been componentized by Brad Combs. You can
find those on www.xpefiles.com. The intel NIC driver may be on xpefiles as
well, I'm not positive.

Feel free to email the drivers to me and I'll make components out of them.
As a previous poster said, there are a variety of issues that may make 3rd
party drivers 'interesting' to incorporate. After completing the component
for the driver, I'd be more than happy to document the process I used to
finish the component.

Another method some people use to make driver installation easier is to
include the Windows Installer Service along with the appropriate Class
Installers then install the drivers after FBA completes.

--Gordon

Mike wrote:
> Hi Gordon,
>
> I was interested in the steps you took to get those 3rd party drivers
> working. I have been to the site you mentioned and followed the
> steps but was not successful. There are areas that was not clear on
> the link's instructions. The drivers I am working are all Intel
> based. The 845G video, Chipset inf, Intel AA, Avance AC97 sound and
> Intel 100pro NIC. Any ideas?
>
> Thanks
> Mike
>
>
> "Gordon Smith (eMVP)" <Gordon.Smith@nospam.avnet.com> wrote in message
> news:#xcwlbClDHA.2732@TK2MSFTNGP11.phx.gbl...
>> I incorporated 4 third party drivers just this week. What specific
>> problems are you running into?
>>
>> The most confusing problem I ran into was seeing something to the
>> effect of "blah blah [BROADCOM] is empty" error message. That turns
>> out to be a situation where you need to use a custom parser when
>> importing the .inf into component designer. In my case, I had to
>> set the Manufacturer to "BROADCOM, NTx86.5.1".
>>
>> Did you consult
>>
>
http://www.microsoft.com/windows/em...rivererrors.asp
>> ?
>>
>> --Gordon Smith (eMVP)
>>
>>
>> "CSI Support" <support@cyberviewsystems.com> wrote in message
>> news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
>>> I have printed and read just about all the tutorials MS had
>>> published, watched all the videos, read the WXPE step by step book
>>> and read all the related messages posted on this newsgroup and have
>>> not yet found any solution (Step By Step Procedure) for importing
>>> and resolving issues with oem inf files (device drivers) listed
>>> under inf directory for devices such as video, sound NIC, etc.
>>> There are a lot of wonderful ideas but non that have actually been
>>> working. I have tried many of the links regarding componentizing
>>> 3rd party drivers but most of them have skipped over steps and the
>>> final procedure had not worked. I was wondering if anyone has
>>> actually created an embedded image and imported inf files for an
>>> oem device into the Target Designer and got it working? If so
>>> would you please share your knowledge with us. We have now been
>>> working on this project for over a month with no hope in sight. I
>>> greatly appreciate your suggestions. I will gladly compensate any
>>> direct instruction to resolve my problem. Thank You.

--
Gordon Smith (eMVP)
Gordon.Smith@nospam.avnet.com

Mike,
Intel chipsets are my favorite, they are easy to handle.
Just make component that will copy Ich4Ide.inf, Ich4Core.inf, Ich4Usb.inf to
inf directory.
And add to TD following components:
PCI Bus
PCI standard EISA bridge
PCI standard host CPU bridge
PCI standard ISA bridge
PCI standard PCI-to-PCI bridge
PCI standard RAM controler
USB 2.0
Standard USB HUB
Standard Universal PCI to USB Host Controller
Standard IDE/ESDI Hard Disk Controller
Standard Enchanced PCI to USB Host Controller
Stnadard Dual Channel PCI IDE Controler
Intel Processor to AGP Controller

Probably you won't need all this components but since they are using the
same files, only thing that is affected is registry so your image size won't
be changed.

Only component that you need to create is for SMBios, and it can be created
from registry info of working XP.

Since I don't use sound I can't tell you what you exactly need to support
it.

Network also can work without component.
But inf file need to be changed to remove all files and entries related to
user mode files that are used for configuration, uninstall, etc.
You need only one inf, and one sys file.
I have custom inf but for Intel(R) PRO/1000 series of cards.

For video I use GeForce so I can't tell you what is required for Intel video
to work.


Regards,
Slobodan

"Mike" <mike@cyberviewsystems.com> wrote in message
news:ewNIXPFlDHA.2488@TK2MSFTNGP12.phx.gbl...
> Hi Gordon,
>
> I was interested in the steps you took to get those 3rd party drivers
> working. I have been to the site you mentioned and followed the steps but
> was not successful. There are areas that was not clear on the link's
> instructions. The drivers I am working are all Intel based. The 845G
> video, Chipset inf, Intel AA, Avance AC97 sound and Intel 100pro NIC. Any
> ideas?
>
> Thanks
> Mike
>
>
> "Gordon Smith (eMVP)" <Gordon.Smith@nospam.avnet.com> wrote in message
> news:#xcwlbClDHA.2732@TK2MSFTNGP11.phx.gbl...
> > I incorporated 4 third party drivers just this week. What specific
> problems
> > are you running into?
> >
> > The most confusing problem I ran into was seeing something to the effect
> of
> > "blah blah [BROADCOM] is empty" error message. That turns out to be a
> > situation where you need to use a custom parser when importing the .inf
> into
> > component designer. In my case, I had to set the Manufacturer to
> "BROADCOM,
> > NTx86.5.1".
> >
> > Did you consult
> >
>
http://www.microsoft.com/windows/em...rivererrors.asp
> > ?
> >
> > --Gordon Smith (eMVP)
> >
> >
> > "CSI Support" <support@cyberviewsystems.com> wrote in message
> > news:ucrMHSClDHA.2456@TK2MSFTNGP09.phx.gbl...
> > > I have printed and read just about all the tutorials MS had published,
> > > watched all the videos, read the WXPE step by step book and read all
the
> > > related messages posted on this newsgroup and have not yet found any
> > > solution (Step By Step Procedure) for importing and resolving issues
> with
> > > oem inf files (device drivers) listed under inf directory for devices
> such
> > > as video, sound NIC, etc. There are a lot of wonderful ideas but non
> that
> > > have actually been working. I have tried many of the links regarding
> > > componentizing 3rd party drivers but most of them have skipped over
> steps
> > > and the final procedure had not worked. I was wondering if anyone
has
> > > actually created an embedded image and imported inf files for an oem
> > device
> > > into the Target Designer and got it working? If so would you please
> share
> > > your knowledge with us. We have now been working on this project for
> over
> > a
> > > month with no hope in sight. I greatly appreciate your suggestions.
I
> > will
> > > gladly compensate any direct instruction to resolve my problem. Thank
> > You.
> > >
> > >
> >
> >
>
>