W7 Exposition (1) definition

Windows 7系统各服务项介绍Adaptive brightness监视周围的光线状况来调节屏幕明暗，如果该服务被禁用，屏幕亮度将不会自动适应周围光线状况。

该服务的默认运行方式是手动，如果你没有使用触摸屏一类的智能调节屏幕亮度的设备，该功能就可以放心禁用。

Application Layer Gateway ServiceWindows XP/Vista中也有该服务，作用也差不多，是系统自带防火墙和开启ICS共享上网的依赖服务，如果装有第三方防火墙且不需要用ICS方式共享上网，完全可以禁用掉。

Application Management该服务默认的运行方式为手动，该功能主要适用于大型企业环境下的集中管理，因此家庭用户可以放心禁用该服务。

Background Intelligent Transfer Service在后台传输客户端和服务器之间的数据。

如果禁用了BITS，一些功能，如Windows Update，就无法正常运行。

该服务的默认运行方式是自动，这个服务的主要用途还是用于进行Windows Update或者自动更新，最好不要更改这个服务。

Base Filtering Engine同样为系统防火墙，VPN以及IPsec提供依赖服务，同时也是系统安全方面的服务，如果使用第三方VPN拨号软件并且不用系统的防火墙以及ICS共享上网，为了系统资源，关闭它吧，否则就别动它。

BitLocker Drive Encryption Service向用户接口提供BitLocker客户端服务并且自动对数据卷解锁。

该服务的默认运行方式是手动，如果你没有使用BitLocker设备，该功能就可以放心禁用。

Block Level Backup Engine Service估计是和备份恢复方面用的服务，无任何依赖关系，默认是手动，也从来没有看他启动过。

就放那吧，不用管了。

Bluetooth Support Service如果你没有使用蓝牙设备，该功能就可以放心禁用。

