g540 universal programmer software developer

Which INF directives are invalid in a universal INF file? The INF DefaultInstall Section is valid only if it has an architecture decoration, for example. The INF Manufacturer Section is valid as long as the TargetOSVersion decoration does not contain a ProductType flag or SuiteMask flag.

INF DDInstall.LogConfigOverride Section.

You can use any INF section in a universal INF file except for the following: Which INF sections are invalid in a universal INF file? If you are building a Windows Desktop Driver package, you don't have to use a universal INF file, but doing so is recommended because of the performance benefits.

To test if your INF is universal, use infverif /u.Ī Windows Driver must pass infverif /w, which tests /u as well as Driver Package Isolation.įor a list of InfVerif options, see Running InfVerif from the command line. For example, co-installer references are not valid in a universal INF file because code in an additional DLL cannot be executed on an offline system.Ī driver package with a universal INF file can be configured in advance and added to an offline system. The results of the installation do not depend on the runtime behavior of the system.

An INF file with such restricted syntax is called a universal INF file.Ī universal INF file installs predictably, with the same result each time. An INF file for non-Desktop versions of Windows must perform only additive operations that do not depend on the runtime behavior of the system. Some editions of Windows use only a subset of the driver installation methods that are available on Windows 10 Desktop.

G540 universal programmer software developer