Christoph Plattner [EMAIL PROTECTED] writes:
If (only if so) the loader expects an image of one block, loaded at
0x1 and with an entry point of 0x1 then you have a chance by
changing the nbiloader.S file (removing the first 32bytes of the
data table and set there a jump to the
marco grigull [EMAIL PROTECTED] writes:
I am interested if this can load /boot (openbsd's boot loader) as it
also has this the problem of not being allowed to load under 1 MB.
No, it won't do that. Accessing memory beyond the first MB is not
that trivial. I think this has to be implemented
I've got a NIC (3com 3c905c TX-M) which supports BOOTP and can load
images up to a certain size (~450 KB) via TFTP. Unfortunately, the
image is stored at address 0x1 and onwards, so I couldn't any of
the existing boot loaders, and couldn't load the 'diskless' image
directly. In order to
On Sun, Mar 04, 2001 at 01:18:45PM +0100, Florian Weimer wrote:
I've got a NIC (3com 3c905c TX-M) which supports BOOTP and can load
images up to a certain size (~450 KB) via TFTP. Unfortunately, the
image is stored at address 0x1 and onwards, so I couldn't any of
the existing boot
The nbiloader.S already does this job. The etherboot/netboot stuff also
only can load not below 0x1 and so the loader includes a routine,
copy
the diskless code down to 0x8200.
But you have to check the protocol of the loading itself. nbiloader.S
uses
the netboot protocol used by etherboot
