Article ID: 321172
Article Last Modified on 2/1/2007
APPLIES TO
- Microsoft Encarta Reference Suite 2001
This article was previously published under Q321172
SYMPTOMS
Windows CE does not start if you use a boot loader that uses an AM33 interrupt.
CAUSE
Windows CE expects a value of zero at INT_CODE for the AM33 Trap Base Register (TBR) when Windows CE starts and constructs the interrupt vector table. If a boot loader uses interrupts before this point, INT_CODE is set to a non-zero interrupt number. This causes Windows CE not to work during the construction of the interrupt vector table.
RESOLUTION
A supported software update is now available from Microsoft as Windows CE 3.0 Core OS QFE Q321172. To resolve this problem immediately, click the following article number for information about obtaining Windows CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows CE Platform Builder products
The English version of this package should have the following file attributes or later:
Size File name ---------------------------------------- 2,062,680 020430_am33_wce30-q321172.exe
The English version of this fix should contain the following files, with the listed file attributes or later:
Date Time Size File name ------------------------------------------------------------------------------------- 11-Apr-2002 18:41 1,359,412 public_common_oak_lib_amxx_am33_ce_debug_nkmain.lib 11-Apr-2002 18:41 102,400 public_common_oak_lib_amxx_am33_ce_debug_nkmain.pdb 11-Apr-2002 18:41 1,552,058 public_common_oak_lib_amxx_am33_ce_debug_nkprmain.lib 11-Apr-2002 18:41 102,400 public_common_oak_lib_amxx_am33_ce_debug_nkprmain.pdb 11-Apr-2002 17:30 978,756 public_common_oak_lib_amxx_am33_ce_retail_nkmain.lib 11-Apr-2002 17:30 94,208 public_common_oak_lib_amxx_am33_ce_retail_nkmain.pdb 11-Apr-2002 17:31 1,151,420 public_common_oak_lib_amxx_am33_ce_retail_nkprmain.lib 11-Apr-2002 17:31 102,400 public_common_oak_lib_amxx_am33_ce_retail_nkprmain.pdb
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbbug kbfix kbqfe KB321172