windows7下提⽰is_notVS2008 在 W INDOWS7 B ETA7000下编译出错-T HE BINARY IS NOT A VALID W INDOWS IMAGE.更新：新装的7048 X64没出现这个问题了，原因还不知道前些天装上了W INDOWS7B ETA7000X86，却发现原先的项⽬编译会出现链接错误：MT.EXE : GENERAL ERROR C101008D:F AILED TO WRITE THE UPDATED MANIFEST TO THE RESOURCE OF FILE "R ELEASE\T EST.EXE".T HE BINARY IS NOT A VALID W INDOWS IMAGE.是MT.EXE在嵌⼊MANIFEST⽂件的时候遇到错误，从⽹上找到的解决⽅案，是在链接器设置选项中，启⽤R ANDOMIZED B ASE A DDRESS ，如下图：原因：JOHN ROBBINS' BLOGS ATURDAY,J ANUARY 24,20095:48PM JROBBINST HE C ASE OF THE C ORRUPT PE B INARIESA FTER INSTALLING W INDOWS 7,I ALSO INSTALLED THE W INDOWS 7 SDK AS I WANTED TO POKE AROUND THE UPDATED HEADERS AND DOCUMENTATION FILES TO SEE WHAT WAS NEW AT A LOW LEVEL.A DDITIONALLY,I WANTED TO MAKE SURE ALL MY CODE COMPILED AGAINST THE NEW HEADERS AND LIBRARIES IN CASE SOMEONE TAKING MY NATIVE DEBUGGING CLASS TRIED IT AND RAN INTO PROBLEMS.A FTER MANY YEARS OF THE SDK TEAM COMPLETELY IGNORING V ISUAL S TUDIO, THE W INDOWS 7SDK INSTALLATION NOW LOOKS FOR V ISUAL S TUDIO AND PROPERLY INTEGRATES WITH IT (I BELIEVE THIS STARTED WITH THE V ISTA SDK).A FTER HUNDREDS OF THOUSANDS OF EMAILS OVER THE YEARS FROM PEOPLE WHO COULDN'T COMPILE CODE FROM MY BOOKS AND COLUMNS BECAUSE THEY HADN'T GONE THROUGH THE MANUAL GYRATIONS TO INTEGRATE THE LATEST SDK WITH THE DEVELOPMENT ENVIRONMENT, IT'S A HUGE HELP.A S I HAVE ALL MY BUILDS AUTOMATED,I LET RIP AND GOT A BUILD FAILURE ON A FEW RELEASE BUILDX86AND X64BINARIES.T HE FAILURE WAS LIKE THE FOLLOWING IN ALL THOSE CASES:MT.EXE : GENERAL ERROR C101008D:F AILED TO WRITE THE UPDATED MANIFEST TO THE RESOURCE OF FILE "..\..\..\..\R ELEASE\FTS IMP T EST.EXE".T HE BINARY IS NOT A VALID W INDOWS IMAGE.MT.EXE IS THE TOOL USED TO EMBED THE MANIFEST INTO YOUR BINARIES.A S I WAS RUNNING A BETA OS,I WONDERED IF THIS WAS A PROBLEM WITH ANTI-VIRUS,SO I DISABLED E T RUST AND TRIED THE BUILD AGAIN BUT STILL GOT THE SAME ERROR.A S I'M USING V ISUAL S TUDIO 2008SP1,CL.EXE AND LINK.EXE ARE DOING ALL THE MAIN WORK OF COMPILING, BUT MT.EXE COMES FROM THE SDK.S INCE THIS CODE COMPILED CORRECTLY ON MY V ISTA COMPUTER WITH THE V ISTA SDK INSTALLED,MY NEXT STEP WAS TO SEE IF THIS WAS POSSIBLY A PROBLEM WITH MT.EXE OR IF CL.EXE AND LINK.EXE WERE EXPOSING A BUG IN THE OPERATING SYSTEM DLL S THEY WERE USING.I UNINSTALLED THE W INDOWS 7 SDK,WHICH REVERTED V ISUAL S TUDIO 2008SP1TO USING THE V ISTA SDK.G IVING THE RECOMPILES A GO,I GOT THE SAME ERROR FROM MT.EXE.I VERIFIED THAT I WAS IN FACT USING THE MT.EXE FROM THE V ISTA SDK.O NE THING THAT WAS CONFUSING TO ME WAS THAT MT.EXE FROM THE VISTA SDK AND W INDOWS 7SDK BOTH REPORT THE SAME VERSION NUMBER,BUT THE BINARIES ARE DIFFERENT SIZES.L OOKING CLOSER AT WHAT BINARIES WERE GETTING CORRUPT,IT WAS ONLY FOUR OUT OF 56.EXE FILES IN MY BUILD.I NTERESTINGLY, THEY WERE ALL CONSOLE APPLICATIONS THAT WERE UNIT TESTS.F IRING UP V ISUAL S TUDIO,I CREATED THE CANONICAL TEST CONSOLE APPLICATION,H ELLO W ORLD,AND VERIFIED THAT IT COMPILED.L OOKING AT THE BUILD.HTM FILE,I SAW THAT H ELLO W ORLD HAD THE FOLLOWING IN IT:C REATING COMMAND LINE "MT.EXE @C:\J UNK\CRUFT\H ELLO W ORLD\R ELEASE\RSP00000840485968.RS P /NOLOGO"C REATING TEMPORARY FILE "C:\J UNK\CRUFT\H ELLO W ORLD\R ELEASE\BAT00000940485968.BAT " WITH CONTENTS[@ECHO M ANIFEST RESOURCE LAST UPDATED AT %TIME% ON %DATE%>.\R ELEASE\MT.DEP]F OR TWO SECONDS,I WAS A LITTLE CONFUSED ABOUT THE TEMPORARY FILE CREATION BECAUSE MY FAILING BUILDS DIDN'T HAVE THAT.W HAT THE OUTPUT TOLD ME WAS THAT THE TEMPORARY FILE INDICATING MT.EXE CREATES THE RESOURCE UPDATE TIME FILE AFTER IT RUNS SUCCESSFULLY.M Y HYPOTHESIS AT THIS POINT WAS THAT EITHER LINK.EXE WAS CREATING A CORRUPT BINARY BEFORE MT.EXE WORKED ON IT, OR IT WAS MT.EXE CORRUPTING THE BINARY ITSELF.U SING ONE OF MY PROJECTS THAT PRODUCED A CORRUPT BINARY,I COPIED OUT THE COMMAND LINES FOR CL.EXE,LINK.EXE, AND MT.EXE FROM ITS BUILD.HTM AND RAN THEM DIRECTLY FROM A BATCH FILE AT THE COMMAND LINE (PROPERLY SET UP WITH VCVARS.BAT).I WANTED TO LOOK AT WHAT WAS IN THE P ORTABLE E XECUTABLE (PE) DATA TO SEE IF ANYTHING WAS AMISS.B Y THE WAY, YOU NEED TO READ M ATT P IETREK'S DEFINITIVE "A N I N-D EPTH L OOK INTO THE W IN32 P ORTABLE E XECUTABLE F ILE F ORMAT" P ARTS 1 AND P ART 2 YOU'LL LEARN A TON ABOUT HOW W INDOWS WORKS.R UNNING DUMPBIN.EXE/HEADERS ON THE RESULTING EXE ALLOWED ME TO LOOK AT THE MAIN PORTIONS.B ECAUSE MT.EXE PUTS THE MANIFEST INTO THE RESOURCE SECTION OF THE BINARY,I PAID SPECIAL ATTENTION TO IT:SECTION HEADER#4.RSRC NAME0 VIRTUAL SIZE4000 VIRTUAL ADDRESS (00404000 TO 00403FFF)0 SIZE OF RAW DATA0 FILE POINTER TO RAW DATA0 FILE POINTER TO RELOCATION TABLE0 FILE POINTER TO LINE NUMBERS0 NUMBER OF RELOCATIONS0 NUMBER OF LINE NUMBERS40000040 FLAGSI NITIALIZED D ATAR EAD O NLYD O YOU SEE THE PROBLEM?H ERE'S A GOOD RESOURCE SECTION FOR COMPARISON:SECTION HEADER#4.RSRC NAME2B0 VIRTUAL SIZE4000 VIRTUAL ADDRESS (00404000 TO 004042AF)400 SIZE OF RAW DATA1800 FILE POINTER TO RAW DATA (00001800 TO 00001BFF)0 FILE POINTER TO RELOCATION TABLE0 FILE POINTER TO LINE NUMBERS0 NUMBER OF RELOCATIONS0 NUMBER OF LINE NUMBERS40000040 FLAGSI NITIALIZED D ATAR EAD O NLYI NTERESTING!T HERE'S A RESOURCE SECTION,BUT IT IS OBVIOUSLY CORRUPT BECAUSE SOMETHING NOT FILLING OUT THE RAW DATA INFORMATION.A S THE MANIFEST GOES IN THE RESOURCE SECTION,MT.EXE REALLY CAN'T ADD TO A SECTION WHOSE RAW DATA STARTS AT ZERO.S INCE THE APP WIZARD GENERATED PROJECT IS NOT PRODUCING CORRUPT BINARIES BUT I HAVE SEVERAL PROJECTS THAT ARE,IT'S TIME TO LOOK AT THE LINK.EXE AND MT.EXE SWITCHES TO SEE WHAT MY PROJECTS HAVE SET THAT ARE TRIPPING EITHER OF THOSE TOOLS UP.T HE EASY WAY FOR ME TO DO THAT IS LOOK AT THE .VCPROJ FILES IN THE FANTASTIC,AND FREE, S OURCE G EAR D IFF M ERGE.(I CAN'T RAVE ENOUGH ABOUT D IFF M ERGE!)D IFF M ERGE POINTED ME WRITE TO THE .VCPROJ,VCL INKER T OOL R ANDOMIZED B ASE A DDRESS ATTRIBUTE AS THE ONLY REAL DIFFERENCE BETWEEN THE FILES.I N THE APP WIZARD PROJECT, THE VALUE IS 1,FOR MY BAD PROJECT,THE VALUE IS 2.A CHECK IN THE PROJECT PROPERTIES SHOWS A VALUE OF 2MAPS TO THE LINKER SWITCH /DYNAMICBASE:NO.I N MY BAD PROJECT,I CHANGE THE VALUE TO/DYNAMICBASE AND THE PREVIOUSLY CORRUPT RELEASE BUILD BUILT AND WORKED PERFECTLY.O NCE I FIX ALL MY BROKEN PROJECTS TO USE /DYNAMICBASE INSTEAD OF /DYNAMICBASE:NO,ALL MY BUILD PROBLEMS GO AWAY.A S I MENTIONED EARLIER, THE CORRUPT BUILDS HAPPENED TO BE SEVERAL OF MY UNIT TESTS,WHICH IS WHERE YOU MIGHT SEE ITAS WELL.T HE EXACT SITUATION I WAS GETTING THE CORRUPT BINARY IS AS FOLLOWS:O N W INDOWS 7 WITH V ISUAL S TUDIO 2008SP1T HERE'S NO RESOURCE FILE IN THE BINARY.I T'S A RELEASE BUILDY OU ARE SPECIFICALLY NOT SETTING /DYNAMICBASE TO THE LINKERA FTER I SPENT THE 20MINUTES TRACKING THIS PROBLEM DOWN,I THOUGHT MAYBE I SHOULD READ THE WINDOWS 7SDK R EAD M E FILE TO SEE IF THIS WAS A KNOWN ISSUE.S ECTION 5.3.6,TITLED "P ROBLEM R UNNING MT.EXE ON W INDOWS 7B ETA," SAYS MT.EXE FAILS IF THE .EXE DOES NOT CONTAIN A RESOURCE (.RSRC) SECTION AND THE WORK AROUND IS TO ADD AN EMPTY .RC FILE TO YOUR PROJECT TO WORK AROUND THE PROBLEM.A FTER SMACKING MY FOREHEAD WONDERING IF THIS WAS THE EXACT BUG I WAS RUNNING INTO,I TOOK THE BATCH FILE WHERE I RAN ALL THE CL.EXE,LINKER.EXE,AND MT.EXE COMMANDS DIRECTLY AND REMOVED ALL THE /MANIFEST RELATED SWITCHES FROM THE LINK.EXE COMMAND LINE.I ALSO COMMENTED OUT CALL TO MT.EXE AND REBUILT.O F COURSE,WITH MT.EXE COMPLETELY OUT OF THE WAY, THE BINARY WASN'T CORRUPT.I THINK I'M SEEING A MANIFESTATION (PUN INTENDED!)OF THE BUGMENTIONED IN SECTION 5.3.6OF THE R EAD M E.A LITTLE EXPERIMENTATION COMPILING AND LINKING WITH THE BARE MINIMUM SWITCHES NECESSARY SHOWS THAT THE LINKER DEFAULTS TO /DYNAMICBASE:NO BECAUSE THE OPTIONAL HEADER DLL CHARACTERISTICS DOES NOT SHOW D YNAMIC BASE WHEN YOU DUMP THE BINARY.W HILE I THOUGHT I WAS GOING TO HAVE A NICE C ASE O F… STORY, IT TURNS OUT THAT I SHOULD HAVE READ THE W INDOWS 7SDK R EAD M E FIRST, WHICH IS ALWAYS A VERY WISE IDEA WHEN DEALING WITH BETAS.T HERE'S NOTHING LIKE REPRODUCING A KNOWN BUG.H OWEVER,I WAS ABLE TO FIND AN ADDITIONAL WORKAROUND TO THE MT.EXE BUG BY SETTING THE/DYNAMICBASE SWITCH.I N MY SITUATION THAT WAS BETTER BECAUSE IF I ADDED A .RC FILE TO ALL THE UNIT TESTS,I WAS GOING TO HAVE TO ADD THOSE FILES TO MY CODE INSTALLS AND PATCHES.F ILED UNDER: J OHN R OBBINS, D EBUGGING。

