component customization

  • Thread starter Thread starter crus
  • Start date Start date
C

crus

Components that have customizable settings need a manual configuration in
every new image. Have anybody a solution for saving customized standard
components to avoid manual setting?
Example are "Autologon" "Regional and language options" components.
Until now I make a customized image and reuse it by changing only the
hardware components, but this way needs working on the full expanded image.
Adding components from scrath seems to me a better solution, because macros
could be used to automate operations.
Regards
 
Dear curs,

How about creating templates of XPE configurations?
1. Creating empty slx file
2. Adding specified components and setting them manually
3. Creating Macro components depending on standard components

This solution takes a long time on dependency check process.

--
Best Regards,
Bing Chen
Advantech Co., Ltd.
Microsoft eMVP

¬ãµØ - ·L³n¥xÆW°Ï´O¤J¦¡§@·~¨t²Î¸g¾P°Ó
http://www.advantech.com.tw/epc/newsletter/ATW/2005MS/
 
Thank you Bing
Your advice gives a good way to do, because you have configurable components
exposed in TD and non configurable ones selectable through macros. In my
image I have 12 configurable components. But if I add languages the number
increases.
I started with this question to have advices about modify and saving custom
components similars to standard ones but with something modified .
The idea is to reuse them in new works.
It's possible to do a new component using the original one as Prototype, but
settings parameters are not seen in CD so modify it is very difficult.
Regards all
 
crus,
Thank you Bing
Your advice gives a good way to do, because you have configurable components exposed in TD and non configurable ones selectable
through macros. In my image I have 12 configurable components. But if I add languages the number increases.
I started with this question to have advices about modify and saving custom components similars to standard ones but with
something modified .
The idea is to reuse them in new works.
It's possible to do a new component using the original one as Prototype, but settings parameters are not seen in CD so modify it
is very difficult.
Click to expand...

It is possible to create a component that inherits a specific component properties but has some fields predefined and changed from
the original component.
To do that you will have to create a simple CMI script and attach it to the component. In the CMI script you will have to implement
cmiOnActivateInstance handler where you'd change the original component extended [advanced] properties to pre-set them as you wanted
to.
 
Back
Top