G
Guest
Hi,
I'm experiencing the new features of FP2007 and specifically the File-Based
write filter. At runtime, I've to align a resistive touchscreen (because each
device is different aligned from each other) with an executable wich saves
his settings under the HKLM\System\CurrentControlSet\Enum etc.. So, after
aligning, I perfom the command 'fbwfmgr c: \WINNT\System32\Config\System' and
the fbwf tell to me that the system registry hive is committed to the compact
flash without error. But after reboot that registry settings are lost! If I
specify the '\WINNT\System32\Config\system' hive file like write-trought file
in the target designer, all is ok and the settings in that hive are persisted
across reboot. Please note that if I try to modify another WriteFilter
protected file (like eula.txt with the Notepad) and after I perform the
commit command to the filter, that modified file persist on the next reboot,
so the behaviour of the filter appears ok. Any suggestion or idea? Thanks.
I'm experiencing the new features of FP2007 and specifically the File-Based
write filter. At runtime, I've to align a resistive touchscreen (because each
device is different aligned from each other) with an executable wich saves
his settings under the HKLM\System\CurrentControlSet\Enum etc.. So, after
aligning, I perfom the command 'fbwfmgr c: \WINNT\System32\Config\System' and
the fbwf tell to me that the system registry hive is committed to the compact
flash without error. But after reboot that registry settings are lost! If I
specify the '\WINNT\System32\Config\system' hive file like write-trought file
in the target designer, all is ok and the settings in that hive are persisted
across reboot. Please note that if I try to modify another WriteFilter
protected file (like eula.txt with the Notepad) and after I perform the
commit command to the filter, that modified file persist on the next reboot,
so the behaviour of the filter appears ok. Any suggestion or idea? Thanks.