"Files Needed" when installing drivers

[Eberhard Schefold]

We install several drivers from the motherboad manufacturer CD onto our XPE
image (yes I know, I could try to componentize these drivers, but the
effort seems smaller the other way). When installing, I get several
standard Windows "Files Needed" dialogs asking for a path e.g. for
"pciide.sys".

I have to stress that I think I have all the necessary components for the
actual drivers chosen in Target Designer, so the files like "pciide.sys"
are already where I think they should be (in the above case "Windows
\system32\drivers"). It's only that the driver setup doesn't seem to look
for them in the right place. When I use "Browse" in the dialog and give the
"drivers" directory, the setup is perfectly content and everything works
fine.

Something must be missing in our image so that the usual path isn't
searched in the first place. This is not a big deal, but over time gets
annoying.

Your hints are greatly appreciated.

 

[Eberhard Schefold]

Eberhard Schefold schrieb/wrote:

I have to stress that I think I have all the necessary components for
the actual drivers chosen in Target Designer, so the files like
"pciide.sys" are already where I think they should be (in the above
case "Windows \system32\drivers"). It's only that the driver setup
doesn't seem to look for them in the right place. When I use "Browse"
in the dialog and give the "drivers" directory, the setup is perfectly
content and everything works fine.

I'm trying to say: This doesn't happen under XP Professional. The setup
runs there without any intervention necessary.

 

[Slobodan Brcin \(eMVP\)]

I have no idea what problem you have with path to your drivers folder.
You should try using generic components for XPe boot. And make at least one
component that will copy all inf, sys, dll files to their folders. (Simple
componentization no need to import inf file in CD).

This will pay off you time on the long run.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[KM]

Eberhard,

Slobodan is right - simply copy all the files to appropriate directories and
this should do the trick.

However, if you want to know why it does not automatically look for the
drivers in the right place you may want to run the driver install along with
FileMon to see what exactly directories are getting searched and with Regmon
to see what's the path registry entry gets loaded.

KM

 

[Eberhard Schefold]

Slobodan Brcin (eMVP) schrieb/wrote:

I have no idea what problem you have with path to your drivers folder.

That's too bad, thanks anyway.

You should try using generic components for XPe boot.

Yes, I do that, otherwise Windows won't come up, understandably.

And make at
least one component that will copy all inf, sys, dll files to their
folders. (Simple componentization no need to import inf file in CD).

This will pay off you time on the long run.

Thanks for the suggestion, but I'm not sure it will pay off in my case.
When I'm doing a new image, the drivers are dated. At least I have to check
every driver. Making and maintaining a component needs more time than
inserting a CD and pressing "Install" on the master image.

 

[Eberhard Schefold]

KM schrieb/wrote:

However, if you want to know why it does not automatically look for
the drivers in the right place you may want to run the driver install
along with FileMon to see what exactly directories are getting
searched and with Regmon to see what's the path registry entry gets
loaded.

Thank you for your answer. I'm afraid I don't see the point yet, though. If
I monitor directories and the registry, which information do I get in order
to fix the problem?

 

[Slobodan Brcin \(eMVP\)]

Hi Eberhard,

You should read one long thread from few days ago regarding this and similar
issues.
http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=OSZm
tlSCEHA.1544%40TK2MSFTNGP09.phx.gbl&prev=/groups%3Fdq%3D%26num%3D25%26hl%3De
n%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group%3Dmicrosoft.public.windowsxp.emb
edded%26start%3D25

You will see that if everything is done correctly only thing you will need
to do is to copy all driver files to one folder and to import it in the DB.
Or you can copy them manually to your image. (No additional creation of
components is required)

BTW: You problem with search path is not related to missing components,
because I have very light minlogon images that work perfectly.
Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Steve]

I have experienced the same issue. I am convinced that it is a registry
setting but I can't seem to find it. Did you find a solution?