Windows 2000 Professional Sysprep Drivers

G

Guest

Thank You in advance for your assistance..

I am creating a base image for multiple desktop systems, and am running into
a problem with sysprep and pnp loading drivers correctly during the
mini-setup process. Per many articles released by Microsoft, I believe I am
following the correct procedure. Please see a snippet of my sysprep.inf:

[Unattended]
OemSkipEula=Yes
OemPreinstall = Yes
DriverSigningPolicy = Ignore
OemPnPDriversPath=DRIVERS\audio;DRIVERS\Ethernet;DRIVERS\video

The drivers themselves are loaded on the root of C: in a folder titled
"DRIVERS". Please see below:

C:\DRIVERS
C:\DRIVERS\audio
C:\DRIVERS\Ethernet
C:\DRIVERS\video

Now, it is my understanding that if the drivers are entirely there, and the
sysprep references the folders correctly, there should be no problem loading
the drivers during the mini-setup.

But, the problem is- the drivers are not installing on the workstation
during the mini-setup. Before I created the image, I ran sysprep.exe with the
-pnp option to reenumerate all PnP devices. However, this is not working as I
think it should.. Can someone tell me what I'm doing wrong?


Many Thanks,

Drummer9909
 
J

John Bell

Do any of the drivers have to have a *.exe run to install the drivers. Thats
the only way Unattended will do it is if the .inf files are there

Oh and add " to you OEMPNPDrivers path like
OemPnPDriversPath="DRIVERS\audio;Drivers\Ethernet;drivers\video:"
That should work.
John
 
G

Guest

Thanks for the reply. The drivers do have individual exes to install them,
but I have extracted the .inf, .sys, and .cat files to those directory.

I have tried enclosing the overall path statement in quotations, but that
hasn't worked.. I'll try again..

Thanks!

John Bell said:
Do any of the drivers have to have a *.exe run to install the drivers. Thats
the only way Unattended will do it is if the .inf files are there

Oh and add " to you OEMPNPDrivers path like
OemPnPDriversPath="DRIVERS\audio;Drivers\Ethernet;drivers\video:"
That should work.
John


Drummer9909 said:
Thank You in advance for your assistance..

I am creating a base image for multiple desktop systems, and am running
into
a problem with sysprep and pnp loading drivers correctly during the
mini-setup process. Per many articles released by Microsoft, I believe I
am
following the correct procedure. Please see a snippet of my sysprep.inf:

[Unattended]
OemSkipEula=Yes
OemPreinstall = Yes
DriverSigningPolicy = Ignore
OemPnPDriversPath=DRIVERS\audio;DRIVERS\Ethernet;DRIVERS\video

The drivers themselves are loaded on the root of C: in a folder titled
"DRIVERS". Please see below:

C:\DRIVERS
C:\DRIVERS\audio
C:\DRIVERS\Ethernet
C:\DRIVERS\video

Now, it is my understanding that if the drivers are entirely there, and
the
sysprep references the folders correctly, there should be no problem
loading
the drivers during the mini-setup.

But, the problem is- the drivers are not installing on the workstation
during the mini-setup. Before I created the image, I ran sysprep.exe with
the
-pnp option to reenumerate all PnP devices. However, this is not working
as I
think it should.. Can someone tell me what I'm doing wrong?


Many Thanks,

Drummer9909
 
J

John Bell

In my winnt.sif file i have the
OemPnpDirversPath="\Drivers\audio;\Drivers\ethernet;\Drivers\video"


Try to add the \ before drivers and see what happens then.

John

Drummer9909 said:
Thanks for the reply. The drivers do have individual exes to install them,
but I have extracted the .inf, .sys, and .cat files to those directory.

I have tried enclosing the overall path statement in quotations, but that
hasn't worked.. I'll try again..

Thanks!

John Bell said:
Do any of the drivers have to have a *.exe run to install the drivers.
Thats
the only way Unattended will do it is if the .inf files are there

Oh and add " to you OEMPNPDrivers path like
OemPnPDriversPath="DRIVERS\audio;Drivers\Ethernet;drivers\video:"
That should work.
John


