Select the product you need help with
Infrared data transfer may be slower in Windows XP or in Windows 2000Article ID: 823979 - View products that this article applies to. Important This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows RegistrySYMPTOMSFile transfers that are performed by using infrared
data association (IrDA) may be much
slower or unusable on notebook systems, on portable systems, or on similar systems. The file transfers involve Microsoft Windows XP or
Microsoft Windows 2000. This problem occurs when the processor
supports the C3 power saving mode of operation. Additionally, when a print job uses the IrDA port, the print job may time out and may stop printing. Or, the print job may take a very long time to finish. CAUSETypically, this problem occurs because of buffer underrun
conditions. The buffer underrun
conditions are caused by latency in the C3 power state transition. WORKAROUNDWarning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk. A registry flag is available that enables Windows 2000 C3 behavior. Important This registry flag does not work on Windows XP ACPI 2.0 systems. To set this flag, follow these steps:
An alternative workaround may be used if disabling C3 is not an acceptable option for your power management requirements. The alternative workaround should also be used if your system is ACPI 2.0, and therefore the CStateFlags key is not applicable. The alternative workaround can reduce by up to 85% how frequently you may
experience this problem between system restarts.To use the alternative workaround, follow these steps:
STATUSThis
is a known problem and is currently under investigation MORE INFORMATIONFor more information about processor performance control, see the "Windows native processor performance control" white
paper at the following Microsoft site: http://www.microsoft.com/whdc/archive/ProcPerfCtrl.mspx
(http://www.microsoft.com/whdc/archive/ProcPerfCtrl.mspx)
PropertiesArticle ID: 823979 - Last Review: March 25, 2005 - Revision: 3.4 APPLIES TO
|


Back to the top








