B6.1.5 General Modem - FAQs B6.1.5.1 Current Modem FAQs
See http://www.microsoft.com/winlogo/hardware/modem/.
B6.1.5.2 DELETED
Modems are not required on any system.
FAQ Date: January 31, 2001
B6.1.5.3 Unimodem required commands [Clarification]
[MOD-0368; SDG3:101]
Windows Unimodem does not use the following commands directly; therefore, these are not in the sample INF and are not required: +ICF, +MA, +EB, +ESR, +ETBM. These commands are only required if the function is controllable in the modem by way of AT commands; in that case, the standard V.250 commands defined here must be included.
FAQ Date: October 7, 1998
B6.1.5.4 Voice recording and playback capabilities [Logo Program correction]
[MOD-0374; SDG3:110]
The capability for voice recording and playback (+VTX, +VRX) is not required.
FAQ Date: July 8, 1999
B6.1.5.5 DELETED B6.1.5.6 WDM support for driver-based modems [Logo Program clarification]
[MOD-0383]
WDM support for driver-based modems is required for Windows Me and Windows XP/Windows 2000. For information about the Ccport.sys QFE for Windows 98, see http://www.microsoft.com/hwdev/devdes/modem_up.htm.
FAQ Date: July 28, 1999; revisions August 26, 1999, March 3, 2000
B6.1.5.7 Total execution time for DPCs queued by a WDM modem [Clarifications]
At any instant in time, the total execution time required for all delayed procedure calls (DPCs) that have been queued by a WDM driver-based modem, but have not dequeued and started executing, should not exceed 500 milliseconds.
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]
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.
See http://www.microsoft.com/hwdev/devdes/modem_up.htm.
FAQ Date: October 7, 1998
B6.1.5.9 Modem supports wake-up events [Clarification]
[MOD-0381, 0382; SDG3:102]
PCI modems must support power states D0 and D3. PCI devices are required to support the D3 state on a PCI 2.2-enabled system with auxiliary power. On all other power-managed buses (such as USB), support for either D2 or D3 state is acceptable. Modem drivers must accept power management IRPs.
FAQ Date: October 7, 1998; June 14, 2000
B6.1.5.10 Analog modem correctly reports caller ID [Clarification]
For hardware-based modems, see ITU-T V253 section 9.2.3.1 for details about correctly implementing caller ID reporting.
Note: Software-based modems are not required to capture caller ID while the system is either in ACPI S3 sleep state or resuming from S3 state.
FAQ Date: May 08, 2001
|
