Bootloader wince.net 4.2

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tweeeek (Tariq.Mahmood_at_nospam.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 14:38:11 +0100

Hi
My first bootloader was developed when I was working on wince300. It was
based on the Ethernet Boot Loader for the Intel SA-1110 development
plastform version 4.5. The bootloader overwrote files in the sa11x0bd
directory, you then had to create an EBOOT shortcut with a command line.
Building the bootloader generated along with other EBOOT.nb0 in
c:\wince300\ebootne2k.release.

When we moved to Wince.net 4.2 we kept to the same procedure for generating
the bootloader, only this time we didn't have to create an eboot shortcut,
we simply drop into DOS through platform builder and build the bootloader
from there.

We are moving to Xscale, obviously he bootloader will have to be modified to
run on the xscale, I would very much appreciate some advice on how to
handle the bootloader.
Do we stick to the way we have been building it for the strongarm,similar
method used from wince300 to wince420.

Or is there any other way of doing this, I've noticed an eboot directory in
platform\xsc1bd. The bootloader is the first bit I will need to get working
when we migrate from sa1110 to the xscale pxa255, I would like to migrate
the bootloader quickly and with minmal pain (thats probably what everyone
wants).

I'm not sure how to approach the bootloader and seem to be getting this
wrapped round my neck.

Regards