Kernel image problems; too large, boot from development system

[MReich]

Hello,

To determine the minimal target image size, I attempted to follow
the instruction in the MSDN Article:

Microsoft Windows XP Embedded \ Building a Kernel Baseline
Configuration

Except, the target is a second HD on the desktop, so I left the
video display drivers. After importing the TA devices.pqm file
directly into TD, I removed all non-essential components, including
all networking and communication components. All of the remining
componsnts had PNDid numbers. Also it was not clear how to find
standard PC components to replace ACPI components per Configuration
article step 6. Checking dependancies with auto resolve pulled in
many components clearly not directly supporting hardware, including
network support and even IE. After two itterations of dependency
resolution, the image size was 95472KB.

1. How can PNP be disabled; what components need to be substituted?
2. How can ACPI based components be removed?
3. How can english support be added for only one locale?
4. What components in my hardware list have networking dependancies?
5. Generally, how can TD resolve dependancies resulting in an image
that supports only the hardware?

M.Reich

 

[Slobodan Brcin]

To determine the minimal target image size, I attempted to follow

the instruction in the MSDN Article:

1. Use Minlogon Sample Macro component.
2. Resolve all dependencies.
3. Disable auto resolve dependencies.
4. Manualy add drivers for MB chipset.
5. All other dependencies resolve manualy, or don't it's up to you.

You won't have ACPI, but it's better if you do have it it's no so big.

Driver for all NVIDIA cards can be customized to 4.5 MB.
Driver for most(all) ATI cards can be customized to below 1 MB.

Everything else is up to you.


What size and functionality are you trying to achieve?

Best regards,
Slobodan