Windows ce inf file


















Ensure that the Makecab. Use the full path to call Cabwiz. Do not create a. You must use Cabwiz. Do not set the read-only attribute for. This flag can be used in combination with any of the other flags in this table.

The value field that follows can be a list of strings separated by commas. The value field that follows must be a list of numeric values separated by commas, one byte per field, and must not use the 0x hexadecimal prefix. Only the non-compatible format in the Win32 Setup. The application's creator and version. String substitutions for application and directory names.

String definitions for one or more strings. The device platform for which the application is targeted. The default installation of the application. The name and path of the disk on which the application resides. The name and path of the files in which the application resides. The names and paths of the destination directories for the application on the target device.

Default files to copy to the target device. Keys and values that the. Shortcuts that the installation application creates on the device. Replacement value. Contains the path to the target directory selected by the user during installation. It is declared in the "CEStrings" section. Contains the application name, defined in the "CEStrings" section. Warn a user if an attempt is made to skip a file after an error has occurred.

Do not allow a user to skip copying a file. Do not overwrite an existing file in the destination directory. Copy the source file to the destination directory only if the file is already in the destination directory. Do not copy files if the target file is newer. Details required :.

Cancel Submit. Linley Meslier MVP. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Only the fixed size header has a fixed file offset, all other strings and sections may be at any file offset, in any order. They are typically in the order given above. Each file offset is given in the fixed size header. The format of this header is as follows:. This is a null-terminated ASCII string that gives the name of the author or publisher of the packaged application.

If this string has more than zero bytes length according to the fixed size header, then this is a sequence of consecutive null terminated ASCII strings. The sequence always terminates with an empty string.

The total number of entries in this section is given in the fixed size header. There is no padding between string entries. The DIRS section is a list of directory paths used in the installation. There is no padding between directory entries. The format of each directory entry is as follows:. This is an abbreviation for one of the CE standard directories, as listed in Appendix B. All files in the list should be installed.

There is no padding between file entries. The format of each file entry is as follows:. There is no padding between hive entries. The format of each hive entry is as follows:. All entries in the list should be added. There is no padding between entries. The format of each entry is as follows:. Specifies another INF-writer-determined, unique file name, with the.

If any decorated CatalogFile. For more information about how to use the system-defined. Note Because the same. However, you must use this entry if you want to create platform-specific. Starting with Windows , this entry is required. Otherwise, if the directive is not included in an INF file or the value of the directive is set to zero, an application that has administrator privileges can directly modify these files. Driver files that are protected in this manner are referred to as third-party protected driver files.

To ensure the integrity of a PnP driver installation, applications should not directly modify driver files that are copied by the driver package INF file. Applications should only use the device installation mechanisms provided by Windows to update PnP drivers. Starting with Windows Vista, a driver package should set PnpLockDown to 1 to prevent an application from directly modifying driver files.

However, some existing applications that uninstall driver packages do directly delete driver files.

To maintain compatibility with these applications, the PnpLockDown directive for such driver package should be set to zero.



0コメント

  • 1000 / 1000