Device config after cloning

[Doug G]

We use the usual procedure for XPE cloning, where I set up a "master"
device, do fbreseal, and then Ghost that for installation on the actual
targets. We have a particular PCI card in our device that, up to now, has
been the same for every target that we produce. But in the future, this
could be any one of three different cards. I am of course installing the
drivers for all three types in the image, but when I do the initial FBA
stuff, I obviously only have one particular type of card in the master
device that I'm using.

When we do the cloning of the target devices, will the actual installed
device be picked up during the first boot of the target and the drivers
correctly started, etc.? I guess I'm not sure of exactly how "static" the
device configuration is in the system before vs. after fbreseal (or at any
time for that matter). But I would assume that XPE does the basic PnP
processing of PCI devices on every boot -- correct?

Doug Gordon

 

[Slobodan Brcin \(eMVP\)]

Hi Doug,

When we do the cloning of the target devices, will the actual installed
device be picked up during the first boot of the target and the drivers
correctly started, etc.? I guess I'm not sure of exactly how "static" the
device configuration is in the system before vs. after fbreseal (or at any
time for that matter). But I would assume that XPE does the basic PnP
processing of PCI devices on every boot -- correct?

PnP is always active. And each lower (bus) driver will try to find out if
there is something new connected on hardware that it controls and if find
some hardware it will report it in registry by creating some basic entries
in enum branch.
Later on PnP will see that there are some entries there that are not fully
installed and will try to pick up valid inf file to do actual driver
instalation.
Once these entries are filled for particular hardware they won't be written
to by PnP anymore.

For each device VID/PID serialnumber change or position on bus depending on
bus driver. You will have slightly different unique reg entries created and
these will triger PnP again to install "new hardware".
Anyhow PnP is always working and will pick your new hardware, or hardware
that you have intentionaly deleted from registry by removing driver or
trough regedit.

Regards,
Slobodan

 

[Doug Gordon]

Hi Doug,


PnP is always active. And each lower (bus) driver will try to find out if
there is something new connected on hardware that it controls and if find
some hardware it will report it in registry by creating some basic entries
in enum branch.
Later on PnP will see that there are some entries there that are not fully
installed and will try to pick up valid inf file to do actual driver
instalation.
Once these entries are filled for particular hardware they won't be
written to by PnP anymore.

For each device VID/PID serialnumber change or position on bus depending
on bus driver. You will have slightly different unique reg entries created
and these will triger PnP again to install "new hardware".
Anyhow PnP is always working and will pick your new hardware, or hardware
that you have intentionaly deleted from registry by removing driver or
trough regedit.

Regards,
Slobodan

Slobodan:
Thanks for the info. I was able to experiment with this late yesterday and
it does work as I had hoped. Now all I have to do is figure out why the new
PCI card works fine in my Dell desktop under XP Pro but does not work on the
target device under either XP Pro or XPE. But it is definitely not an XPE
issue (if it were, I might be able to solve it more easily). Grrrr...

Doug Gordon

 

[Slobodan Brcin \(eMVP\)]

Doug,

Continue testing on XPP.
1. Delete setupapi.log
2. Go to device manager and remove driver if it is there.
3. Restart computer and check setupapi.log to see if there is any indication
of your hardware.

Or when you add new hardware just:
1. Delete setupapi.log
2. Shutdown.
3. Plugin card.
4. boot and check setupapi.log for infos.

Regards,
Slobodan