Asked By patrick
17-Nov-09 09:20 PM
I am having a little trouble getting a thin client to work with remote
boot PXE. I have built my image both with and without "componetized"
drivers with the same end result. After image is built, I run through
FBA, manually install drivers (in the second case with the driver
components disabled), fbreseal, then transfer back to my dev machine
to create SDI and copy to server. The trouble is that one of the
network adapters "loses" its driver somewhere between fbreseal and sdi
creation/deployment. After PXE boot, when one adapter is connected to
the network, it is always the non-connected adapter that has the
problem. When both adapters are connected to the network, the image
runs as intended, but I still get trouble with one adapter. I get
the drivers. I know I can disable the "Found New Hardware" wizard and
it will be transparent to the user, but that is not a very clean way of
doing it. I have looked through setupapi.log and fba.log without too
much luck. Again, I come to the same end result whether or not I use
components for drivers. I know nVidia video drivers do not like to be
made into components, and I am starting to have the feeling that
chipset/ethernet drivers for the MCP55 are the same way. In addition,
I have attempted to use the SLD provided on Sean Liming's site (http://
www.seanliming.com/WES2009_XPe.html) to set the installation to occur
after FBA reboot. The installation proceeds in the same way as if I
run from the driver CD. I thank you in advance for any help that you
can provide.