Embedded Enabling Features MODULE 4. mpcdata delivering software innovation

Transcription

1 Embedded Enabling Features MODULE 4

2 Headless A System without Display, Keyboard, Mouse Headless must be supported by system BIOS Replace user input/output with another input/output method LCD Touchscreen system and may create message boxes Windows Embedded Standard solu;on Message Box Default Reply Package Dialog Box Filter Package

3 Message Box Default Reply Intercept message boxes only Provided by a modified User32.dll Acknowledges message box Selec;on of default reply Re- direct to Event Log

4 Message Box Default Reply Intercept message boxes only Provided by a modified User32.dll Acknowledges message box Selec;on of default reply Re- direct to Event Log

5 Message Box Default Reply Controlled via Message Box Default Reply Package semngs SeMngs allow you to set the severity level to be logged Log all events Log events with the dwstyle parameter defined Log only errors, warnings, ques;ons, and informa;on Log only errors, warnings, and ques;ons Log only errors and warnings Log only errors

6 Dialog Box Filter Runs as a service on the target planorm. Prevents Windows or Dialogs from appearing. Iden@fies windows or dialogs using The process name The window ;tle The window class The bunons that are present in the window Ensures that suppressed windows are drawn off- screen. Sends a defined buvon press to a suppressed window.

7 Dialog Box Filter are undertaken in the context of the logged on user. Configured using the Dialog Filter Editor Creates an editable XML file for the service to use Wild- card defini;ons are possible not if used On an applica;on that has elevated access privileges over the current logged in user Where special (e.g. split) bunons are present On non- standard window types (e.g. Magnifier)

8 Enhanced Write Filter (EWF) Enhanced Write Filter (EWF) Protects en;re disk par;;on Enables fast boot scenario using HORM Not necessary to re- develop applica;ons Does not support boo;ng from read- only media EWF API allows control of the Enhanced Write Filter Turn EWF On/Off Commit changes

9 Enhanced Write Filter - Overlays

10 Enhanced Write Filter - Overlay Op@ons EWF can be configured and applied to mul@ple volumes, each of which may have RAM or RAMREG Overlays. Enables stateless opera@on AYer reboot all changes lost RAM Overlay Uses hidden EWF Volume RAMREG Overlay Persists EWF informa;on in system registry

11 Enhanced Write Filter (EWF) APIs EWFMGR.EXE command line program built with the EWF APIs that controls EWF EWF APIs allow you to incorporate EWF control from within your Supports Visual C++ applica;on development EWFAPI.H and EWFAPI.LIB.NET support is possible*

12 File Based Write Filter (FBWF) FBWF protects at a file level where EWF protects the whole par@@on FBWF allows for certain files to be unprotected Selec;ve write- through Individual file commit instead of whole volume like EWF Dynamic protec;on volumes can be added and removed through FBWF manager FBWF uses RAM Overlay only no extra volume par@@on needed

13 File Based Write Filter (FBWF) There are some that FBWF does not support: Object ID in NTFS Quota Hard links Opportunis;c lock File compression and encryp;on

14 File Based Write Filter (FBWF)

15 File Based Write Filter (FBWF)

16 File Based Write Filter (FBWF) APIs FBWFMGR.EXE command line program built with the FBWF APIs that controls FBWF FBWF APIs allow you to build in FBWF control from within your Supports Visual C++ applica;on development FBWFAPI.H and FBWFAPI.LIB.NET support is possible*

17 Write Filter Overview

18 Write Filter Overview (Good Things) Allows Embedded Standard to run on systems that have no persistent data storage. Turn off for some files and directories. File Based Write Filter only Instantly commit changes to selected files. File Based Write Filter only They provide API s that you can use in your applica@ons. Command- line u@li@es are provided to manage the filters.

19 Write Filter Overview (Things To Be Aware Of) Combining the use of EWF and FBWF is difficult. They cannot be used to protect the same volume. processing overhead is required. This impacts on the performance of some types of device. They require RAM to implement. RAM overlays can use up all the available memory. RAM overlays are lost when a system is rebooted. Unless they were previously commived to the protected volume. You must commit all outstanding data in an EWF overlay. You cannot commit changes to just some files / directories. Most EWF management opera@ons only occur at

20 Registry Filter Registry Filter persists license and domain secret key in the registry using a special file / RAM file solu@on EWF and FBWF TSCAL (Terminal Services Client Access License) and Domain secret key could be lost, which can impact network access If using EWF, RAM or RAM- REG Overlay must protect OS boot par@@on Ability to add custom user keys in HKLM hive

21 Registry Filter

22 Hibernate Once Resume Many (HORM) of EWF and ACPI Reboot every ;me from the HIBERFIL.SYS Used for faster system boot EWF RAM or RAM- REG only on the boot par;;on Simple setup within ICE HORM op;on in EWF SeMngs EWFMGR and EWF API support enable / disable HORM

23 Hibernate Once Resume Many (HORM) Will require a dismount/mount solu@on for read- write volumes Loss of data if not implemented More informa;on on MSDN and product help Hiberna@on not supported when USB boo@ng. Alterna@ve - Standby could be used for faster starts if supported and power can be maintained.

24 & Answers

25 MPC Data Offices MPC Data Inc th Ave. NE, Redmond, WA, 98052, USA Phone: +1 (425) Fax: +1 (425) MPC Data Limited County Gate, County Way, Trowbridge, Wiltshire BA14 7FJ, United Kingdom Phone: +44 (0) Fax: +44 (0) Web: