The files on the support disk are meant to be installed by the NDISWAN.INF. A properly written INF for the adapter will bind it automatically to the NDISWAN protocol as well as trigger the NDISWAN.INF install itself.
In the sample INF file, isdntest.inf, there are several sections that should be included in an INF for a miniport driver. The [BoardName.ndi] section includes a CopyFiles line for the [BoardName.inf.CopyFiles] section. This section will copy the NDISWAN.INF file as well as the INF for the adapter into the Windows\Inf directory and rebuild the driver database file. This is necessary so the Network Control Panel will be able to locate the NDISWAN protocol and automatically bind it to the miniport driver.
Under the [BoardName.ndi.reg] section, there is a Required Components subsection which all miniport drivers using NDISWAN should have. These lines will ensure that a miniport driver is not installed without the NDISWAN support protocol. In the Interfaces subsection, WAN Miniports which need the WAN Wrapper services should specify ndiswan as the DefUpper interface and the range should only include ndiswan. These WAN Miniport drivers should not include a ndis3, ndis2, or odi value which would let them bind to upper layer protocols directly.
The NDISWAN.INF currently adds the WAN SP if there is only one installed TAPI SP. If more than one SP is installed, you will need to manually add the WAN SP using the Telephony Control Panel. This will removed in the future when the install wizard is introduced.