>> I thought of one other possibility to try. We might be stomping BIOS tables
>> if etherboot is loading to high. Setting RELOCADDR lower might be worth
>> a shot.
Another idea: There is the possibility for etherboot to load the hda
MBR as boot block (or hdX-partitions even). Couldn't we establish an
option LOCALBOOTDEVICE= for this purpose (if set, then instead of
returning to BIOS for local boot, get the MBR ourselves)?
I know this is really against reason on working machines, but
obviously, that machines isn't working as it should. And this way, you
could hinder users from tampering with the Bios boot device settings,
as (at least for my setup) no matter that setting, Etherboot ROM to be
first boot priority. Even if user can crack the BIOS-Password (by
looking over someone's shoulder, for example) they could NOT
floppy-boot anyway...
Just an idea.
Anselm
|