REG: Entrées de cartes de carte du réseau, partie 1
IMPORTANT : Cet article est issu du système de traduction automatique mis au point par Microsoft (http://support.microsoft.com/gp/mtdetails). Un certain nombre d’articles obtenus par traduction automatique sont en effet mis à votre disposition en complément des articles traduits en langue française par des traducteurs professionnels. Cela vous permet d’avoir accès, dans votre propre langue, à l’ensemble des articles de la base de connaissances rédigés originellement en langue anglaise. Les articles traduits automatiquement ne sont pas toujours parfaits et peuvent comporter des erreurs de vocabulaire, de syntaxe ou de grammaire (probablement semblables aux erreurs que ferait une personne étrangère s’exprimant dans votre langue !). Néanmoins, mis à part ces imperfections, ces articles devraient suffire à vous orienter et à vous aider à résoudre votre problème. Microsoft s’efforce aussi continuellement de faire évoluer son système de traduction automatique.
La version anglaise de cet article est la suivante: 102999
Cet article a été archivé. Il est proposé « en l'état » et ne sera plus mis à jour.
L'article contient des entrées de Registre pour les cartes réseau, partie 1. Ces sous-groupes sont inclus :
- Sous-clé NetRules
- Entrées de sous-clé d'une liaison pour des composants réseau
Entrées de cartes de carte réseau
This section describes specific Registry entries related to network adaptercards and the drivers for network adapters. Windows NT supports networkadapter drivers under the NDIS 3.0 specification (Network Device InterfaceSpecification). The CurrentControlSet\Services subkey for a network driveror adapter card includes the standard entries found in the Servicessubkeys, with the following default values:Entry Value ValueError Control 0x1 (normal)Start 0x3 (load on demand)Type 0x1 or 0x4 (driver or adapter)The following sections describe entries in the other areas of the Registrythat contain configuration information for network adapter cards and theirdrivers, including: - NetRules subkeys under HKEY_LOCAL_MACHINE\SOFTWARE for drivers and adapters. - Linkage subkey entries under HKEY_LOCAL_MACHINE\SYSTEM for drivers and adapters, defining information about bindings for the component. - Parameter subkey entries under HKEY_LOCAL_MACHINE\SYSTEM for network card adapters, defining specific information such as the IRQ number, I/O base address, and other details. (In "Network Adapter Cards Entries, PART 2".)The information provided here is chiefly to be used for informational andtroubleshooting purposes. The settings for either the NDIS driver or thenetwork adapter card should be changed using the Network icon in ControlPanel.For information about Registry values for other network services, see theappropriate article in the "Network Services Entries" article series. ForTCP/IP entries that are specific to network adapter cards, see the articles"TCP/IP Transport Entries" Part 1 and Part 2.NetRules Subkey Entries-----------------------During network reconfiguration (that is, when you use the Network icon inControl Panel to make changes), the system reads the values stored in theNetRules subkeys for information used to bind the network components. TheRegistry path for these value entries is the following: - For adapter card drivers and network services, where the driverName subkey is the name of the network card's driver, as defined by the system:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft \driverName\CurrentVersion\NetRules - For network adapter cards, where the netcard# subkey is a number, beginning with 01 for the first network adapter:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT \CurrentVersion\NetworkCards\netcard#\NetRulesBindable REG_MULTI_SZ fromClass toClass Yes|No Yes|No valueDefines a possible binding and its constraints. For example:bindable = ndisDriver ndisAdapter non exclusive 100This example specifies that components of class "ndisDriver" can be boundto those of class "ndisAdapter." For the other fields in this example: - Non indicates that the component of class ndisDriver can accept other bindings. - Exclusive indicates that the component of class ndisAdapter cannot accept other bindings. - 100 indicates the relative importance (weight) of this binding; that is, in cases of competition, it will be discarded in favor of other bindings whose weight is greater.Because this value entry is a REG_MULTI_SZ, as many criteria for binding asnecessary can be defined by a single component.This value entry is optional, because there are a few predefined bindingrules, and binding rules defined anywhere in the system apply to allnetwork component classes.Bindform REG_SZ ObjectName Yes|No Yes|No [container|simple|streams]The ObjectName field contains the name (or name prefix) by which thecomponent is identified by the system. This value must be the same as thename in the related CurrentControlSet\Services subkey. Names for adaptersare created by the system and override the Bindform setting. The firstYes|No pair indicates whether the component is to receive bindinginformation directly in its Linkage subkey. The second Yes|No pairindicates whether the device name is supposed to appear in generatedbinding strings.The final optional value in this entry indicates how binding device namesare constructed. This value is required for software components.Class REG_MULTI_SZ NewClassName OldClassName|basic [Yes|No]Allows a component to define a new class. As many new classes as necessarycan be defined by any component.NOTE: These classes are not related to the OLE and DDE classes definedunder HKEY_LOCAL_MACHINE\SOFTWARE\Classes.Class names do not need to be defined within any particular component. Thesystem adds the new definition to its database without regard to origin.The order of Class entries is irrelevant. However, results areindeterminate if classes are referred to that are not defined anywhere inthe system.This entry is optional, because there are a few predefined classes, andclass definitions made anywhere in the system apply to all networkcomponents. Because any network component can define new classes, becareful that the names used are unique within all possible installablenetwork components. The following shows the predefined class names in thefirst release of Windows NT. This list, of course, cannot be exhaustive.Predefined Class Adapter Card Typeee16Driver Intel EtherExpress 16 LANee16Adapter adapterelnkiiAdapter; 3Com Etherlink II adapterelinkiiDriveribmtokDriver; IBM Token Ring adapteribmtokAdapterlanceDriver; DEC Lance adapterdec101Adapterlt200Driver; Daystar Digital LocalTalklt200Adapter adapterne2000Driver; Novell NE2000 adapterne2000AdapterproteonDriver; Proteon adapterp1390AdapterubDriver; ubAdapter Ungermann-Bass Ethernet NIUpc adapterwdlanDriver; SMC (WD) adaptersmcisaAdapterThe final optional value indicates whether this class is a "logical end-point" for the bindings protocol; the default value is No.Hidden REG_DWORD 0 or 1Suppresses the display of the component (adapter or network software) inthe Network dialog box in Control Panel.Usually, all networking components discovered in the Registry are displayedin the two list boxes in the Network dialog box in Control Panel. Settingthis value to 1 prevents the item from being displayed, which means itcannot be configured or removed by the user.Interface REG_MULTI_SZAllows a single component to make available more than one type ofcapability to other components in the system. The format for this value is:Interface = interfaceName upperClass "objectName" namingMethodValue MeaninginterfaceName The tokenized name of the secondary interface.upperClass The class to which the interface belongs. (LowerClass is the same as the primary interface.)objectName The Windows NT device name to becreated.namingMethod Determines how the bindings appear.Review REG_DWORD 0 or 1Indicates whether a component requests bindings review. If set to 1 (ornonzero), the system reinvokes this component's .INF file after bindingshave been changed. This allows network components to modify the bindinginformation or request additional information from administrators about thenew or altered connections.Type REG_SZ component className [lowerClass]Defines the type of the component in terms of abstract network componentclasses. If the optional lower class name is absent, the first (or upperlevel) class type name is used for both its upper and lower classes.This value is required for network software and network adapter cards.Component MeaningTypeAdapter A piece of hardwareDriver A software component associated directly with a piece of hardware.Transport A software component used by services.Service A software component providing capability directly to user applications.Basic A token used to represent a fundamental class name (that is, a class with no parent).Use REG_SZ service|driver|transport|adapter [Yes|No] [Yes|No]Defines the role played by the component. If this entry is absent, thevalue of Service is assumed. This value entry only appears for softwareitems.A hardware device is automatically assumed to be an adapter. Each networkcomponent may identify itself as a driver, transport, or service to clarifyits role. This distinction is as follows (note the lowercase for thevalues):Value Meaningdriver Exists only to support one or more adapters. If no bindings are generated (or permitted by the user) that include a particular driver, that driver is not loaded. However, no error is generated, since no "denial of service" has occurred.service Provides end-user functionality, and every attempt is made to support its operation. An EventLog entry is generated if a service is present in the system for which there is no available transport (the number of possible bindings is zero).transport Exists only to support services. Like a driver, it is not loaded unless necessary.The final two Yes|No values in this entry are optional; if present, eachmust be either Yes or No. The first value indicates whether driver groupnames are used instead of specific driver dependencies. The second valueindicates whether transport group names are used instead of specifictransport dependencies. These values cause the system to generatereferences to dependencies based upon their group names, not by theirspecific service names.For example, the LanmanServer is marked as Yes Yes; this means that itstransport and driver dependencies are at the group level; so LanmanServerwill be loaded if any one of its transport dependencies and any one of itsdriver dependencies successfully load.The RawRules entry appears under the following Registry path:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NCPA\CurrentVersionRawRules REG_MULTI_SZ (rule 1 data) (rule 2 data) ...Contains the rules for the binding algorithm, and consequently allowsdirect interaction with the bindings inference engine through unrestrictedrule addition. The system simply combines all RawRules with the generatedconfiguration rule set before running the inference engine.IMPORTANT: The RawRules value entry is not directly supported, and shouldbe avoided unless absolutely necessary.Under this same Registry path for NCPA, a volatile subkey appears namedConfigChanged whenever the network configuration is changed. This allowsthe system to change the Cancel button to Close in the Network dialog boxunder Control Panel. It also causes the system to prompt the user torestart the system each time the Network icon is chosen before a systemrestart has occurred.Linkage Subkey Entries for Network Components---------------------------------------------Each network component that the system determines to be required can begiven bindings, which establish the relationships between network softwarecomponents, as described in "Bindings for Network Components" in the"Windows NT Resource Kit," Chapter 11, "Overview of the Windows NTRegistry." All bindings are created by the system and should not be changedby the user, except by choosing the Bindings button in the Network dialogbox in Control Panel.Whether the bindings actually appear in the Registrydepends upon the Bindform value for the component in itsNetRules subkey.The binding information is stored in three value entries in the Linkagesubkey for a component under the Services subkey. The Registry path foreach Linkage subkey is the following:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \ServiceName\LinkageIf a binding is disabled, the settings are stored under a Disabled subkeyunder the Linkage subkey. These values are in exactly the same format asfor active bindings.For a network component, there might be more than one subkey under itsServices key: one for the driver and one for the network adapter card, plusadditional subkeys for services that might be installed with the networkadapter. Also, entries for adapter cards for AppleTalk, DLC, NWLink, andTCP/IP are described in their respective articles in the "Network ServicesEntries" article series. See Part 1 for a complete listing.Bind REG_MULTI_SZ ObjectName ObjectName ...Each string in this value entry is the name of a Windows NT object createdby the underlying software. The names are based on the object namesdeclared in the Bindform entry under the NetRules subkey.Export REG_MULTI_SZ ObjectName ObjectName ...Each string in this value entry indicates the name that should be added inthe system to allow access to the corresponding bound object. The names arebased on the object names declared in the Bindform entry under the NetRulessubkey.Route REG_MULTI_SZ "Name of service" "Name of service"...Each string in this value entry indicates the exact path through thebinding protocol represented by the binding. The names of services areused, surrounded by quotation marks.Each element of these multistring values has a one-to-one correspondencewith the others; that is, Bind is to Export and Route as Bindis to Export and Route.In addition to generating binding information, the system determines eachnetwork component's complete set of dependencies, and stores them in therelated subkey in the CurrentControlSet\Services key. For examples usingthese value entries, see "Bindings for Network Components" in the "WindowsNT Resource Kit," Chapter 11, "Overview of the Windows NT Registry."
«Kit de ressources Windows NT pour la version 3.1 du système d'exploitation».
Avertissement : Cet article a été traduit automatiquement.
ID d'article : 102999 - Dernière mise à jour : 12/04/2015 09:39:13 - Révision : 2.1
Microsoft Windows NT Advanced Server 3.1, Microsoft Windows NT Workstation 3.1, Microsoft Windows NT Advanced Server 3.1
- kbnosurvey kbarchive kbmt kbother KB102999 KbMtfr