drivers problems in xp unattended

[johga]

Hello there,

Im using a deployment tool to try to install Windows XP on our machines. We have a few different models and I would like to include all the drivers for them in this image.

My problem is that when OemPnPDriversPath get's too long then the installation stops the installation at 39 minutes left. I'm then prompted with a Welcome message and asked to press Next to continue. After the button is pressed everything continues in unattended mode. Is there a way to get around this screen?

I'm testing this image distribution on VMware 5.5.

My non working unattended.inf:

;SetupMgrTag

[unattended]

UnattendMode=FullUnattended

TargetPath=\WINDOWS

OemSkipEula=Yes

OemPreinstall=Yes

NoWaitAfterTextMode=1

NoWaitAfterGuiMode=1

FileSystem=ConvertNTFS

ExtendOemPartition=1

DriverSigningPolicy=Ignore

UnattendSwitch=Yes

Autoactivate=No

ActivateProxy=Proxyact

OemPnPDriversPath="drivers\chipset\1;drivers\chipset\2;drivers\display\1;

drivers\display\2;drivers\modem\1;drivers\modem\1;drivers\monitor\1;

drivers\mouse\1;drivers\mouse\2;drivers\network\1;drivers\pcmcia\1;

drivers\sound\1;drivers\video\1;drivers\other\1"

The above OemPnPDriversPath is too long and I'm prompted with the message. It's aprox 260 characters long. The one below does work and is aprox 160 characters. I've read someplace that the maximum length is over 4000 characters in Windows XP so this should not be the problem.

OemPnPDriversPath="drivers\chipset\;drivers\network\;drivers\video\;

drivers\sound\;drivers\monitor\;drivers\modem\;drivers\pcmia\;

drivers\mouse\;drivers\display\;"

Here's a screenshot of the message that prevents the setup from continuing:

http://img184.imageshack.us/img184/1982/sshot1rk5.png

Edit:

Will running the setup from an FAT16 partition limit me to 256 characters in the unattend.inf even though the Windows XP setup should support over 4000 chars? The FAT16 partition is a result of my deployment system.

Edited December 13, 2006 by johga

[IcemanND]

you could do a couple of things. you could rename the drivers folder to D instead of DRIVERS that will save you almsot 80 characters. You could also do the same with the sub folders.

Or you could add the paths directly to the registry key and not use oempnpdriverspath in you answer file at all.

There is a setdevicepath.exe app here on MSFN that you could run to populate the regitry key before the drivers are needed.

What deployment tool are you using?

[johga]

I tried adding the paths to the registry once before but I couldnt get it to work. I will however try it once more with that tool ... if I'll manage to find it.

I've thought about shortening the foldernames and I will do this if nothing else works.

I'm using CA Unicenter Software Delivery 4.0 SP1 (Boot Management) to deploy the OS.

No problem finding the file. Google is my friend Also, thanks for the reply!

Edited December 14, 2006 by johga