Select the product you need help with

Debug Is Not Initialized on Some Devices with 1394 PC Cards

Article ID: 315399 - View products that this article applies to.

This article was previously published under Q315399

SYMPTOMS

If you try to debug by using a 1394 PC Card, debugging may not be turned on in some cases.

This problem occurs because the hardware abstraction layer (HAL) may not wait long enough for the CardBus bus to be initialized. Or, in other cases, the HAL may not wait long enough for the card to be initialized after power is applied. When this occurs, Windows does not actually start in Debug mode even if you use the correct Boot.ini file switches and Kd1394.dll is loaded.

You can verify whether Debug mode is in use by building a program that contains the following sample code:

void main(void)  {
     _asm {  int 3 }
     return 0;

}

If Debug mode is in use, the program hangs (it breaks into the debugger) when you run this code. If Debug mode is not in use, you receive a Dr. Watson error message.

Back to the top | Give Feedback

RESOLUTION

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

(http://support.microsoft.com/kb/322389/EN-US/ )

How to Obtain the Latest Windows XP Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version      Size     File name
   ------------------------------------------------------
   27-Jan-2002  17:56  5.1.2600.28  101,376  Hal.dll
   27-Jan-2002  17:56  5.1.2600.28  128,000  Halaacpi.dll
   27-Jan-2002  17:56  5.1.2600.28   77,440  Halacpi.dll

   27-Jan-2002  17:56  5.1.2600.28  146,432  Halapic.dll
   27-Jan-2002  17:56  5.1.2600.28  130,048  Halmacpi.dll
   27-Jan-2002  17:56  5.1.2600.28  148,352  Halmps.dll
   27-Jan-2002  17:56  5.1.2600.28   75,136  Halsp.dll

Back to the top | Give Feedback

STATUS

Microsoft 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 Windows XP Service Pack 1.

Back to the top | Give Feedback