Windows Embedded Standard 2011: Determining Image Size

One of the big differences between Windows Embedded Standard 2011 and previous versions is, the OS must be deployed on NTFS. “This poses a challenge in estimating footprint. In Embedded Windows 7, all packages, including eCore, have footprint estimates. But these’re estimates. Actual deployed size will vary based on actual hardware used and necessary drivers, […]

One of the big differences between Windows Embedded Standard 2011 and previous versions is, the OS must be deployed on NTFS. “This poses a challenge in estimating footprint. In Embedded Windows 7, all packages, including eCore, have footprint estimates. But these’re estimates. Actual deployed size will vary based on actual hardware used and necessary drivers, and volume size. For eCore, footprint estimate is based on eCore with English Language pack and required fonts, Native Windows USB Support, Native Windows Branding, and Native Window Boot environment and Custom Shell with Command Prompt packages selected. This image's deployed to a PC with all auto mapped drivers on a 2 GB partition for x86 and 4 GB partition for AMD64 with default cluster sizes. We then measure number of free clusters remaining and convert this to available bytes and subtract this from the image size to determine estimated eCore footprint. For all other packages, footprint estimates, are based on Cab size with an additional allocation to allow for space consumed by ACLs, registry entries and other metadata,” revealed.