📄 rp_infdef_keywords.html
字号:
DDInstall</i> section will not install devices having device IDs that match any of
the hardware IDs or compatible IDs listed.<br>
</dd>
</DL>
<!!!>
<!!! F !!!>
<!!!>
<H3><P><BR><BR><A NAME=F> F </A></H3>
<!!!>
<!!! G !!!>
<!!!>
<H3><P><BR><BR><A NAME=G> G </A></H3>
<!!!>
<!!! H !!!>
<!!!>
<H3><P><BR><BR><A NAME=H> H </A></H3>
<!!!>
<!!! I !!!>
<!!!>
<H3><P><BR><BR><A NAME=I> I </A></H3>
<DL>
<DT><B><A NAME=KWD_Include>
Include
</A>=</B><I>filename</I><B>.</B><I>inf</I>[<B>,</B><I>filename2</I><B>.</B><I>inf</I>]...</DT>
<DD>This optional entry specifies one or more additional named INF files containing sections needed to install this device and/or driver. If this entry is specified, usually so is a <B><A HREF="#KWD_Needs">Needs</A></B> entry.
<P>For example, the system INFs for device drivers that depend on the system's kernel-streaming support specify this entry as <BR>
<B>Include= ks.inf</B>[<B>, </B>[<B>kscaptur.inf,</B>] [<B>ksfilter.inf</B>]].
</DD>
<DL>
<DT><B><P>See Also</B></DT>
<DD><B><A HREF="AC97SMPL.HTML#LP_INCLUDE_DEF" TARGET="LP_INFSRC">Include</A></B> directive in the INF.</DD>
</DL>
</DL>
<!!!>
<!!! J !!!>
<!!!>
<H3><P><BR><BR><A NAME=J> J </A></H3>
<!!!>
<!!! K !!!>
<!!!>
<H3><P><BR><BR><A NAME=K> K </A></H3>
<!!!>
<!!! L !!!>
<!!!>
<H3><P><BR><BR><A NAME=L> L </A></H3>
<DL>
<DT><A NAME=KWD_LayoutFile><B>
LayoutFile</A>=</B><I>filename</I><B>.inf</B><I> </I>[<B>,</B><I>filename</I><B>.inf</B>]...
</DT>
<DD>
Specifies one or more additional system-supplied INF files that contain layout information on the source media required for installing the software described in this INF. All system-supplied INFs specify this entry, but IHV/OEM-supplied INFs do not.
<P>INF files that are not distributed with the OS itself must omit this entry and have <A HREF="AC97SMPL.HTML#LP_SRCDSKNM_SECT" TARGET="LP_INFSRC"><B>SourceDisksNames</A></B> and <B><A HREF="AC97SMPL.HTML#LP_SRCDSKFL_SECT" TARGET="LP_INFSRC">SourceDisksFiles</A></B> sections instead. By convention, these two sections follow the <B><A HREF="AC97SMPL.HTML#LP_VER_SECT" TARGET="LP_INFSRC">Version</A></B> section.
</DL>
<!!!>
<!!! M !!!>
<!!!>
<H3><P><BR><BR><A NAME=M> M </A></H3>
<DL>
<DT><P><BR><BR><A NAME=KWD_Manufacturer><B>
[Manufacturer]
</A></B><BR> <BR></DT>
<DD><I>manufacturer</I>-<I>name</I><BR>
[<I>manufacturer</I>-<I>name</I>] ... | <BR>
<B>%</B><I><A HREF="#KWD_StringToken">strkey</A></I><B>%=</B><I><A HREF="#KWD_Models">models-section-name</A></I><BR>
[<B>%</B><I>strkey</I><B>%=</B><I>models-section-name</I>] ...<BR>
</P></DD>
<P>The <B>Manufacturer</B> section identifies the manufacturer of one or more devices that can be installed using the INF file. It also defines the [<I><A HREF="#KWD_Models"><B>Models</B></A></I>] section name for the installation of that manufacturer's devices and their driver(s). </P>
<DL>
<DT><B>Entries and values</B></DT>
<DT><P><I>manufacturer-name</I></DT>
<DD>Identifies the device(s)' manufacturer and the corresponding <I>Models</I> section elsewhere in the INF. Each such entry must uniquely identify the manufacturer within the INF file. However, an entry specified in this manner cannot be localized.</DD>
<DT><I>strkey</I></DT>
<DD>Specifies a token, unique within the INF, representing the name of a manufacturer. Each such <B>%</B><I>strkey</I><B>%</B> token must be defined in a <B>Strings</B> section of the INF file.</DD>
<DT><I><A HREF="#KWD_MOdels">models-section-name</A></I></DT>
<DD>Specifies an INF-writer-defined name for the per-manufacturer <I>Models</I> section within the INF file. This value must be unique within the INF.
</DD>
<DT><P><B>See Also</B></DT>
<DD><B><A HREF="AC97SMPL.HTML#LP_MFTR_SECT" TARGET="LP_INFSRC">[Manufacturer]</A></B> section in the INF, <B><A HREF="RP_INFDEF_MFTR.HTML">[Manufacturer]</A></B> section described.</DD>
</DL>
</DL>
<DL>
<DT><P><BR><BR><A NAME=KWD_Models><B>[<I>
Models
</I>]</B></A><BR> <BR></DT>
<DD><I>device-description</I><B> = </B><I>install-section-name</I><B>, </B><I>hw-id</I>[<B>, </B><I>compatible-id</I>...]<BR>
[<I>device-description</I><B> = </B><I>install-section-name</I><B>, </B><I>hw-id</I>[<B>, </B><I>compatible-id</I>]...] ...<BR>
</DD>
<DD><P>A per-manufacturer <I>Models</I> section identifies at least one device, references the <A HREF="#KWD_DDInstall"><B>[<I>DDInstall</I>]</B></A> section of the INF file for that device, and specifies a unique-to-the-INF hardware identifier for that device. Any entry in the per-manufacturer <I>Models</I> section also can specify one or more additional device ID(s) for model(s) compatible with the device designated by the initial HW ID and controlled by the same driver(s).</P>
<P>Each INF-writer-defined <I>models-section-name</I> must be referenced in the <B>Manufacturer</B> section of the INF file. There can be one or more entries in any per-manufacturer <I>Models</I> section, depending upon how many devices (and drivers) the INF file installs for a particular manufacturer.</P>
</DD>
<B>Entries and values</B>
<DL>
<DT><P><I><A NAME=KWD_DeviceDesc>
device-description</A></I></DT>
<DD>Identifies a device to be installed, expressed as any unique combination of explicitly visible characters or as a <A HREF="#KWD_StringToken"><B>%</B><I>strkey</I><B>%</B></A> token defined in a <A HREF="#KWD_Strings"><B>Strings</B></A> section of the INF file.</DD>
<DT><I><A NAME=KWD_InstSect>
install-section-name</A></I></DT>
<DD>Specifies an INF-writer-determined name of the <A HREF="#KWD_DDInstall"><I><B>DDInstall</B></I></A> section for the device (and compatible models of device, if any). </DD>
<DT><I><A NAME=KWD_HWID>
hw-id</A></I></DT>
<DD>Specifies a vendor-defined string that identifies a device, which the PnP Manager uses to find an INF-file match for this device. Such a hardware ID has one of the following formats:
<DL>
<DT><I>enumerator</I><B>\</B><I>enumerator-specific-device-id</I></DT>
<DD>Is the typical format for individual PnP devices reported to the PnP Manager by a single enumerator. For example, USB\VID_045E&PID_00B identifies the Microsoft HID keyboard device on a USB bus. Depending on the enumerator, such a specification can even include the device's hardware revison number as, for example, PCI\VEN_1011&DEV_002&SUBSYS_00000000&REV_02. </DD>
<DT><B>*</B><I>enumerator-specific-device-id</I></DT>
<DD>Indicates with the asterisk (<B>*</B>) that the device is supported by more than one enumerator. For example, *PNP0F01 identifies the Microsoft serial mouse, which also has a <I>compatible-id</I> specification of SERENUM\PNP0F01. </DD>
<DT><I>device-class-specific-ID</I></DT>
<DD>Is an I/O bus-specific format, as described in the hardware specification for the bus, for the hardware IDs of all peripheral devices on that type of I/O bus. </DD>
</DL>
<DD><P>Note that a single device can have more than one <I>hw-id</I> value. The PnP Manager uses each such <I>hw-id</I> value, which is usually provided by the underlying bus when it enumerates its child devices, to create a subkey for each such device in the registry .<B>.Enum</B> branch. For manually installed devices, the system's setup code uses their <I>hw-id</I> values as specified in their respective INF files to create each such registry subkey.</DD>
<DT><I>compatible-id</I></DT>
<DD>Specifies a <I>hw-id</I> value compatible with that designated by the given <I>hw-id</I>. Any number of <I>compatible-id</I> values can be specified for an entry in the <I>Models</I> section, each separated from the next by a comma (<B>,</B>). All such compatible devices and/or device models are controlled by the same driver as the device designated by the initial <I>hw-id</I>.</DD>
<DT><B><P>See Also</B></DT>
<DD><B><A HREF="AC97SMPL.HTML#LP_MODEL_SECT" TARGET="LP_INFSRC">[<I>Models</I>]</A></B> section in the INF, <B><A HREF="RP_INFDEF_MODEL.HTML">[<I>Models</I>]</A></B> section described.</DD>
</DL>
</DL>
<!!!>
<!!! N !!!>
<!!!>
<H3><P><BR><BR><A NAME=N> N </A></H3>
<DL>
<DT><B><P><A NAME=KWD_Needs>
Needs
</A>=</B><I>inf-section-name</I>[<B>,</B><I>inf-section-name</I>]...</DT>
<DD>This optional entry specifies the particular section(s) within the given INF file(s) that must be processed during the installation of this device. Typically, such a named section is a <I><B><A HREF="#KWD_DDInstall">DDInstall</A></B></I> (or <I>DDInstall</I><B>.</B><I>xxx</I>) section within one of the INF file(s) listed in an <B><A HREF="#KWD_Include">Include</A></B> entry. However, it can be any section that is referenced within such a <I>DDInstall</I> or <I>DDInstall</I><B>.</B><I>xxx</I> section of the included INF.
<P>For example, the INFs for device drivers that have the preceding <B>Include</B> entry specify this entry as <BR>
<P><B>Needs= KS.Registration</B>[<B>, KSCAPTUR.Registration</B> | <BR>
<B>KSCAPTUR.Registration.NT,</B> <B>MSPCLOCK.Installation</B>]
</DD>
<DL>
<DT><P><B>See Also</B></DT>
<DD><B><A HREF="AC97SMPL.HTML#LP_NEEDS_DEF" TARGET="LP_INFSRC">Needs</A></B> directive in the INF.</DD>
</DL>
</DL>
<!!!>
<!!! O !!!>
<!!!>
<H3><P><BR><BR><A NAME=O> O </A></H3>
<!!!>
<!!! P !!!>
<!!!>
<H3><P><BR><BR><A NAME=P> P </A></H3>
<DL>
<DT><B><A NAME=#KWD_Provider>
Provider</A>=%</B><I>INF-creator</I><B>%</B>
</DT>
<DD>Identifies the provider of the INF file. Typically, this is specified as an <B>%</B><I>OrganizationName</I><B>%</B> token that is expanded later in the INF's <B><A HREF="#KWD_Strings">Strings</A></B> section.
<P>For example, INFs supplied with the system typically specify the <I>INF-creator</I> as <B>%</B>Msft<B>%</B> and define <B>%</B>Msft<B>% = "</B>Microsoft<B>"</B> in their <B>Strings</B> sections.
</DD>
</DL>
<!!!>
<!!! Q !!!>
<!!!>
<H3><P><BR><BR><A NAME=Q> Q </A></H3>
<!!!>
<!!! R !!!>
<!!!>
<H3><P><BR><BR><A NAME=R> R </A></H3>
<DL>
<DT><A NAME=KWD_RegKeys><B>
RegKeys
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -