This section summarizes device driver requirements for modems. The items in this section are requirements for all PC 98 systems.
37. Device drivers and installation meet PC 98 requirements
Required
The manufacturer does not need to supply a driver if a PC 98-compliant driver provided with the operating system can be used. If the manufacturer supplies a driver, the requirements for the device drivers and installation are defined in the “Basic PC 98” chapter in Part 2 of this guide. The basic requirements include driver support for unattended installation and Help file support if special driver parameters are used.
For information about support for controllerless and software modems under WDM, see the Windows NT 5.0 DDK. See also the related articles at http://www.microsoft.com/hwdev/pcfuture/. For information about WDM-based modem driver support under Windows NT, see the Windows NT 5.0 DDK.
For guidelines about implementing driver and installation support for modems under the Windows operating system, see the Windows MDK.
38. Driver supports Unimodem
Required
The device driver must include Unimodem support. Typically, this requires a modem INF file, developed and verified using the MDK and pretested by the modem manufacturer.
39. Applications provided with device meet Win32 requirements
Required
Any Windows-based applications provided with the device, such as fax utilities, must meet requirements for software compatibility as defined in the Win32 SDK.
As an API, the Windows Telephony API (TAPI) is the cornerstone of telephony for Windows and Windows NT. Telephony applications and service providers provided with PC 98 systems must be implemented using TAPI 2.0.
Among other enhancements, applications can request, negotiate, and renegotiate QOS parameters with the network and receive indication of QOS on inbound calls and when QOS is changed by the network. For a summary of the TAPI 2.0 architecture and a description of how to write a TAPI service provider, see http://www.microsoft.com/ntserver/communications/. For implementation information, see the Win32 SDK.