Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Jumping to 0x00226d10 error in Windows CE 6.0 during boot

Status
Not open for further replies.

k7gada

Programmer
Aug 22, 2011
2
GB
senrdev (Programmer)
31 Mar 09 17:41
I am in the process of evaluating CE 6 for a new small device project

It is my first time with CE (I have successfully built Embedded XP but want to see the differences as CE is cheaper and may be better suited)

I would like to try of my software on CE and want to initially try it on standard size laptops before I start the process of building for a specific small device

I have built some CE 6 images with Platform Builder

After some initial issues I now get "nk.bin" images ok but I have no luck at all in getting over a "jumping to 0x00226d10" message when I try to run the image (from a dos diskette I created using the Platform Builder tool) - it seems to start displaying a number of lines, then gets the "jumping" display

I have tried various builds on 3 different laptops (different makes/models) - absolutely no difference, same message

I have seen various tips on forums and have actted on several - no joy. The most common tip is to use vesatest to test and then adjust the screen resolution in the loadcepc command - no difference (except size of the "jumping" message). If that was an issue would it not know how to display anything?

I see some tips about playing with config.bib. Surely this is built as a default? I do not configure anything special - I just want a basic CE system up and running on a standard laptop - is it possible without a specific device? I have tried several types, custom,
small footprint and thin - no difference, same message

Can anyone help?

Thanks
 
I got this problem solved this way
================================
The problem in this case is that bootloader is unaware of the display resolution or it has a wrong resolution. So to check the resolution that are supported by the target device.
==============================================


During boot you are asked few options as
1.load nk.bin locally
2.through eboot
3.sboot and
4.vesatest

.........................
select vesatest option which will show you the accepted resolutions
select any one and put it below
then write in the commandline
for example
-----------------------------
loadcepc /v /l:800x600x32 nk.bin
-----------------------------

thats it Wince will be up and running
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top