Thanks for the response..
All the files exist in the image, either installed from a installshield
package or native to OS. The problem when it has to go back and forth from
directories, it doesn't know it's path. You have to browse for all the paths
for each file.
"steves" wrote:
> Bodean,
>
> I have seen similar problems with printer drivers but have been unable
> to solve them. (Don't despair - There are people out there that are
> much more knowledgeable than I.) It would be helpful to post
> exactly which files are missing, and maybe also what you are trying to
> install. If I understand your post correctly, the required files
> ARE already present in your image, somehow the installer just can't
> automatically locate them. Is this correct? Also, you could check C:
> \Windows\SetupAPI.log, and maybe also setupact.log and setuperr.log.
> to see if they provide any clues.
>
> If it is a Windows file that is not present in your image, (although
> doesn't sound like that's it from your description), then use the
> "Filtering" feature in target designer to create a "component contains
> file" filter to locate extra components that you might need in your
> build.
>
> Good luck
> SteveDOTSchilzATsbcglobalDOTnet
>
>
>
>
> On Sep 11, 12:29 pm, Bodean
discussions.microsoft.com> wrote:>> New to XPe and running into some install problems, post image deployment.
>> Attempting to run an msi or installshield package and it stops in the middle
>> and throws a "files needed" dialog box. If i manually type in the path to
>> i.e. windows\system32 or windows\system32\drivers it works.
>>
>> I've tried the oempnppath, sourcepath, installsourcepath and so on.
>>
>> Any help would be appricated.
