Compile on a Windows XP-based computer takes longer to complete than on a Windows NT-based computer (816073)


The information in this article applies to:

  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
For a Microsoft Windows Server 2003 version of this article, see 890553.
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 Description of the Microsoft Windows Registry

SYMPTOMS

When you try to compile a program on a Microsoft Windows XP-based computer, it may take approximately 30 percent to 40 percent longer to complete than it did when the same computer hardware was Microsoft Windows NT-based.

On a multihomed computer that is running Microsoft Windows XP, you may experience delays of between 10 and 60 seconds when you use Universal Naming Convention (UNC) paths to access files that are stored on a remote server message block (SMB) server. This problem occurs more frequently as your computer tries to access files more frequently. For example, the problem may occur when an application tries to access files at two-second intervals. The problem does not occur when you access the files through a mapped network drive. The problem also does not occur when NetBIOS over TCP/IP (NetBT) is disabled on at least one network interface.

CAUSE

This problem may occur if you compile a large program that has many files. Windows XP caches the files that you are compiling, and when the Windows cache limit is reached, Windows removes the files from the cache. When it does so, Windows may remove the files that are used frequently during the compilation. To use these files, you must cache them again. Recaching the files slows the compile process.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows XP service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual 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 hotfix 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
   --------------------------------------------------
15-Apr-2003 23:25 5.1.2600.1206 92,160 Cscdll.dll 
15-Apr-2003 22:59 5.1.2600.1206 401,920 Mrxsmb.sys 
15-Apr-2003 22:59 5.1.2600.1206 155,392 Rdbss.sys

WORKAROUND

To work around this problem, follow these steps:
  1. Map a network drive to the SMB server. To do this, follow these steps:
    1. Start Windows Explorer.
    2. On the Tools menu, click Map Network Drive.
    3. In the Drive list, click a drive letter.
    4. In the Folder list, type the UNC path of the shared resource on the server. Use the following format:

      \\ServerName\SharedItem

      Alternatively, click Browse, and then locate the shared resource.
    5. Click Finish.
  2. Disable NetBT on a network interface. To do this, follow these steps:
    1. Click Start, click Run, type ncpa.cpl, and then click OK.
    2. Right-click the network connection that you want to configure, and then click Properties.
    3. If the connection is a local area connection, click the General tab, click Internet Protocol [TCP/IP] in the This connection uses the following items box, and then click Properties. If the connection is not a local area connection, click the Networking tab.
    4. Click Advanced, and then click the WINS tab.
    5. In the NetBIOS setting area, click Disable NetBIOS over TCP/IP.
    6. Click OK three times.

MORE INFORMATION

WARNING: 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. To successfully apply this hotfix, you must add the ScavengerTimeLimit value to the registry. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters

  3. Right-click Parameters, point to New, and then click DWORD value.
  4. Type ScavengerTimeLimit, and then press ENTER, to name the new value.
  5. Double-click ScavengerTimeLimit.
  6. In the Value data box, type 60, and then click OK.
  7. Close Registry Editor.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Modification Type:MinorLast Reviewed:10/10/2005
Keywords:kbHotfixServer kbQFE kbQFE kbWinXPsp2fix kbWinXPpreSP2fix kbfix kbbug KB816073 kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.