S
s.k.easley
This was covered in an earlier thread, but no resolution was posted.
After booting up a new XPe image, when I run the Intel driver
installers they keep displaying a "Files Needed" dialog. In all cases
the files it needs is already on the system, either in
C:\Window\System32 or C:\Windows\System32\drivers.
I'm guessing that there's some bad path setting,
probably in the registry. A similar situation is in the handling of
script files. If you double click on a .js or .vbs file, and the path
to that file has spaces in it, it won't work. The problem is in the
registry, and those registry settings are different in XPe than they
are in XP Pro. Damn sloppy.
As far as creating components for these Intel drivers, I know that's
the recommended option. However, there's a bug in Compenent Designer's
..inf parser that's covered in another topic in this group. All the
Intel .inf files seem to run into this bug. It's possible to edit the
..inf to get around it, but I figured it would just be easier to use the
installers. It would be, except that XPe also has this bug with
finding files and all of the Intel driver installers run it.
With these seemingly endless XPe bugs, MS really should be calling
these XPe tools "beta" (maybe even 'alpha').
After booting up a new XPe image, when I run the Intel driver
installers they keep displaying a "Files Needed" dialog. In all cases
the files it needs is already on the system, either in
C:\Window\System32 or C:\Windows\System32\drivers.
I'm guessing that there's some bad path setting,
probably in the registry. A similar situation is in the handling of
script files. If you double click on a .js or .vbs file, and the path
to that file has spaces in it, it won't work. The problem is in the
registry, and those registry settings are different in XPe than they
are in XP Pro. Damn sloppy.
As far as creating components for these Intel drivers, I know that's
the recommended option. However, there's a bug in Compenent Designer's
..inf parser that's covered in another topic in this group. All the
Intel .inf files seem to run into this bug. It's possible to edit the
..inf to get around it, but I figured it would just be easier to use the
installers. It would be, except that XPe also has this bug with
finding files and all of the Intel driver installers run it.
With these seemingly endless XPe bugs, MS really should be calling
these XPe tools "beta" (maybe even 'alpha').