System Memory May Run Low With WinSAT Included On A Standard 7 Runtime

Submitted by Wolfgang Unger on 1 June, 2011 - 08:08

Microsoft has published a workaround for the case that you use EWF and that WinSAT is included in your image and it consumes too much memory.

The article is about the following scenario:

You develop a Windows Embedded Standard 7 or Windows Embedded Standard 7 Service Pack 1 image for your device.
You added "Performance Monitoring" package in your answer file using Image Configuration Editor.
You added "Enhanced Write Filter with HORM" package in your answer file to protect the system (C:) volume.
You deployed your image without executing "winsat prepop".
You enabled EWF for the runtime image.

Post new comment

(If you're a human, don't change the following field)

Enter your name:

Your first name.

(If you're a human, don't change the following field)

Enter your name:

Your first name.

Subject:

Comment: *

Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
Lines and paragraphs break automatically.
Glossary terms will be automatically marked with links to their descriptions. If there are certain phrases or sections of text that should be excluded from glossary marking and linking, use the special markup, [no-glossary] ... [/no-glossary]. Additionally, these HTML elements will not be scanned: H1, H2, H3, STRONG, a, abbr, acronym, h1, h2, h3, strong.
Each email address will be obfuscated in a human readable fashion or (if JavaScript is enabled) replaced with a spamproof clickable link.

CAPTCHA

This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Additional Question: * Please enter the sum of 2 and 0:

Solve this simple math problem and enter the result. E.g. for the sum of 1 and 3, enter 4.