X hits on this document





121 / 174

Microsoft Windows Logo Program System and Device Requirements  —  121

A WDM driver-based modem should not continuously disable thread preemption for more than 4.4 milliseconds. This guideline accommodates 400 microseconds of interrupts being disabled together with two back-to-back episodes of 2.0 milliseconds of extended processing at DISPATCH_LEVEL, as up to four 500-microsecond DPCs execute sequentially. FAQ Date: October 7, 1998

B6.1.5.8 WDM modem latency tolerances [Clarifications]

Note: WDM modem latency tolerance is a recommendation. This is not tested.

A driver-based modem should be able to tolerate:

A period of 4 milliseconds with interrupts disabled.

A continuous period of 8 milliseconds during which a queued DPC is held off from execution, possibly by other DPCs.

A 16-millisecond period when thread scheduling is continuously disabled.

FAQ Date: October 7, 1998

B6.1.5.9 DELETED

Note: There is no Wake on Ring requirement for modems.  

B6.1.5.10 Analog modem correctly reports caller ID [Clarification]

FAQ incorporated at B6.

B6.1.R General Modem - Future Requirements

Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/.

B7.0 Network Devices

Requirements for network components designed for servers running Windows Datacenter Server, including LAN and wide area network (WAN) server network adapters, are not provided in this appendix, which focuses solely on components for desktop and mobile client PCs and servers running Windows Server 2003, Standard or Enterprise Edition.

B7.1 General Network

All general requirements in B1.0 are included by reference. All bus-specific requirements in B2.0 are included by reference.

B7.1.1 General Network - Windows Compatibility

B7.1.1.1 NDIS 5.0 miniport driver model: "Network Devices and Protocols" in the Windows DDK

The network adapter driver must be based on and comply with NDIS 5.0 in order to take advantage of new operating system capabilities. The driver must follow the NDIS 5.0 miniport driver model defined in the Windows DDK.

Important: The development of full media access control (MAC) drivers is no longer supported.

If the network device is for connection-oriented media, such as ATM, ISDN, frame relay, or X.25, it must have a connection-oriented miniport driver that follows the connection-oriented model defined for NDIS 5.0. Also, for connection-oriented media, there must be an NDIS 5.0 call manager driver as

© 1999-2002 Microsoft Corporation. All rights reserved.

Document info
Document views699
Page views699
Page last viewedTue Jan 24 05:41:49 UTC 2017