Kai,
Well... WFP on XPe should work the same way as on XP pro (remember, the same binaries).
AFAIK, the WFP generates the protected file list at the end of the Windows installation (analyzing some extension like .dll, ..exe,
..sys, etc. under system catalog). And there is no way to add your files to the list later.
Even WFP APIs do not have such functions.
Look here for more info:
http://msdn.microsoft.com/library/en-us/wfp/setup/windows_file_protection_start_page.asp
On XP Embedded there is no exactly the same system installation process as on XP Pro. My guess would be that it may be the First
Boot Agent (FBA) who populates (installs) the WFP list. Even more, it is probably all about the layout.inf (XPe Repository) file
where all system installed files specified to be protected by WFP.
You can perform a quick dirty test:
1. Add you own file entry there, in the layout.inf file under [SourceDisksFiles] section (the file format would be clear to you
when you see it).
2.Deploy the image with SFC enabled:
a) SFC primitive components included and
b) "SFCDisable" reg.value under Winlogon registry resources is set to "0".
3. Verify if your files are protected (delete them and they should appear again after a small timeout).
Let us know if it works.
KM
Hello,
does somebody know if it is possible to use the System File Protection (wfp,
sfc) to use for own files (DLLs etc) in the XP embedded image.
We would like to use it to ensure none of our files are damaged due to hard
disk failures.
Thanks for your help
Kai