Re: [Etherboot-developers] booting non linux images

[Anuradha R. <anu...@gn...>]

Dear Ken,

I got the tagged image completed, but it didn't boot. Rather it rebooted!

What I did was to create a tagged image such that

1. The loading address of first 512 bytes of the image itself is 9320:0000
2. Start address is 9000:0200
3. Bootsector is loaded at 00090000 (512/512 - memory / image length)
4. Setup is loaded at 00090200 (2048/2048)
5. The rest is loaded at 00010000 (65020/65020 as of precomp.bin -precompiled
   image)

The total size of precomp.bin is 512+2048+65020=67580 and the tagged image
is 512 bytes larger.

Any suggessions would be highly appreciated.

Anuradha

PS: Yes. I checked the tagged image with both disnbi and hexdump. The rest
of the first 512 bytes were padded with zeros.

On Wed, 16 May 2001, Ken Yap wrote:

> >See if this two line change to mknbi.pl makes it work on memtest86.bin
> 
> Actually on looking at memtest86/setup.S, it won't work, because
> first32.c writes to various locations in the setup segment, and will
> overwrite valid code because memtest86/setup.S doesn't have those memory
> areas reserved. So yes, you need to make a tagged image builder for it.
> Pity you didn't write an function in mknbi.pl to do it.
> 
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> http://lists.sourceforge.net/lists/listinfo/etherboot-developers
>