Sysprep again

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

Guest

Hi,

I posted about this some months back, but I still have some questions.

I have already preinstalled this wireless adapter in my XP Pro image, and
then I sysprep it. Once minisetup is done and when I do the first log in, the
system prompts me to install the wireless adapter again. Is this the expected
behaviour? I did not specify the driver paths in the sysprep.inf.

Why does Windows still prompt for installation even though I have already
preinstalled the driver? Is there another workaround besides having to
specify driver paths in the sysprep.inf file?

Thanks very much!
 
Hi,

I posted about this some months back, but I still have some
questions.

I have already preinstalled this wireless adapter in my XP Pro
image, and then I sysprep it. Once minisetup is done and when I do
the first log in, the system prompts me to install the wireless
adapter again. Is this the expected behaviour? I did not specify
the driver paths in the sysprep.inf.
Click to expand...

Are you specifying -pnp for sysprep? If so, remove it.

Yes, sysprep tends to do this. Best to grin and bare it and put the
driver paths in your sysprep.inf file.

Adam
 
Hi Adam,

No, I am simply double clicking on Sysprep from Windows :)

I tried using the workarounds recommended, and it fixed the wireless driver
problem ... BUT ... the rest of the hardware installations got messed up. I
tried putting all the driver paths in, but I still end up with multiple
installations/unknown devices after sysprep. Some of the HW installations
are COM port installations and are not physically attached hardware.
Basically, if I just run Sysprep without trying to fix the unsigned driver
problem, everything is fine.

Am I missing something here? I tried the following lines and toggled with
the last two settings with combis of Yes/Nos, but still couldn't get all the
problem resolved. I am using Minisetup with Reseal.


DriverSigningPolicy=Ignore
InstallFilesPath=C:\Sysprep\i386
OemPnPDriversPath=\driver\xxx; (etc...etc...)
OEMPreinstall =No/No/Yes/Yes
UpdateInstalledDrivers=No/YesNo/Yes

Many thanks!
 
Am I missing something here? I tried the following lines and
toggled with the last two settings with combis of Yes/Nos, but
still couldn't get all the problem resolved. I am using Minisetup
with Reseal.


DriverSigningPolicy=Ignore
InstallFilesPath=C:\Sysprep\i386
OemPnPDriversPath=\driver\xxx; (etc...etc...)
OEMPreinstall =No/No/Yes/Yes
UpdateInstalledDrivers=No/YesNo/Yes
Click to expand...

See http://www.leinss.com/files/sysprep.inf for a sample sysprep.inf
file. This one worked fine for two of my employers. Try setting
InstallFilesPath=C:\sysprep and leave off the leading \ for the
paths,so it reads OEMPnPDriversPath=driver\video;driver\audio; etc.

Check HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath with
regedit. Clean it out so that only C:\windows\inf shows up. If this
path is > 2048 characters, everything past the 2048th character is
ignored. Essentially, when you run sysprep, it appends the path set by
OEMPnPDriversPath to the DevicePath key so that over time your
DevicePath becomes incredibly huge and unwieldy.

Try issuing just "sysprep -mini -pnp" and see if your device
installations come up. Also, you might want to purge all OEM*.INF
files from C:\windows\inf each time before you close the image with
sysprep.

OEMPreinstall should have no effect on driver installation.

Adam
 
Back
Top