Network Parameters in the Registry

Network Parameters in the Registry Networking features in Windows 2000, Windows XP, and Windows Server 2003 include several improvements
Nội dung trích xuất từ tài liệu:
Network Parameters in the RegistryNetwork Parameters in the RegistryNetworking features in Windows 2000, Windows XP, and Windows Server 2003 includeseveral improvements. These improvements have also influenced the method of storingnetwork data in the registry. The main improvements introduced into the networking are:support for NDIS 5.0 (Windows 2000) and NDIS 5.1 (Windows XP and Windows Server2003), Plug and Play support, power management, and the new INF file format used forinstalling network components.Installing Network Components in the RegistryTo install networking components in Windows 2000, Windows XP and Windows Server2003, the operating system requires the following: Class installer and optional co-installer Class installer is a dynamically loaded library (DLL) that installs, configures, or deletes devices of a specified class. Networking components in Windows 2000, Windows XP, and Windows Server 2003 must be installed by a network class or by a vendor-supplied class installer. If the standard class installer doesnt provide all of the necessary functionality for an individual device, the device vendor may develop an optional coinstaller. This coinstaller is a Win32 DLL that implements all the necessary functions for the individual device. A list of existing network components is provided below: Net — this class defines network adapters. NetTrans — this class defines network protocols (such as TCP/IP and IPX) and connection-oriented network clients. NetClient — this class specifies network clients, such as Microsoft Client for Networks or NetWare Client. The NetClient component is considered a network provider. It can also be used to provide print services (in this case, its also the print provider). NetService — this class specifies network services, such as a file or print service. The network class installer defines the class of the network component to be installed by the ClassGuid value. The ClassGuid value is the Globally Unique Identifier (GUID) for the class. You can generate GUID values using the Uuidgen.exe utility. More detailed information about this utility is provided in Platform SDK supplementary documents. All standard network component classes and their respective ClassGuid values are listed in Table 8.2. Table 8.2: Network Component Classes and Their Respective ClassGuid Values Network component ClassGuid value class Net {4D36E972-E325-11CE-BFC1- 08002BE10318} NetTrans {4D36E973-E325-11CE-BFC1- 08002BE10318} NetClient {4D36E974-E325-11CE-BFC1- 08002BE10318} NetService {4D36E975-E325-11CE-BFC1- 08002BE10318}Class installer information is stored in the registry underHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class. Foreach class installer, this key contains a subkey named… No, it wont have thename youre expecting it to have. And it wont be something like Net either.Rather, it will be the ClassGuid value (Fig. 8.7). Compare this name to theClassGuid values listed in Table 8.2.Figure 8.7: The contents of theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972–E325–11CE-BFC1–08002BE10318} registry key defines the settings of theclass installer for the network adapter classOne or more INF filesINF files contain the necessary information for the class installer of the networkcomponent to install this component. A detailed description of the INF file formatis provided in the documents supplied with Windows Driver Development Kit(DDK).Optional notify objectNetwork software components, such as network protocols, services, or networkclients, may have to notify objects that allow you to display the user interface formanual configuring of the network components. For example, the UI providescapabilities for manual control over the binding process. Notice that hardwarecomponents, such as network adapters, may also provide both UI and softwarecontrol over the binding process. However, all these tasks are performed by theINF file or coinstaller, rather than by notify objects. Fig. 8.8 shows information onthe notify object that provides the capability of manually configuring the NWLinkprotocol, Migration DLL, and its associated files.Figure 8.8: Information on the notify object that configures the NWLink protocolIf the device driver isnt included with the standard Windows 2000, Windows XP,and Windows Server 2003 distribution package, then the device vendor shouldprovide the necessary support.In addition to the files listed above, the following files are needed to installnetwork components.One or more device drivers. Normally, each driver contains a driver image (theSYS file) and a driver library (DLL).The driver catalog file is optional, but highly desirable. We discussed catalog filesin Chapter 6. Here, well only note that if the device vendor needs to include adevice into the Hardware Compatibility List (HCL), its necessary to test both thedevice and its driver in the Windows Hardware Quality Lab (WHQL). If the test results are satisfactory, WHQL includes the device into the HCL and provides the catalog file (CAT file) for the driver. The CAT file contains the digital signature. The optional Txtsetup.oem file. This file contains the data needed by the Setup program that installs Windows 2000, Windows XP, and Windows Server 2003 to install the device driver during the ...