SparkleFlow is the acclaimed packaging solution that combines all aspects of a software packaging project into a single interface. Preparing an application migration? Need to reduce your TCO? Need to manage lots of applications? Want to setup your applications right now and not waste to much of your value time? SparkleFlow Package Management offers the complete solution for creating structure in your packaging project.
| Written by Manfred van Poorten |
|||||||||
|
Description: Windows File Protection requires an exact match between the file and the signature embedded in the catalog file. Files that reference a SFP catalog must not be listed in the BindImage table because the effect of the BindImage action on these files differs between computers. Files referenced by SFP catalogs must be in components that are permanent or installed locally. Concerns: ICE76 outputs an error if a file in the FileSFPCatalog table belongs to a component with any of the following true:
Additional information: For files specified in the BindImage table, the BindImage action shall for each file that is installed locally, link the executable to the DLL! Internally, the Windows API "BindImageEX" is called. InstallSFPCatalogFile is an action which installs a CatalogFile by Windows Millennium Edition's Windows File Protection. Rule is that the files which are included in a FSP Catalog, may not be placed in the BindImage table. ICE also gives this error if a component contains an SFP file:
Examples of possible errors: FileSFPCatalog Table:
BindImage Table:
1. File 'File1' references a SFP catalog. Therefore it cannot be in the BindImage table. This error must be solved: |
|||||||||
» Back to article overview