->Sysprep->OemPnPDriversPath->for multiple machines/brands

Hi there,

I use sysprep and Ghost 2003 and I want to create one single image for multiple machine brands/types.

I've created a folder structure on the boot partition (C:\Drivers\(brand)\(type)\(device))

In the [Unattend] section of sysprep.inf I have the following statements:

;Dell Lattitude C810
OemPnPDriversPath = Drivers\Dell\C810\Modem;Drivers\Dell\C810\Nic;

;Dell Lattitude C840
OemPnPDriversPath = Drivers\Dell\C840\Modem;Drivers\Dell\C840\Nic;


The C810 works fine, but all other OemPnPDriversPaths are discarded. Is this fixable or is there an other solution for this?

Thanx in advance, Harold.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rob StoneCommented:
Do others work if you put them to the top of the list?

alingAuthor Commented:
I've found out the following:

All folders set in OemPnPDriversPath are added to the registry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath so if I specify multiply (6+) different machines, the first path is stored in the registry and all other paths are discarded.

If I add all macines to one line, it becomes very unreadable and unmanageable, and I don't want that to happen.

I can't place all .inf+drivers into one folder per machinetype because the drivers all have identical names (ie data1.cab etc)

It seems that the only solution is to work with different registry keys per machine type. Maybe write a batch file wich will copy the correct drivers and set the correct registry key per machinetype.

Or are there other suggestions?

Thanx, Harold.
String them all on one line.

Instead of:
;Dell Lattitude C810
OemPnPDriversPath = Drivers\Dell\C810\Modem;Drivers\Dell\C810\Nic;

;Dell Lattitude C840
OemPnPDriversPath = Drivers\Dell\C840\Modem;Drivers\Dell\C840\Nic;


OemPnPDriversPath = Drivers\Dell\C810\Modem;Drivers\Dell\C810\Nic;Drivers\Dell\C840\Modem;Drivers\Dell\C840\Nic;

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Well I saw your comment about the one line and readability after I posted; but I think this is the solution.
I think I provided aling with the answer to aling's question.
alingAuthor Commented:
Oops, forgot all about this Q... Sorry 'bout that...

Here's what I've done: I havn't used any of your answers... I've only added the NIC drivers to the sysprep.inf file and lateron I've batched the copying and installation of the system specific drivers...

What to do with the points? I do use gemarti's comment for installing the NIC drivers... So, that will be my choice...

Thank you all for helping me out!!!
Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.