Missing files installing driver

  • Thread starter Thread starter Perro Flaco
  • Start date Start date
P

Perro Flaco

Hi everybody!

I've developed my Windows XP Embedded image, and something very strange
is going on. When FBA finishes, I try to install the driver for the
chipset (Intel 82852GM) but it starts to ask me about some "missing"
files, like "usbui.dll", "pci.sys" or "isapnp.sys". However, these
files ARE in the hardisk, but for some strange reason, Windows cannot
locate them.

Maybe, I forgot to include some component in my image, because when I
install this driver using Windows XP Professional, I've got no problem
at all.

Whats going on here? Any idea?

Thank you very much for your help!!!
 
Perro said:
I've developed my Windows XP Embedded image, and something very
strange is going on. When FBA finishes, I try to install the driver
for the chipset (Intel 82852GM) but it starts to ask me about some
"missing" files, like "usbui.dll", "pci.sys" or "isapnp.sys".
However, these files ARE in the hardisk, but for some strange reason,
Windows cannot locate them.
Click to expand...

This problem catches lots of people and I have not been able to
find an answer.You can browse to where the files are (usually
System32 or System32\Drivers) and the installation will continue.

I found that adding C:\Windows\System32\drivers for the path
environment variable will help with some set-up programs.

-Mike
 
Hi Perro, hi Mike


This is a known issue an there are also some answers on this NG.
:-)
Here some background:
The XP Embedded don't write the .pnf file during
installation. The .pnf file is "only" a temporary copy of the drivers .inf
file.

Due to this fact, the installer loose the installer path
and point always to the standard winroot path.

During installation, the installer will open a windows
"file not found". then, you can mannually browse to
the file location and it will work.

...but there is a way forcing XP-E to write the .png file....
:-))


Basically delete the following value:
[HKEY_LOCAL_MACHINE\SOFTWARE\M­icrosoft\Windows\CurrentVersio­n\Setup]
"MinimizeFootprint"=dword:0000­0001

or set it to 0.


This enables driver signing checking, pnf file creation and who knows what
else. It's a very global switch and I'm not sure how big the image will
become and what other XP features listen to it. Personally I'm only going
to
remove it after FBA. And that's if I can't convince the powers that be that
this is a silly idea.

There is a serious of "embedded" flags supported by OS. The
MinimizeFootprint is one of them.
It causes the OS (specifically - SetupAPI) to never call any crypto APIs,
and just assume everything is signed.
It also forces the SetupAPI to never generate PNFs.
(thanks to Ed and KM)

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Martin said:
..but there is a way forcing XP-E to write the .png file....
:-))


Basically delete the following value:
[HKEY_LOCAL_MACHINE\SOFTWARE\M­icrosoft\Windows\CurrentVersio­n\Setup]
"MinimizeFootprint"=dword:0000­0001

or set it to 0.
Click to expand...

Thanks Martin. I'll play with that today.

-Mike
 
perfect Mike

please provide me a feedback.
Thanks

--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Mike Warren said:
Martin said:
..but there is a way forcing XP-E to write the .png file....
:-))


Basically delete the following value:
[HKEY_LOCAL_MACHINE\SOFTWARE\M­icrosoft\Windows\CurrentVersio­n\Setup]
"MinimizeFootprint"=dword:0000­0001

or set it to 0.
Click to expand...

Thanks Martin. I'll play with that today.

-Mike
Click to expand...
 
Hi Mike, hi Martin!

Thank you very much for your help!

I've tried your advice, but without success. Now, Windows tells me that
the driver is unsigned (before changing the registry, it didn't ask me
anything), but it keep asking me about some "mising" files. Nothing has
changed after deleting what you told me in the registry.

Any suggestion?
 
Hi Perro

Why don't you include the driver into your image in
TargetDesigner before building?

I have uploaded a componized version for the Intel Graphics
Chipsets on www.xpefiles.com some month ago.
See under "Hardware/Drivers"



--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Hi Martin,
perfect Mike

please provide me a feedback.
Thanks
Click to expand...

It didn't make any difference to the problem with me either.
I did, however only set the key after FBA. If solving this small
annoyance is going to increase my image size significantly
I won't bother.

-Mike
 
Back
Top