Hi ,
I would suggest you not to run the bootviz install directly on the
runtime image .Could you make a component it would work fine..else you
may very well need to trackdown the resources that are being utilised
by bootviz and include the dependencies as told by KM.
I guess MS should look into having all these tools packed with the xpe
pack.It would really help the beginners save time in searching for the
same.Revisions of the tools can also be made with an effort to improve
the tracking capabilities and drilling into the system resource usage
for particular needs.
Altogether only these explicitely used tools make things going,
during the hours of componentalisation of complex drivers and
understanding of
the performance issues of the behavior and stability of the system
during wrong
adverse or unexpected scenarios.
Regards,
Kesavan ...
"KM" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> mr. plow,
>
> Do you have all the Bootvis dependencies in your image?
> E.g., "Primitive: Iphlpapi" ?
>
> Just go though the Bootvis.exe with Dependency Walker on your target or on your dev.machine (but modify "Module Search order" then).
> Don't forget to start Profiling. You may be missing some dynamic dependencies (e.g., "Primitive: Msctf").
>
> --
> KM,
> BSquare Corporation
>
> > tried to run bootvis on my xp embedded image,
> > got a dialog box with the message
> > "Failed to Create"
> >
> > anyone know what this means and how to get bootvis to run
> > on xp embedded?
|
Similar Threads
