Re: [Etherboot-developers] etherboot Ver. 4.7.23

[Ken Y. <ke...@nl...>]

|>Perhaps you might like to analyse why it works and
|is there a way to debug etherboot and/or with file is to edit for a
|printf?
|
|>what it tells you about what the BIOS is expecting.
|hmm...
|there is a USB-bug in this BIOS-Vers. The networkhardware don't works
|when USB is enebeld (on Windows and Linux) ?!?!

You have to work out, possibly with the help of documentation from the
BIOS manufacturer, what mechanism is used to give control to the
extension BIOS. From the symptoms, it appears the BIOS is not PnP
compliant but it does call the ROM at the +3 entry point when it detects
the BIOS, which is legacy (ISA) ROM behaviour. However the BIOS does not
appear to boot by calling INT 0x19 after all devices have initialised so
even though Etherboot has hooked that interrupt, it isn't getting
called. It must have its own startup mechanism. The fact that the USB
device seems to disrupt the network booting points to this also. So you
have to get more documentation from the mfr and study it. In summary,
it's not Etherboot you have to debug, it's the mfr's BIOS.