Remove unnecessary components

[Guest]

Hi, All.

I want build a image for my target device which is used as a Human
Interface device. So i want remove unnecessary components such as Indexing
sevice components and any relate to Internet Explorer component for a small
footprint size as possible. I don't know how to delete it. Even though i
delete these components manually, it will automatically include when i run
Check Dependencies in TD.

Anyone can help me ?
Thanks.

 

[KM]

Tingjun,

Turn off Auto-resolve dependencies feature of TD (Options-->Dependency).

 

[Tingjun]

Hi,KM
I don't know turn off Auto-resolve dependencies whether makes the image to
be unreliable or work incorrectly. I want to know which component is
dependent with Indexing Service Component and Internet Explorer Component.

Thank you very much!

 

[KM]

Tingjun,

Not seeing your image I can hardly estimate the "damage" that may be done to your system if you remove components.

A few tips, though:

- First of all, if you turn off the Auto-resolve dependency you will be able to see (in TD Task/Error panel) what components are
trying to bring in the IE and Index Service.

- If you are working on minimizing image footprint, at some point you will likely have to turn off the auto-resolving dependencies
and leave the build with some errors in build log. Only way to prove the image works would be much testing

- If you are using SP2, the help system there allows you to see dependency tree for selected component.

- Use DependencyExplorer and ConfigurationExplorer components from XPETools package on www.xpefiles.com. Using those you can easy
explore dependency trees of XPe components.

 

[J.S.]

Interface device. So i want remove unnecessary components such as Indexing
sevice components and any relate to Internet Explorer component for a small
footprint size as possible. I don't know how to delete it. Even though i
delete these components manually, it will automatically include when i run

I think you get a small footprint by redefining what is "small". Another
way is hardly possible when your goal is an image that uses the Winlogon
service (indexing service is required here).
I made a "small" image of about 100MB compressed size on a CF by basing
on Task Manager Shell. One can substitute explorer.exe as shell
application with an own application or some other small weight desktop
manager as used in BartPE's boot cd, too. Be care of what your
including. Don't use "auto-resolve dependencies" but acknowledge every
component you're adding. Store many intermediate steps of this evolution
process so you may go back if an added component blows up your target by
requesting too much components.
This is a hard work with very less help from target designer and I
wonder if anyboldy really unterstands each component's work in the final
target. But I don't see any other way.
btw: I didn't manage to get rid of IE. There are so many dialogs and
components that require it even if you never deal with web browsing (I
don't know the reason why, eg, the whole huge html-rendering machine is
really needed to display the Add/Remove Software dialog and why this
couldn't be done with ressource saving C++-programming).