NIOS II常见编译问题解答win7下的兼容性问题cygdrive/f/altera/10.0/nios2eds/components/altera_hal/build/system_rules.mk:120:/components/altera_hal/build/gnu_rules.mk: No such file or directory/cygdrive/f/altera/10.0/nios2eds/components/altera_hal/build/system_rules.mk:124:/components/altera_hal/build/gtf_rules.mk: No such file or directorymake[1]: *** No rule to make target `/components/altera_hal/build/gtf_rules.mk'. Stop.make: *** [system_project] Error 2Build completed in 11.068 seconds解决办法：因为在win7下的权限问题.具体解决方法参考下面的方法:Under your Quartus II folder, go to bin->cygwin->bin folder, select the following files in the list below and then right-click and choose Properties. Under the Compatibility tab, check “Run this program in compatibility mode for:”and choose “Windows XP (Service Pack 2)”. Check “Run this program as an administrator”, as well.Here is the list of files that you can select to change their compatibility mode under the Quartus II->bin->cygwin->bin folder:1. Make.exe2. Sh.exe3. Echo.exe4. Cygstart.exe5. MakeInfo.exe6. Perl.exe7.Collect2.exe(undernios2eds\bin\nios2-gnutools\H-i686-pc-cygwin\libexec\gcc\nios2-elf\3.4.6)8. Nios2-elf-g++.exe (under nios2eds\bin\nios2-gnutools\ H-i686-pc-cygwin\bin)在英文网上查到的,这几个不同的exe文件在不同的bin文件夹之间,依次右击改掉属性,把允许管理员使用权限前面打上勾即可.5.如果run Niosii时经常出现到2%后N久也不动，也不报错，甚至进度条也在滚，当然没有前进了。

ISO9001:2015质量管理体系DIS版标准解读研讨会ISO/TC176/SC2/WG24/N112ISO/TC176/SC2秘书处：BSI日期： 2014年5月13日致 ISO/TC176/SC2/WG24成员关于ISO 9001的修订ISO/DIS 9001国际标准草案投票起始于：2014-07-10投票截止于：2014-10-10 ISO/DIS 9001:2014质量管理体系——要求(中译文仅供参考)二○一四年十月六日..目次前言┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄4引言┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄50.1总则┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄50.2 ISO质量管理标准┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄50.3过程方法┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄60.4“计划—实施—检查—处置”循环┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄70.5基于风险的考量┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄70.6与其它管理体系标准的相容性┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄81范围┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄92规范性引用文件┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄93术语和定义┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄94组织的背景环境┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄184.1理解组织及其背景环境┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄184.2理解相关方的需求和期望┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄184.3确定质量管理体系范围┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄194.4质量管理体系及其过程┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄195领导作用┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄195.1领导作用和承诺┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄195.2质量方针┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄205.3组织的作用、职责和权限┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄206质量管理体系的策划┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄206.1应对风险和机遇的措施┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄206.2质量目标及其实施的策划┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄216.3对变更的策划┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄217 支持┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄217.1资源┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄217.2能力┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄227.3意识┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄227.4沟通┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄227.5形成文件的信息┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄238运行┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄238.1运行的策划和控制┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄238.2产品和服务要求的确定┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄248.3产品和服务的设计与开发┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄248.4外部供应的产品和服务的控制┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄258.5产品生产和服务提供┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄268.6产品和服务的放行┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄278.7不符合的过程输出、产品和服务的控制┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄279绩效评价┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄279.1监视、测量、分析和评价┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄279.2内部审核┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄289.3管理评审┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄2810改进┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄2910.1总则┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄2910.2不符合与纠正措施┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄2910.3持续改进┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄29附录A（资料性附录）关于新结构，术语和内容的说明┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄30 附录B（资料性附录）质量管理原则┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄32附录C（资料性附录）ISO 10000质量管理标准族┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄34 参考文献┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄36前言国际标准化组织（ISO）是由各国标准化机构（ISO成员团体）组成的世界性的联合会。

高级应用程序实现第四章内容能力。

4 - 1选择数据传输。

4-17 ImageData及其布局。

4-23转移多个图像。

4-26传输压缩数据。

4-32替代用户界面。

4-35图像的灰度和颜色信息。

4-38使用吐温获得光栅图像从一个设备是相对简单的实现在第3章,“应用程序实现”。

然而,马克·吐温也允许应用程序开发人员超越简单的收购一个图像在本地(DIB或皮克特人)格式。

在本章中讨论这些更高级的主题。

Capabilities功能,并应用谈判能力的力量来源,给控制TWAIN-compliant应用程序。

在第十二章,“操作系统依赖关系”,你会看到的谈判能力,CAP_XFERCOUNT。

这种能力是在状态4协商总是如此,除非推迟谈判是同意由应用程序和源代码。

在事实上,有更多的了解能力。

能力值几个值是用来定义每个功能。

在第十章,“能力”,马克·吐温定义了一个默认值和一组允许的值为每个功能。

应用程序不能修改默认值。

然而,它能限制值提供给用户允许的值的子集和选择能力的当前值。

默认值源被打开时,每个功能的当前值设置为吐温默认值列在第十章,“功能”。

如果没有定义默认的吐温,源将为其默认选择一个值。

应用程序可以返回一个TWAIN-defined能力默认发出DG_CONTROL / DAT_CAPABILITY MSG_RESET操作。

尽管吐温定义默认值的功能,可能有不同的来源值,它将更喜欢使用作为默认,因为它将更有效。

例如,源可能通常使用0在黑白图像显示白色。

然而,默认为ICAP_PIXELFLAVOR TWPF_CHOCOLATE即0代表黑人。

尽管吐温默认TWPF_CHOCOLATE,来源的首选违约TWPF_VANILLA。

当应用程序发出一个DG_CONTROL / DAT_CAPABILITY /MSG_GETDEFAULT操作,返回信息来源对其首选的违约。

的源和应用能够更有效的转移在此基础上进行谈判信息。

XX High Level Design Specification XX 概要设计说明书Prepared byName+ID Date yyyy-mm-dd日期+姓名工号拟制yyyy-mm-dd Reviewed by Date评审人日期yyyy-mm-dd Date Approved by批准日期XXXX Co., Ltd.XXXX有限公司XX High Level Design Specification Please input confidentiality level请输入密级XX 概要设计说明书Revision Record 修订记录Page 2 , Total 16 第2页，共16页XX High Level Design Specification Please input confidentiality level请输入密级XX 概要设计说明书Catalog 目录1Introduction 简介 (6)1.1Purpose 目的 (6)Scope 1.2范围 (6)Name 软件名称 ............................................................................................................ 61.2.1 1.2.2 ...................................................................................................... 6Functions 软件功能1.2.3Applications软件应用 ................................................................................................... 62High Level Design概要设计 (6)2.1Level 0 Design Description第零层设计描述 (6)Software System Context Definition 软件系统上下文定义 .......................................... 62.1.1 2.1.27Design Considerations (Optional)设计思路(可选) .......................................................2.2Level 1 Design Description第一层设计描述 (8)Decomposition Description分解描述 ........................................................................... 82.2.1 2.2.2Dependency Description依赖性描述............................................................................ 92.2.310Interface Description接口描述....................................................................................2.3Level 2 Design Description （Optional）第二层设计描述（可选） (12)Module name (1) 模块1名称 ...................................................................................... 122.3.1 2.3.213Module name (2) 模块2名称 ......................................................................................2.4Configuration and Control （Optional）配置和控制（可选） (14)Startup 启动 ................................................................................................................ 142.4.1 2.4.2Closing 关闭 ............................................................................................................... 142.4.314 .................................................................. Creating MIB Table Item MIB表项的创建2.4.4.................................................................. Deleting MIB Table Item MIB表项的删除 .142.4.54表项的更改 ................................................................ 1Modifying MIB Table ItemMIB2.5Database （Optional）数据库（可选） (14)Entity, Attributes and their relationships 实体、属性及它们之间的关系 .................... 142.5.1 2.5.2......................................................................................... 实体关系图 .14E-R diagramPage 3 , Total 16 第3页，共16页XX High Level Design Specification Please input confidentiality level请输入密级概要设计说明书XXTable List 表目录Table1**表 ....................................................................................................... 错误！未定义书签。

Windows Embedded Standard 2011 CTP2 Lab ManualWindows Embedded Standard 2011 – CTP2 Lab ManualTable of Contents1 Preparing to Use Windows Embedded Standard 2011 ...................................................................... 5 1.1 1.2 1.3 1.4 1.5 1.6 Introduction .............................................................................................................................. 5 Related Windows 7 Documentation .......................................................................................... 5 Minimum Device Hardware Requirements ................................................................................ 5 Release Notes ........................................................................................................................... 5 Install Windows Embedded Standard 2011 Toolkit .................................................................... 6 1.5.1 1.6.1 1.6.2 1.7 1.7.1 1.7.2 2 2.1 Open Windows Embedded Standard 2011 Toolkit Help .................................................. 6 Make Your Utility Disk Bootable ..................................................................................... 7 Add Image Builder Wizard to Your Utility Disk ................................................................ 7 Create a Windows PE Utility Disk with Image Configuration Editor ................................. 8 Create a Custom Windows PE Image .............................................................................. 8 Create a Utility Drive ................................................................................................................. 7Create a Windows Preinstallation Environment Utility Drive (Optional) ..................................... 8Build Windows Embedded Standard 2011 Images ............................................................................ 9 Build a Windows Embedded Standard 2011 Image with Image Builder Wizard .......................... 9 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 2.2.7 Build a Thin Client Image with Embedded Enabling Features .......................................... 9 Build an Image with Embedded Core Only .................................................................... 11 Build a Thin Client Image with Custom Settings ............................................................ 11 Add Update Packages to a Distribution Share (Optional) .............................................. 14 Add Third-Party Software (Optional) ............................................................................ 15 Run a Custom Script (Optional) .................................................................................... 16 Add Third-Party Drivers (Optional) ............................................................................... 17 Make Your Install Fully Unattended (Optional) ............................................................. 17 Create Image Builder Wizard Disk from Answer File (optional) ..................................... 24Build a Windows Embedded Standard 2011 Image Using Image Configuration Editor ............. 113Deploy an Image ............................................................................................................................ 25 3.1 Prepare and Capture an Image for Deployment ...................................................................... 25 3.1.1 3.1.2 3.2 3.2.1 3.2.2 Sysprep the Image........................................................................................................ 25 Capture the Image Into a Windows Image (.wim) File................................................... 25 Prepare your Destination Device .................................................................................. 26 Apply an Image to Your Device’s Hard Drive ................................................................. 27Page 2Deploy an Image Using ImageX ............................................................................................... 26©2009 Microsoft. All Rights Reserved.Windows Embedded Standard 2011 – CTP2 Lab Manual3.2.3 3.3 3.3.1 3.3.2 4 4.1Shut Down the Destination Device ............................................................................... 27 Start Image Builder Wizard with your Image ................................................................ 28 Customize a Captured Image ........................................................................................ 29Deploy an Image Using Image Builder Wizard.......................................................................... 27Service an Image ............................................................................................................................ 31 Service an Image with Image Configuration Editor and DISM................................................... 31 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6 4.3 4.4 Create a Configuration Set using Image Configuration Editor........................................ 31 Install using your Configuration Set .............................................................................. 32 Test your image ........................................................................................................... 34 Mount your image ....................................................................................................... 34 Add sample packages ................................................................................................... 34 Adding a Package Using DISM ...................................................................................... 35 Unmount and Commit Changes .................................................................................... 35 Redeploy and Verify ..................................................................................................... 35 Add a Language Pack (optional).................................................................................... 35Service an Image with DISM .................................................................................................... 34Install Updates with WUSA...................................................................................................... 36 Service an Image with Package Scanner .................................................................................. 36 4.4.1 4.4.2 4.4.3 Package Enumeration................................................................................................... 37 Find Applicable Updates ............................................................................................... 37 Scavenging ................................................................................................................... 375Additional Windows Embedded Standard 2011 Labs ...................................................................... 39 5.1 Suppress OOBE ....................................................................................................................... 39 5.1.1 5.1.2 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.3 5.3.1 5.3.2 5.4 Create an Answer File .................................................................................................. 39 Using your answer file with Image Builder Wizard ........................................................ 39 Hide boot screens ........................................................................................................ 40 Use Shell Launcher ....................................................................................................... 40 Remove Windows branding ......................................................................................... 41 Replace the startup screen background image ............................................................. 41 Add Message Blockers.................................................................................................. 42 Install from Image Builder Wizard directly to UFD : ...................................................... 44 Install from Image Builder Wizard to Hard Drive, ImageX to UFD: ................................. 44Using a Custom Shell and Custom Branding............................................................................. 40Build a USB bootable Windows Embedded 2011 image ........................................................... 44Create Custom Templates for IBW .......................................................................................... 46©2009 Microsoft. All Rights Reserved. Page 3Windows Embedded Standard 2011 – CTP2 Lab Manual5.4.1 5.4.2Creating Templates ...................................................................................................... 46 Using Custom Templates in IBW ................................................................................... 46©2009 Microsoft. All Rights Reserved.Page 4Windows Embedded Standard 2011 – CTP2 Lab Manual1 Preparing to Use Windows Embedded Standard 20111.1 IntroductionWelcome to Windows Embedded Standard 2011. This lab manual is a guide to help you use and evaluate Windows Embedded Standard 2011. In addition to preparation steps, such as toolkit installation, this manual includes labs for key scenarios such as building an image, deploying an image and servicing an image. The labs are most easily followed in the order presented. You can also chose labs individually based on your interests and previous experience with Windows Embedded, but please note that several lab scenarios assume you have the output of an earlier lab scenario.1.2 Related Windows 7 DocumentationWindows Embedded Standard 2011 is based on Windows 7; therefore much of the Windows 7 documentation can be used as reference material. • Windows 7 Automated Installation Kit (Windows AIK) online documentation /downloads/details.aspx?FamilyID=f1bae135-4190-4d7c-b19319123141edaa&displaylang=en Windows 7 Technical Library on Microsoft TechNet /enus/library/dd349342.aspx Windows Developer Center for Windows 7 /enus/windows/dd433113.aspx• •1.3 Minimum Device Hardware RequirementsYou must have the following minimum hardware to be able to build a Windows Embedded Standard 2011 image on your device: • • • • • 1 GHz x86 or amd64 processor 1 GB of flash or hard drive space (4 GB recommended) 512 MB of RAM (1 GB recommended for amd64 devices) 900 MHz CPU or equivalent At least one of the following bootable media types: • • • • Bootable DVD-ROM drive Bootable USB 2.0 port and a USB Flash Drive (UFD) with 4 GB free space, or access to a local networkBIOS supporting Windows Preinstallation Environment (Windows PE) 3.0 Minimum hardware requirements, particularly RAM requirements, may be greater depending on the size and type of feature packages selected.1.4 Release NotesAlthough every attempt has been made to provide workarounds and additional usage notes for scenarios that are affected by known issues in the pre-release versions of Windows Embedded Standard 2011, we strongly recommend that you refer to the release notes provided with this release before beginning any of the labs described in this manual. ©2009 Microsoft. All Rights Reserved. Page 5Windows Embedded Standard 2011 – CTP2 Lab Manual1.5 Install Windows Embedded Standard 2011 ToolkitYou can install Windows Embedded Standard 2011 Toolkit on your development computer from a DVD or from setup files downloaded from Microsoft Connect. 1. Run Setup.exe • If you have the Windows Embedded Standard 2011 Toolkit DVD, installation should begin when you insert the DVD into the DVD drive. If it doesn’t start automatically, the Setup.exe file can be found at: <DVD Drive>:\WindowsEmbeddedStudio.msi. 2. On the Setup Type page, do one of the following: • To install the tools and distribution share to the default location, select Complete. The default locations are: • • • 3. 32-bit operating system: [System Drive]:\Program Files\Windows Embedded Standard 2011 64-bit operating system: [System Drive]:\Program Files(x86)\Windows Embedded Standard 2011To install the tools and distribution share to a different location, select Custom.Follow the instructions in the installation wizard to complete the installation process.1.5.1 Open Windows Embedded Standard 2011 Toolkit HelpThe Windows Embedded Standard 2011 Toolkit Help contains more detailed information on many of the topics and steps contained in this manual. To access the Windows Embedded Standard 2011 Toolkit Help: 1. Start Image Configuration Editor on your development computer • 2. From the Start menu, click Programs, click Windows Embedded Standard 2011, and then click Image Configuration Editor.On the toolbar, click the Help icon to launch Help.©2009 Microsoft. All Rights Reserved.Page 6Windows Embedded Standard 2011 – CTP2 Lab Manual1.6 Create a Utility DriveIf your device is able to boot from a DVD, you can use the Windows Embedded Standard 2011 DVD appropriate to your device’s architecture to install the OS image directly to your device. Otherwise you can create a bootable USB drive by using the DiskPart tool and then loading the USB Drive with Image Builder Wizard (IBW) or WindowsPreinstallation Environment (WinPE). Diskpart supports the partitioning and formatting of a USB Flash Device (UFD) as a bootable device. A USB drive with a minimum of 4 GB is recommended for a utility drive loaded with Image Builder Wizard.1.6.1 Make Your Utility Disk Bootable1. 2. Attach your USB drive to your development computer. From a Windows Vista, Windows 7 or Windows Preinstallation (Windows PE) 3.0 environment, run the DiskPart tool by typing the following at a command prompt: diskpart Note: The version of the DiskPart tool provided by Windows Vista, Windows 7 and Windows PE 2.0, 2.1 and 3.0 supports the partitioning and formatting of a UFD as a bootable device. Previous versions of the DiskPart tool, including the version provided by Windows XP, do not fully support partitioning and formatting a UFD to be bootable and should not be used. 3. Use the DiskPart tool to determine the disk number and device size to be used for the next step by typing the following at the DiskPart prompt: list disk 4. Use the DiskPart tool to partition and format the drive and make it bootable. At the DiskPart prompt, type the following, replacing <disk_number> with the disk number of the USB drive: select clean create select active format assign exit disk <disk_number> part pri part 1 fs=ntfs quickYour USB drive is now bootable.1.6.2 Add Image Builder Wizard to Your Utility DiskThe Image Builder Wizard disks provide the ability to quickly generate a new IBW disk in the event IBW has been serviced or new packages have been added to the distribution share. To generate an Image Builder Wizard Disk:©2009 Microsoft. All Rights Reserved.Page 7Windows Embedded Standard 2011 – CTP2 Lab Manual 1. Start Image Configuration Editor on your development computer • 2. 3. 4. 5. 6. From the Start menu, selectPrograms, selectWindows Embedded Standard 2011, then selectImage Configuration Editor.On the Tools menu, select Media Creation, then select Create IBW Disk Enter the desired distribution share to be copied. Select your USB drive as the target folder. Select the desired disk architecture. Click OK.1.7 Create a Windows Preinstallation Environment Utility Drive (Optional)In some instances, you may want to create a utility disk that includes the Windows Preinstallation Environment (Windows PE). Windows PE is a lightweight version of Windows used mainly for deployment. You may prefer to use Windows PE instead of Image Builder Wizard if your USB drive is smaller than 2 GB, if you have space limitations on your device or if your device requires custom drivers that you will install on a custom version of Windows PE.1.7.1 Create a Windows PE Utility Disk with Image Configuration EditorThe Windows PE Utility Disk feature of the Media Creation tool in Image Configuration Editor provides the ability to quickly generate a Windows PE disk for gathering information about your target device or for deploying an image using Image Builder Wizard. The generated disk includes TAP.exe, ImageX and Package Scanner. To generate a Windows PE utility disk: 1. 2. Create a bootable utility disk (section 1.6.1 above). Start Image Configuration Editor on your development computer • 3. 4. 5. 6. 7. From the Start menu, selectPrograms, selectWindows Embedded Standard 2011, then selectImage Configuration Editor.On the Toolsmenu, selectMedia Creation, then selectCreate PE Image. Enter a target folder on your development computer to which the binaries will be copied. Select the desired disk architecture. Click OK. Copy the contents of the ISO sub-folder from the target folder on your development computer to the root directory of your bootable utility disk.1.7.2 Create a Custom Windows PE ImageSee the topic “Create a Custom Windows PE Image” in the Windows Embedded Standard 2011 Toolkit Help for more information about creating a custom Windows PE Image and gathering other files to add to the bootable USB drive you created in section 1.6.1.©2009 Microsoft. All Rights Reserved.Page 8Windows Embedded Standard 2011 – CTP2 Lab Manual2 Build Windows Embedded Standard 2011 Images2.1 Build a Windows Embedded Standard 2011 Image with Image Builder WizardImage Builder Wizard (IBW) is a tool you can use to create, configure and install Windows Embedded Standard 2011 on your device. The wizard runs directly on your device and guides you through a set of configuration choices. After you make your selections, the wizard creates and installs Windows Embedded Standard 2011 onto the device. You can further customize the installation or you can capture it to an image file and deploy it to other devices. In this lab, you will use IBW on your device to create different Windows Embedded Standard 2011 images. You can follow the steps provided in this lab to create the following variations: • • An image that can be used for a thin client device. A “minboot” image that contains only the base packages (referred to as Embedded Core).2.1.1 Build a Thin Client Image with Embedded Enabling FeaturesTo build a thin client image using IBW: 1. Start Image Builder Wizard on your device by either: • • Start the wizard from your Windows Embedded Standard 2011 DVD, your ISO image, or the USB drive prepared in section 1.6 Boot your device into Windows PE and run setup.exe from another location (USB drive, network share, etc.). Note: Image Builder Wizard will setup and install Windows Embedded Standard 2011. It’s important to make sure you are running the wizard on your device itself and not on your development computer. 2. On the first page, select Build an Image This option starts IBW and allows you to choose packages, drivers and languages to include in your image. You can optionally start from a template. 3. 4. Accept the End User License Agreement (EULA). The Choose the way you want to build your image page allows you to start from a template or from a blank configuration. In this exercise, select the Thin Client template and click Next. Select a language, time and currency format and keyboard or input method to install on the final image. These selections are for the primary language of your image. You can add additional languages later. Click Next to continue. The Summary of Drivers and Features page shows a summary of the drivers to be installed, detected devices and feature packages in your template. Check the Modify Drivers and Modify Features checkboxes and click Next.5.6.©2009 Microsoft. All Rights Reserved.Page 9Windows Embedded Standard 2011 – CTP2 Lab Manual 7. On the Find and Select Drivers page, choose one of the following options and click Next to continue: • • The Automatically detect devices option detects the drivers on your device and attempts to find drivers for them. The Choose a PMQ option makes it possible for you to import a device list from a previously generated PMQ file. As with Windows Embedded XP, TAP.exe is used to generate this PMQ file. The Do not select additional drivers option includes only the drivers in Embedded Core. Your image will still be bootable but drivers for non-boot-critical devices may not be installed.•8.The Confirm drivers to be installed page shows drivers that will be installed as well as the devices that were detected on your computer for which we do not have drivers. Click Browse if you want to add custom drivers. Click Next to continue. On the Please select Feature Packagesto include in your image page you can add additional features to your configuration. Because you started from the Thin Client template, several packages have been preselected for you. Choose any additional packages you wish to include.9.10. Determine which type of write filters you want to use for your thin client and select the appropriate feature packages. To use File Based Write Filter (FBWF) and Registry Filter, select: • • OR To use Enhanced Write Filter (EWF), Hibernate Once Resume Many (HORM) and Registry Filter, select: • • • Embedded Enabling Features\Enhanced Write Filter with HORM Embedded Enabling Features\Registry Filter Boot Environments\Enhanced Write Filter Boot Environment Note: Although EWF can be used without HORM, using HORM requires EWF. Adding EWF in IBW (without an answer file) will configure all existing volumes to be protected in RAM-REG mode; however EWF will be disabled for all of them. 11. Click the Resolve Dependencies button. If a pop-up window asks you to choose between multiple packages, make the following selections: a. If you are installing HORM, select Embedded Windows 7 Boot Environment, otherwise select the Windows 7 Boot Environment. • • • Select Windows Embedded Standard Startup Screens. Select Windows Explorer. Select Standard Windows USB Stack. Embedded Enabling Features\File Based Write Filter (FBWF) Embedded Enabling Features\Registry Filter©2009 Microsoft. All Rights Reserved.Page 10Windows Embedded Standard 2011 – CTP2 Lab Manual b. Resolve all other dependencies, then click Done. Click Next to continue.12. The Summary of Drivers and Features page gives you a final overview of packages and drivers to be installed. If you are satisfied with your selections, click Next. 13. Select the disk or partition where you would like to install the image, then click Next to begin installation and set up of the customized Windows Embedded Standard 2011 image on your device. 14. To enable Embedded Enabling Features after installation is complete, open a command prompt on your device and run the following commands: • For FBWF and Registry Filter: fbwfmgr /enable fbwfmrg /addvolume c: • For EWF, HORM and Registry Filter: ewfmgr c: -enable ewfmgr c: -activatehorm 15. Once HORM has been activated, it should be tested: a. b. c. d. e. f. Reboot so that EWF is enabled. Start Internet Explorer Enable hibernation by typing the following at a command prompt: powercfg –h on Reboot and device should resume from hibernation. Make changes and reboot your device again Verify your device state returns to that of step d above and that the changes made in step e were not retained.2.1.2 Build an Image with Embedded Core OnlyA Windows Embedded Standard 2011 image that contains just the Embedded Core package is described as a “minboot” image. To build an Embedded Core (eCore) image using Image Builder Wizard, follow the steps in section 2.1.1 Build a Thin Client Image with Embedded Enabling Features with the following changes: 1. 2. At step 4, choose the Minimum Configuration template Complete steps 10 and 15 only if you want to enable write filters.2.2 Build a Windows Embedded Standard 2011 Image Using Image Configuration Editor2.2.1 Build a Thin Client Image with Custom Settings1. Start Image Configuration Editor on your development computer. • From the Start menu, selectPrograms, selectWindows Embedded Standard 2011, then selectImage Configuration Editor.©2009 Microsoft. All Rights Reserved.Page 11Windows Embedded Standard 2011 – CTP2 Lab Manual 2. On the File menu, select Distribution Share, then navigate to the desired distribution share. The default distribution share locations are: • On a development computer running a 32-bit operating system: • • • x86 distribution share: C:\Program Files\Windows Embedded Standard 2011\DS amd64 distribution share: C:\Program Files\Windows Embedded Standard 2011\DS64On a development computer running a 64-bit operating system: • • x86 distribution share: C:\Program Files(x86)\Windows Embedded Standard 2011\DS amd64 distribution share: C:\Program Files(x86)\Windows Embedded Standard 2011\DS643. 4.On the File menu, click New Answer File. By default, the Embedded Edition package is added to this new answer file. This is the Embedded Core package. Add Driver Packages a. On the File menu, click Import then select Import PMQ to add device drivers using a PMQ file. In the Messages pane, in the Import PMQ tab, you can review the results of mapping the devices in a PMQ file to driver packages. • • Successfully mapped devices will be listed. To view the package in the answer file that the device was mapped to, double-click the device name. The warning icons denote devices that were not mapped to driver packages. If you need support for these devices, see section 2.2.3 Note: For more information on how to generate a PMQ file, refer to the Windows Embedded Standard 2011 Help topic “How to Generate a .PMQFile Using Target Analyzer”. b. In the Distribution Share pane, under Packages/Driver, you can add additional driver packages. Double-click any driver package (leaf node in the tree) to add it to your answer file. In the Distribution Share pane, expand the Packages/FeaturePack node. Expand the Browsers/Internet Explorer 8 node, right-click on Internet Explorer 8 Browser and select Add to Answer File. Expand the Graphics and Multimedia node, right-click on Windows Media Player 12 and selectAdd to Answer File. Expand the Remote Connections node, right-click on Remote Desktop Connectionand select Add to Answer File.5.Add Feature Packages a. b. c. d.6.Determine which type of write filters you want to use for your thin client. In the Distribution Share pane, under Packages/FeaturesPack, right-click on the appropriate feature packages and select Add to Answer File. To use File Based Write Filter (FBWF) and Registry Filter, select:©2009 Microsoft. All Rights Reserved.Page 12Windows Embedded Standard 2011 – CTP2 Lab Manual • • OR To use Enhanced Write Filter (EWF), Hibernate Once Resume Many (HORM) and Registry Filter, select: • • • Embedded Enabling Features\Enhanced Write Filter with HORM Embedded Enabling Features\Registry Filter Boot Environments\Enhanced Write Filter Boot Environment Note: Although EWF can be used without HORM, using HORM requires EWF. Adding EWF in IBW (without an answer file) will configure all existing volumes to be protected in RAM-REG mode; however EWF will be disabled for all of them. 7. To add language packs, in the Distribution Share pane, expand the Packages/LanguagePack/en-US node. Right-click the English (US) Language Pack package and select Add to Answer File. Add additional language packs the same way. To change Internet Explorer 8 settings: a. b. c. d. e. f. In theAnswer File pane, click on theInternet Explorer 8 Browser package. In the Settings pane, change Filter View to “4 Specialize”. In the Settings pane, click on the Value column to update the value for each of the following settings: Set Home_Page to /embedded SetIEWelcomeMsg to false Save your answer file. Embedded Enabling Features\File Based Write Filter (FBWF) Embedded Enabling Features\Registry Filter8.You have now changed the way Internet Explorer behaves by using Image Configuration Editor’s settings UI. You can change additional settings in your answer file the same way. 9. To resolve dependencies, from the Validate menu, select Add Required Packages. a. If there are any errors listed in the Validation tab of the Messages pane that state “Dependencies of the source package are not satisfied,” double-click the error message and use the Resolve Dependencies dialogue box to satisfy all required package dependencies. • If you are asked to choose between two USB stacks, choose “Bootable Windows USB Stack” only if you are using the USB Boot Embedded Enabling Feature and enabling a USB bootable image (see section 5.3). Otherwise choose “Standard Windows USB Stack.” If you are asked to choose between two boot environment packages, choose “Enhanced Write Filter Boot Environment” if you are installing HORM with EWF. Otherwise choose “Windows Boot Environment”.•b.Warnings that state “Optional Dependencies exist for the source package” are acceptable and may be ignored. Page 13©2009 Microsoft. All Rights Reserved.。