Reduce XPe image size - removing network components

[Jay]

I am trying to reduce the RAM footprint on a single-use nForce2
system. There is no networking (the device's only input device is a
custom USB board), no keyboard/mouse, and no
user/authentication/security requirement as no user ever "logs on" to
the system. It simply boots and launches the application executable.

Basically I need minlogon, FAT, OpenGL, DirectSound, EWF, and NVIDIA
A/V chipset components (minus the network controller). I and
currently have a working, stable XPe build, but with a large RAM
footprint (>100MB).

After satisfying the dependencies I notice that more than half of the
included components are not in any way required by my application,
e.g. network protocol subsystems, COM, RPC, security, authentication,
encryption, etc. Through *MUCH* trial and error I have managed to
remove a few of the less pernicious components related to English
Language Support, Disk Management, User Locale, Control Panels, NLS,
along with a few obviously superfluous Primitives including Winspool,
Wmi, and Clusapi. The dependency check still complains, of course,
but the resulting image appears to work fine.

My question is: is it even possible to pull out the big stuff like COM
infastructure, lsass & ldap, marta, security accounts, wininet, etc,
and still support the minimum features I require? Or is networking,
security, etc all inextricably linked to basic required components
regardless of whether you even have a network or user accounts?

This newsgroup has provided me with a veritable TON of help thus far.
TIA for your expert suggestions regarding this topic!


Jay

 

[James Beau Cseri]

Have you made a custom shell for the application? The explorer shell tends
to bring in a lot of dependencies. Check the XPe help for creating a custom
shell. Also, search the MSDN embedded site for "image size reduction" and
there will be a lot of articles providing tips.

 

[Slobodan Brcin \(eMVP\)]

Hi Jay,

Like James said you should use your custom shell and battle to fit image on 64 MB storage.
Don't use TAP results (Use them but manually).
1. Start by using one of macro templates (minlogon).
2. Resolve all dependencies
3. Then disable auto resolve dependency option.
4. Modify nvidia inf files so you can use driver from only three files (~3-4 MB footprint impact). (For opengl there might be one or
two files more required)
5. Now add DirectSound and see what is really required.
6. Support for all pieces of nForce2 chipsets (excluding sound) should not exceed 1 MB.

Anyhow start by building the smallest image possible and then add required pieces.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Do have an opinion on the effectiveness of Microsoft Windows Mobile and Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~