Re: Perflib bug!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


First of all, to prove the concept please load the main [big] image's software hive offline (use XP Pro machine, regedit) and check
if the key is there.
I started to think you are right. The PerfLib key must be there even offline but the 009 subkey gets created by performance counters
at run time and therefore you will unlikely be able to see it in the offline hive.
I think the original bug was that Microsoft componentized the Performance Counter Configuration with the 009 key accidentally added.
For proper performance counter configuration you wouldn't want the key pre-created.



Just for the record about footprint reductions... (might not be relevant to your issue now)
Well, 5 Mb is kernel only image (even bigger on SP2). You will have to program your app(s) using kernel APIs. Possible but hell lot
of work.

I am surprised your image is that big. Did you happen to use a template, e.g. Minlogon Macro?
Then please remove all the network related stuff. Obviously, for the purpose of that small image you won't need that.

Also, did you include your hardware related stuff (e.g., the platform macro you got from importing TAP result)? Then it would bring
over too much stuff you might not need.

Check and delete everything you don't need in that image. From Audio support to video drivers (you only need VGA boot and VGA safe).
Network, and especially Firewall stuff on SP2, would bring lots of other components.
Anything GUI related that is not for CMD support. E.g., some control panel applets and etc. that're brought in by a dependency
checker.

And of course you'd want to turn off automatic dependency checking option.

--
=========
Regards,
KM


"Per" <Per@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:BA4C8A6F-9F8A-4566-9266-D68B5C6FAA8B@xxxxxxxxxxxxxxxx
An image with Minlogon+CMD+reg.exe built for Virtual PC is 37,5MB
uncompressed and 19MB compressed. Any ideas on how to build a smaller image?
I keep hearing that the smallest footprint is 5MB, but how can you actually
build that "small" image? Why is there not an MSDN article available that
explains how to build a 5MB XP Embedded image? (if it is possible!)

Anyway, the solution to delete the key from a "small" image by loading the
registry key offlince does not work. When trying to delete the \Perflib\009
key from the "small" image the result is: "the key cannot be found". After
checking with Process Explorer to see which process is dynamically loading
this key it turns out to be a process named "smss.exe".
(Windows NT Session Manager)

So, it seems to be impossible to correct this issue on already deployed
systems(?)

Thanks.


.