sysprep image with multiple drivers

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I'm currently evaluating the use of one image file to be used across 7
different models of hardware. The image includes all of the required drivers
and the sysprep.inf files includes the paths to these locations. The problem
that I am having is that one particular model keeps installing the incorrect
display drivers but all the others install their correct drivers.

Any one else came across this before or have any suggestions how I can
overcome this problem?
 
The 883667 hotfix solves some issues with video drivers not being
correctly installed in the sysprep minisetup


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment
 
Hi,

I'm currently evaluating the use of one image file to be used
across 7 different models of hardware. The image includes all of
the required drivers and the sysprep.inf files includes the paths
to these locations. The problem that I am having is that one
particular model keeps installing the incorrect display drivers
but all the others install their correct drivers.

Any one else came across this before or have any suggestions how I
can overcome this problem?
Click to expand...

Cross reference the device instance id in the device manager and search
for that string in your INF files. Assume that id is pci\ven_1106&dev_
3058&subsys_05C00E11.

Here's a very small snippet from a Soundmax INF file:

%*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415
&subsys_B1840E11
%*WDM_AC97AUD.DeviceDesc%=WDM_ICHAUD, pci\ven_8086&dev_2415
&subsys_B1850E11

So, in above example, Sysprep finds a audio driver in C:\install\driver
\hp160\sound. Maybe, just maybe, that same string is in a later INF
file. Sysprep, however, doesn't care about that. It just picks the
first INF file that contains the text its looking for and runs with it.

Check out http://www.leinss.com/uniimg.html and read over the section
on OEM INF files. It may be as simple as re-ordering your driver paths
or making sure you don't have any bum INF files hanging out there. Put
your path to the troubled video drivers at the beginning of your
OEMPnPDriversPath statement and be sure to clean out your DevicePath
key as given in the above website.

Adam
 
Back
Top