Image Size...

  • Thread starter Thread starter HQuinonez
  • Start date Start date
H

HQuinonez

I have a question. When I create an image and then do the Dependancies
Check... Target Designer adds a bunch of items that are of no concern to my
projected target (such as Telephony, Sound, Video Codecs, etc.). When I
eliminate them, then run another dependancy check... they are added back in.
I can't seem to break a 200mb image. I'm working on creating an image for a
POS system that does not require Video Codecs, Sound, telephony, LDAP, or
many of the other itesm that are thrown in there. How do I create an image
with the core components only? Such as:
* Basic Computer (non APCI compliant)
* Video Driver (Via Twister)
* IDE Drivers (All sytem drivers including PCI and the like)
* Basic OS, and Exlporer Shell

Yet get that under 100mb or less? The targeted device will contain an
M-Systems iDOC chip of 512mb. The chip will contain only the OS, the
application (which is around 100mb) and the database for the application's
transactions... which I'm told is merely a text file and should not exceed
25mb before being off-loaded from that POS terminal. Any and all
suggestions are greatly appreciated.

Hector Q.
SAI Systsems International
Lab Tech.
hquinonez at saisystems dot com
 
Hector,

You will need to turn off "Auto Resolve Dependencies" option in TD.
I have a question. When I create an image and then do the Dependancies
Check... Target Designer adds a bunch of items that are of no concern to my
projected target (such as Telephony, Sound, Video Codecs, etc.). When I
eliminate them, then run another dependancy check... they are added back in.
I can't seem to break a 200mb image. I'm working on creating an image for a
POS system that does not require Video Codecs, Sound, telephony, LDAP, or
many of the other itesm that are thrown in there. How do I create an image
with the core components only? Such as:
* Basic Computer (non APCI compliant)
Click to expand...

"Standard PC"
* Video Driver (Via Twister)
Click to expand...

Add the video driver component :-)
* IDE Drivers (All sytem drivers including PCI and the like)
Click to expand...

TAP will pick up those for you.
* Basic OS, and Exlporer Shell
Click to expand...

Add "Runtime Quick Start Helper Macro" component and resolve its dependenceis.
Yet get that under 100mb or less?
Click to expand...

You may not since you need Explorer Shell which is heavy.
The targeted device will contain an
M-Systems iDOC chip of 512mb. The chip will contain only the OS, the
application (which is around 100mb) and the database for the application's
transactions... which I'm told is merely a text file and should not exceed
25mb before being off-loaded from that POS terminal. Any and all
suggestions are greatly appreciated.
Click to expand...

There is "Retail Point Of Sale Terminal" (SP2 only) macro template component for you to start with.
 
Thanks again! I will turn off the Auto Resolve and work on setting this POS
machine again.
 
Hector,

You have an alternative solution.

Use TAP results only for consulting purposes do not add its result to your
image.

To empty project add one of following components: "Minlogon Sample Macro" or
"Winlogon Sample Macro". Resolve all dependencies and you should get
working XPe image with acceptable size for you.
Add your video driver component, and GART component (agp driver) if
required.

Regards,
Slobodan
 
Back
Top