problem with new hardware (OemPnPDriversPath)

R

Raymond Geering

Hello

I ran into problems by trying to add new drivers to my distribution
folder. The whole unattended setup worked fine with my older
NIC (D-Link DFE530TX, Rev A1 -> recognized by XP) which
isn't available anymore.

So I'm now using the same NIC, but Rev C1 which isn't recognized
by Windows anymore.

So I copied the content of the CD into the folder
\i386\$oem$\drivers\dlkfet\
(sys files, hlp files, oemsetup.inf, dll files and some others)

and I added the following line in my unattend.txt

[Unattended]
DriverSigningPolicy=Ignore

OemPnPDriversPath="drivers\dlkfet;drivers\dlkfet\install;drivers\nv4_disp"

Since I made those changes, the unattend setup doesn't work as
expected - in fact it's no longer unattended (I suppose cause it doesn't
install the NIC correctly, so that it can't find the unattend.txt on the
network share anymore?).

I simply can't see an error in my configuration and I hope somebody
can help me out in this matter.

Kind regards
/Ray
 
P

Patrick J. LoPresti

Raymond Geering said:
So I copied the content of the CD into the folder
\i386\$oem$\drivers\dlkfet\

That should be:

\i386\$oem$\$1\drivers\dlkfet\

This is assuming you are doing a network-based install. If you are
making a customized CD, the path should be:

\$oem$\$1\drivers\dlkfet\

(That is, $oem$ goes parallel to the i386 directory, not within it.
But again, only for CD installs.)
(sys files, hlp files, oemsetup.inf, dll files and some others)

The .inf file is the key; it indicates the "top level" of the driver
tree. That would be my second guess for what the problem is... But
try fixing the location of the drivers first.

- Pat
 
R

Raymond Geering

Patrick J. LoPresti said:
That should be:
\i386\$oem$\$1\drivers\dlkfet\

Oh...didn't notice the $1.
This is assuming you are doing a network-based install.

Yes, it is network based.
The .inf file is the key; it indicates the "top level" of the driver
tree. That would be my second guess for what the problem is... But
try fixing the location of the drivers first.

I'll try it :) Thanks for the valuable hint - I hope it will work.

/Ray
 

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