Does anyone have any suggestions on how to minimize the amount of space in
unfilled ROM holes in an OS image build ?

It seems like the packing is based on the order things are found in ce.bib
which is based on where they are in the various .bib files. If you start with
a bunch of 'small' files and then graduate up to the large file components,
it would seem like you'll end up with a fairly different OS footprint, but
there doesn't appear to be much control available or a good step to insert a
home-grown tool. If I wanted to go in a shuffle the order of entries in
ce.bib, where could I insert that ? The initial call is into makeimg.exe.

Re: Unfilled ROM holes by Sue

Sue
Tue May 16 10:33:32 CDT 2006

I don't have any suggestions for packing more efficiently, but you can run a
tool on ce.bib by making a "preromimage.bat" which will get called during
makeimg. If you're that desperate for ROM space, try compressing things?
Move modules from the MODULES section to the FILES section?

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________