Computer Enters Standby During IR File Transfer in Windows 2000 (325031)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
This article was previously published under Q325031 SYMPTOMS While an Infrared (IR) file transfer is occurring in
Windows 2000, the receiving computer may enter Standby if the CPU utilization
is low enough. Example One or both of the following conditions exist:
- The receiving computer has a very fast CPU such as a 1 GHz
or faster CPU.
- The IR connection between the two computers is operating at
a low transfer rate such as 57,600 bps or slower.
Under these conditions, the CPU activity that is required to
continue receive the data may be very low. Because of this, the receiving
computer may enter Standby while the transfer is still occurring. The CPU
activity that is required to continue to receive data may be as low as 12
percent or less, and you can view this amount with Task Manager or System
Monitor. CAUSE On Windows 2000, the Infrared transfer utility (Irmon.dll)
does not signal the system to indicate that it is "active" while it is
receiving a file by using an IR connection. If no user input occurs and the CPU
utilization remains below a threshold of approximately 12 percent, the system
appears to be in an "idle" state. The computer then enters Standby after the
specified period of time passes. RESOLUTIONService Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported fix is now available
from Microsoft, but it is only intended to correct the problem that is
described in this article. Apply it only to computers that are experiencing
this specific problem. This fix may receive additional testing. Therefore, if
you are not severely affected by this problem, Microsoft recommends that you
wait for the next Windows 2000 service pack that contains this hotfix. To
resolve this problem immediately, contact Microsoft Product Support Services to
obtain the fix. For a complete list of Microsoft Product Support Services phone
numbers and information about support costs, visit the following Microsoft Web
site: NOTE: In special cases, charges that are ordinarily incurred for
support calls may be canceled if a Microsoft Support Professional determines
that a specific update will resolve your problem. The typical support costs
will apply to additional support questions and issues that do not qualify for
the specific update in question. The English version of
this fix has the file attributes (or later) that are listed in the following
table. The dates and times for these files are listed in coordinated universal
time (UTC). When you view the file information, it is converted to local time.
To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
----------------------------------------------------
01-Jul-2002 22:06 5.0.2195.5922 79,632 Irmon.dll
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft Windows 2000 Service Pack 4.This problem was corrected in Microsoft Windows
XP.
| Modification Type: | Minor | Last Reviewed: | 10/11/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbnetwork kbWin2kSP4fix kbbug kbenv kbfix kbWin2000preSP4Fix KB325031 |
|---|
|