pnpdrvrs\ and subfolders?

  • Thread starter Thread starter Gerry Hickman
  • Start date Start date
G

Gerry Hickman

Hi,

Is it possible to tell the pnp Drivers installer to recurse all
subfolders looking for drivers? At present I have to add every single
path separated by semicolons and it's getting a bit long!

drv\audio;drv\video;drv\nics;drv\storage and so on.

I'm trying to create a build that will work with 5 models of desktop,
and three models of laptop.
 
I've looked into this and it seems not. It would be very nice if it did.

I do a similar thing. If I can group up all the drivers of a certain class
into a single directory, I do so. Some drivers make it difficult, though,
by using the same filenames.

It would be nice to see this improved on in Longhorn.

Cheers

Oli
 
Oli said:
I've looked into this and it seems not. It would be very nice if it did.
OK.

I do a similar thing. If I can group up all the drivers of a certain class
into a single directory, I do so. Some drivers make it difficult, though,
by using the same filenames.
Click to expand...

Yes, I have the same problem, the filenames clash!
It would be nice to see this improved on in Longhorn.
Click to expand...

I agree. From what I can tell the deployment tools are not very
different for XP to what they were in 2000? I'm not sure about Windows
Server 2003. I have to do a build for this early next year.
 
XP has some new options for the XP-specific features, but is quite similar
to 2000. Windows Server 2003 is very similar to Windows XP, obviously with
the addition of the server-specific options.

Longhorn, from what I've read on MSDN, will be a very different beast with
respect to setup.

Cheers

Oli
 
Hi, Gerry. I got annoyed by this, too, so I automated it. My system
scans ...\$oem$\$1 looking for directories containing .inf files, and
then lets you select from a menu which ones to add to
OemPnPDriversPath.

So when I want to add a new driver to my build, I just copy the
directory to $oem$\$1\drivers and it automagically appears in the
menu.

(You can also tell my system to skip the menu and just add all of the
directories to OemPnPDriversPath. This is one of the examples on the
"advanced configuration" page.)

Cheers!

- Pat
http://unattended.sourceforge.net/
 
Patrick said:
So when I want to add a new driver to my build, I just copy the
directory to $oem$\$1\drivers and it automagically appears in the
menu.
Click to expand...

Thanks, this sounds good!
 
Nice one!

Oli


Patrick J. LoPresti said:
Hi, Gerry. I got annoyed by this, too, so I automated it. My system
scans ...\$oem$\$1 looking for directories containing .inf files, and
then lets you select from a menu which ones to add to
OemPnPDriversPath.

So when I want to add a new driver to my build, I just copy the
directory to $oem$\$1\drivers and it automagically appears in the
menu.

(You can also tell my system to skip the menu and just add all of the
directories to OemPnPDriversPath. This is one of the examples on the
"advanced configuration" page.)

Cheers!

- Pat
http://unattended.sourceforge.net/
Click to expand...
 
Back
Top