The standard NT WAN Miniport places driver-specific data as well as common ISDN configuration data under its own driver key. Aside from a few NDIS values, the value names in this key are completely specific to the driver and lack conformity with other drivers. An example of an NT driver's registry key follows.
\HKLM\System\CurrentControlSet\Services\ISDNAdapter1\
BoardName = (LPSTR) "ISDNBoardName"
BoardType = (LPSTR) "ISDNBoardType"
DeviceVxDs = (LPSTR) "driver.sys"
DevLoader = (LPSTR) "*ndis"
DriverDesc = (LPSTR) "ISDN Adapter Description"
EnumPropPages = (LPSTR) "netdi.dll,EnumPropPages"
InfPath = (LPSTR) "COMPANYX.INF"
InterruptNumber = (BINARY) 04 00 00 00
IOBaseAddress = (BINARY) 02 00 00 00
NumChannels = (LPSTR) "2"
Phone1 = (LPSTR) "5551111"
Phone2 = (LPSTR) "5552222"
SPID1 = (LPSTR) "015551111000"
SPID2 = (LPSTR) "015552222000"
SwitchType = (LPSTR) "1"
Note that in the preceding example, the values (and value names) in italics may differ between drivers. Some ISDN adapters support multiple physical lines. Following is an example of a card which supports two physical ISDN lines.
\HKLM\System\CurrentControlSet\Services\ISDNAdapter2\
BoardName = (LPSTR) "ISDNBoard - 2 Lines"
BoardType = (LPSTR) "ISDNBoardType - 2 Lines"
DeviceVxDs = (LPSTR) "driver.sys"
DevLoader = (LPSTR) "*ndis"
DriverDesc = (LPSTR) "ISDN 2 Line Adapter"
EnumPropPages = (LPSTR) "netdi.dll,EnumPropPages"
InfPath = (LPSTR) "COMPANYX.INF"
IOBaseAddress = (BINARY) 04 00 00 00
Line0.NumChannels = (LPSTR) "2"
Line0.Phone1 = (LPSTR) "5551111"
Line0.Phone2 = (LPSTR) "5552222"
Line0.SPID1 = (LPSTR) "015551111000"
Line0.SPID2 = (LPSTR) "015552222000"
Line0.SwitchType = (LPSTR) "1"
Line1.NumChannels = (LPSTR) "2"
Line1.Phone1 = (LPSTR) "5553333"
Line1.Phone2 = (LPSTR) "5554444"
Line1.SPID1 = (LPSTR) "015553333000"
Line1.SPID2 = (LPSTR) "015554444000"
Line1.SwitchType = (LPSTR) "1"
NumberOfLines = (LPSTR) "2"
As in the previous example, all values in italics are specific to the driver, they may have different names or not be present in other driver layouts. In the preceding example, the driver values are in a "flat key" format, for example, all the values are contained in the root key. Currently, this is the only method supported by NDIS for drivers to use. The WAN TAPI Service Provider uses a hierarchical key layout which it will map to a flat key layout for the drivers to read. The values which are mapped to the flat layout are described in the following topic, Windows 95 Layout.