New to designing targets : device drivers

[Martin Dowie]

Hi,
First time WinXPe user with a "how to" question.

We are developing an embedded device with Flash as the storage media. Our
development rig uses an HDD and we have WinXP Pro installed on this. We
generated our DEVICES.PMQ file and we've started to define a target. 4 of the
board devices drivers need to be included in the final image but are not
supported out-of-the-box by the WinXPe Toolkit. Unfortunately none of them
come with a nice simple .inf file to generate a new component from to create
a new component from.

I was wondering that as we will nee to perform the FBA boot of our WinXPe
image on the HDD development rig anyway, could I just create a component that
lists the .exe setup files as RunOnce "Extra Resources" and install them then?

We're looking (as ever!) for a quick solution but repeatable - it doesn't
have to be the "nicest" or the "one true WinXPe way".

TIA

Martin

 

[Sean Liming \(MVP\)]

You can create driver components and installer components. It is perfectly
okay to install post-FBA, but in my experience, it is better to componentize
the drivers.

I use my Component Helper program to capture a driver installation, others
use InCTRL 5. In either case, once the driver has been install you can then
import the INF. The other trick is to look in your Win XP Pro image - look
in the \windows\inf folder to oem#.inf files. These are most likely the INF
files you need.

--
Regards,

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

 

[Martin Dowie]

Sean,

Thanks for the reply - so at least this approach sounds feasible and we're
not going totally off-beam.

I'd be more inclined to conponentize these drivers 'properly' if we were
going to be installing 1000's of systems or loads of different systems but
that's just not the sort of business we're in.

And we need something that works /real/ soon!

Cheers
-- Martin