Re: BIOS bootloader not working

From: Peter Beard (mail[REMOVE)
Date: 12/06/04


Date: Mon, 6 Dec 2004 14:21:55 -0000

Mello,

Join the club, I've been trying to get this to work for over a week without
much success or help :(

the information you are getting is exactly like mine except for an extra
warning...

INFO: code=0x4 // File found
INFO: code=0x4 // File found
INFO: code=0x4 // File found
WARNING: code=0x05 // Unable to reset disk controller
ERROR: code=0x1 // Unknown file system
ERROR: code=0xD // Failed to read data from storage
ERROR: code=0xB // Cannot read record information
INFO: code=0x37 // Trying backup image file
ERROR: code=0x1 // Unknown file system
ERROR: code=0x3 // Couldn't read root directory sector
ERROR: code=0x8 // Failed to load BIN image

if you get any further please let me know as I am about to give up as I
can't see any solution; like wise if I manage to get it working then I'll
let you know.

make sure that you have the following files on your FDD/HDD:
eboot.bix, splash.bmx, boot.ini

the bios loader will only build in release mode. (build -c, sysgen) the file
bldr should then be in your _FLATRELEASEDIR which you can transfer to your
setup disk and then use mkdisk as directed in the msdn documentation.

building the biosloader is one thing modifying it is another! if you change
more than a couple of lines it will crash either just after or during the
display of Microsoft Windows CE Boot Loader version 2.2....

hope this helps :) I know its not much but at least I can save you a week of
pain :-)

Regards...

P.

"cmello" <cmello@discussions.microsoft.com> wrote in message
news:FB58DFF7-7F80-4150-A916-D5C4AB3F4518@microsoft.com...
> Hello!
>
> I can successfully boot from the nwtwork with eboot, but I'm not having
> success with the BIOS bootloader.
>
> I've tried the standard one installed by the setupdisk floppy, available
> at
> \WINCE500\PUBLIC\COMMON\OAK\CSP\X86\BIOSLOADER\DISKIMAGES.
>
> It tries to access the floppy disk, and dumps the following message
> through
> the serial port:
>
> Microsoft Windows CE BIOS Bootloader Version 2.2 (Built Mar 13 2004)
> INFO: code=0x4.
> INFO: code=0x4.
> INFO: code=0x4.
> ERROR: code=0x1.
> ERROR: code=0xD.
> ERROR: code=0xB.
> INFO: code=0x37.
> ERROR: code=0x1.
> ERROR: code=0x3.
> ERROR: code=0x8.
>
> I'm still reading the docs to find out how to compile the boot loader with
> debug messages, but if you can help me on this one, it would be great.
>
> Thank you a lot for the attention!
> Mello



Relevant Pages

  • Re: libata in 2.4.24?
    ... IDE disks report immediate success even before the ... The way CONFIG_IDE (the traditional IDE driver) and libata work right ... > until the write hits disk. ...
    (Linux-Kernel)
  • Re: Cloning my C Drive onto D...
    ... I've cloned my C drive onto D twice, both with equal success (or ... and boot up from IDE2 goes ahead as normal. ... Depending on how you did it, your cloning may ... > a) By using a commercial disk imaging program such as the one ...
    (microsoft.public.win2000.general)
  • No space left on device
    ... Disk /dev/hdc: 40.0 GB, 40016019456 bytes ... 255 heads, 63 sectors/track, 4865 cylinders ... Device Boot Start End Blocks Id System ... Then I tried the command "touch a" without success. ...
    (RedHat)
  • second drive is not booting
    ... I have tried recovery without success (Fixmbr). ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: no publickey auth with OpenSSH_3.7.1p2 and HPUX11i
    ... I do it but no success :-((, the same debug messages and password-query. ... Wolfram ...
    (comp.security.ssh)