Drummer9909 said:
Thank You in advance for your assistance..

I am creating a base image for multiple desktop systems, and am running
into
a problem with sysprep and pnp loading drivers correctly during the
mini-setup process. Per many articles released by Microsoft, I believe
I
am
following the correct procedure. Please see a snippet of my
sysprep.inf:

[Unattended]
OemSkipEula=Yes
OemPreinstall = Yes
DriverSigningPolicy = Ignore
OemPnPDriversPath=DRIVERS\audio;DRIVERS\Ethernet;DRIVERS\video

The drivers themselves are loaded on the root of C: in a folder titled
"DRIVERS". Please see below:

C:\DRIVERS
C:\DRIVERS\audio
C:\DRIVERS\Ethernet
C:\DRIVERS\video

Now, it is my understanding that if the drivers are entirely there, and
the
sysprep references the folders correctly, there should be no problem
loading
the drivers during the mini-setup.

But, the problem is- the drivers are not installing on the workstation
during the mini-setup. Before I created the image, I ran sysprep.exe
with
the
-pnp option to reenumerate all PnP devices. However, this is not
working
as I
think it should.. Can someone tell me what I'm doing wrong?


Many Thanks,

Drummer9909
 
G

Guest

John,

Thanks for all your help.. Though I had the syntax right, my procedure was
wrong. In looking at the values (EXPAND_SZ) of the DevicePath reg entry, the
values from the sysprep.inf were not populating over. I found that if you
create your sysprep.inf and place it in the sysprep folder before you
actually run sysprep.exe, the values will populate over. I sort of defeats
the purpose for what I'm doing, but I found a way around it. I'm using Ghost,
WinPE, and a custom VB app to build base images for workstations, and the
reg.exe command-line util will allow you to load and edit the reg hives for
OS's even if they are not loaded. This allowed me to programatically change
the DevicePath reg entry to the paths I needed, really eliminating the need
for the OEMPnpDriversPath. My original goal was to run sysprep on the
original base image, then apply a custom sysprep.inf depending on what type
of image I needed to build.

Once again, thank you for your assistance.

John Bell said:
In my winnt.sif file i have the
OemPnpDirversPath="\Drivers\audio;\Drivers\ethernet;\Drivers\video"


Try to add the \ before drivers and see what happens then.

John

Drummer9909 said:
Thanks for the reply. The drivers do have individual exes to install them,
but I have extracted the .inf, .sys, and .cat files to those directory.

I have tried enclosing the overall path statement in quotations, but that
hasn't worked.. I'll try again..

Thanks!

John Bell said:
Do any of the drivers have to have a *.exe run to install the drivers.
Thats
the only way Unattended will do it is if the .inf files are there

Oh and add " to you OEMPNPDrivers path like
OemPnPDriversPath="DRIVERS\audio;Drivers\Ethernet;drivers\video:"
That should work.
John


Thank You in advance for your assistance..

I am creating a base image for multiple desktop systems, and am running
into
a problem with sysprep and pnp loading drivers correctly during the
mini-setup process. Per many articles released by Microsoft, I believe
I
am
following the correct procedure. Please see a snippet of my
sysprep.inf:

[Unattended]
OemSkipEula=Yes
OemPreinstall = Yes
DriverSigningPolicy = Ignore
OemPnPDriversPath=DRIVERS\audio;DRIVERS\Ethernet;DRIVERS\video

The drivers themselves are loaded on the root of C: in a folder titled
"DRIVERS". Please see below:

C:\DRIVERS
C:\DRIVERS\audio
C:\DRIVERS\Ethernet
C:\DRIVERS\video

Now, it is my understanding that if the drivers are entirely there, and
the
sysprep references the folders correctly, there should be no problem
loading
the drivers during the mini-setup.

But, the problem is- the drivers are not installing on the workstation
during the mini-setup. Before I created the image, I ran sysprep.exe
with
the
-pnp option to reenumerate all PnP devices. However, this is not
working
as I
think it should.. Can someone tell me what I'm doing wrong?


Many Thanks,

Drummer9909
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top