PE又一技术难题，提供共同研究。

lxl1638

今天又看了一下以前从911CD拉下来的FBWF插件，发现似乎可以对其它卷或路径开启FBWF，
看红字部分：

; fbwf.inf
; PE Builder v3 plug-in INF file for File-based write filter
; Created by SCP
; Modified by d4vr0s 2005-12-30
; Only Slightly Modified by frodo 2006-8-4

[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="File-based write filter"
Enable=1

[SourceDisksFiles]
; Im using the fltmgr files from XP SP2, instead of the ones from Vista, and
; these work 100%, unlike Vista's which either randomly give "the file fltmgr.sys is
; corrupted" errors or blue screens completely.
fltmgr.inf=20
fltmgr.sys=4
fltlib.dll=2
files\system32\*.*=2,,1
files\system32\drivers\*.*=4,,1
%11%\emptyregdb.dat=2; Required for XPE
[SetupReg.AddReg]
0x4,"ControlSet001\Services\FBWF","Start",0x0
0x4,"ControlSet001\Services\FBWF","Type",0x2
0x4,"ControlSet001\Services\FBWF","ErrorControl",0x1
0x2,"ControlSet001\Services\fbwf","ImagePath","system32\DRIVERS\fbwf.sys"
0x1,"ControlSet001\Services\FBWF","Group","FSFilter System Recovery"
0x1,"ControlSet001\Services\FBWF","DisplayName","File-Based Write Filter"
0x1,"ControlSet001\Services\FBWF","Description","File-Based Write Filter driver"
0x7,"ControlSet001\Services\FBWF","DependOnService","FltMgr"
0x4,"ControlSet001\Services\FBWF","DebugFlags", 0x0
;Only here for completeness - doesnt seem to be needed
;0x4,"ControlSet001\Services\FBWF","EnabledOnAllSkus", 0x1
;Not changeable
0x1,"ControlSet001\Services\FBWF\Instances","DefaultInstance","Fbwf Instance"
0x4,"ControlSet001\Services\FBWF\Instances\Fbwf Instance","Flags", 0x0
;Altitude never changes, so no point messing with it.
0x1,"ControlSet001\Services\FBWF\Instances\Fbwf Instance","Altitude","226000"

:SIZING
;======
;
; 8Mb - This is apparently not possible, the XPe documentation
;     says FBWF sizes are from 16Mb - 1024Mb only.
;       Trying to force it with Target Designer reverts it to 16Mb.
;    To be honest i didnt bother fiddling this low in real world testing.
:
; Valid sizes are:
;
; 0x10 = 16Mb
; 0x18 = 24Mb
; 0x20 = 32Mb
; 0x30 = 48Mb
; 0x40 = 64Mb
; 0x48 = 72Mb
; 0x60 = 96Mb
; 0x80 = 128Mb
; 0x100 = 256Mb
;
; The following line sets the cachesize to 64Mb, theoretically
; you could leave this out and it will still do 64Mb, but
; in my testing, it would revert to 32Mb, not the 64Mb
; according to the documentation.
0x4,"ControlSet001\Services\FBWF","WinPECacheThreshold", 0x40

;CACHING
;=======
;
; "Apparently" you can either Pre-Allocate the cache to full size,
; say 64Mb and it starts off at 64Mb, or you can set it to grow
; dynamically, where it dynamically increases. You can also try
; the dynamically compressed setting, but this may come with a
; performance hit, meaning file access will be slower, but this
; setting is better for lower RAM systems.
;
; 0x1 = "dynamic"
; 0x2 = "dynamic compressed"
; 0x3 = "pre-allocated"
;
; This is with "pre-allocated" caching on.
; i dont know if its the best option, yet.
; I tested all 3 and found no real difference in usability.
0x4,"ControlSet001\Services\FBWF","CacheType", 0x3

; PROTECTION
;==========
;
; Set protection for drives/paths.
; You should set this as ProtectionX,<drive:>,<\Path>
; Any path specified will not allow commits.
;
; By default the systemdrive is automatically protected.
;
; This is just an example....
;
;0x7,"ControlSet001\Services\FBWF\Exclusion", "protection1","C:","\windows"

;FltMgr Stuff
;--------------------------------------------------------------------------------------
0x4,"ControlSet001\Services\FltMgr","Type",0x2
0x4,"ControlSet001\Services\FltMgr","Start",0x3
0x4,"ControlSet001\Services\FltMgr","ErrorControl",0x1
0x2,"ControlSet001\Services\FltMgr","ImagePath","system32\DRIVERS\fltMgr.sys"
0x1,"ControlSet001\Services\FltMgr","DisplayName","FltMgr"
0x1,"ControlSet001\Services\FltMgr","Description","File System Filter Manager Driver"
0x4,"ControlSet001\Services\FltMgr","AttachWhenLoaded",0x0
;--------------------------------------------------------------------------------------
0x4,"ControlSet001\Enum\Root\LEGACY_FLTMGR","NextInstance",0x1
0x1,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","Service","FltMgr"
0x4,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","Legacy",0x1
0x4,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","ConfigFlags",0x0
0x1,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","Class","LegacyDriver"
0x1,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","ClassGUID","{8ECC055D-047F-11D1-A537-0000F8753ED1}"
0x1,"ControlSet001\Enum\Root\LEGACY_FLTMGR\0000","DeviceDesc","FltMgr"

[AddLine]
"txtsetup.sif","BusExtenders.Load",     "fbwf     = fbwf.sys"
"txtsetup.sif","BusExtenders.Load",     "fltmgr   = fltmgr.sys"
"txtsetup.sif","files.fbwf",     "fbwf.sys,4"
"txtsetup.sif","files.fbwf",     "fbwflib.dll,2"
"txtsetup.sif","files.fbwf",     "fbwfdll.dll,2"
"txtsetup.sif","files.fltmgr",   "fltmgr.sys,4"
"txtsetup.sif","files.fltmgr",   "fltlib.dll,2"

但本人简单用如下的试验，
0x7,"ControlSet001\Services\FBWF\Exclusion","Protection1","B:","\Programs"
发现不功成。定制过Embedded朋友可能对FBWF有较多的了解，在这里能否提供一些信息和技术指导？

[ 本帖最后由 lxl1638 于 2007-9-19 12:18 PM 编辑 ]

lxl1638

如果曾经定制过Embedded的，可能对这一技术有了解，或者手头上有这方面的资料。

lxl1638

原帖由 无翼鸟飞翔 于 2007-9-20 12:54 PM 发表
呃。老九。从字面上看。。好像规定的是保护区域。。也就是不允许更改的区域？
比如你那样的。好像是把b盘和program文件夹定义成只读？！

; PROTECTION
;==========
;
; Set protection for drives/paths.
; You should set this as ProtectionX,<drive:>,<\Path>
; Any path specified will not allow commits.
;
; By default the systemdrive is automatically protected.
;
; This is just an example....
;
;0x7,"ControlSet001\Services\FBWF\Exclusion", "protection1","C:","\windows"

本人是这样理解的：所谓保护区域就FBWF作用的区域，FBWF起作用后，该区域的一切文件更改都是在内存进行。
蓝字部分是不是这个意思：系统驱动器(X盘)是自动默认的保护区域？

lxl1638

原帖由 uepon 于 2007-9-23 02:58 PM 发表
不知有什么实用价值。

如果能实现，可以将所有的工具挂到B盘，且能动态挂载，即可以随时UnMount一个WIM，再MOUNT别一个WIM，或者随时以增加的方式MOUNT上不同的WIM。另外也可以解决某些程序读写本身目录的问题(911的B盘是只读的，因为WIM只读，只能以只读方式挂上；当B盘能开FBWF后，即使是只读挂载，程序所处的目录也是可写的)。