lschultz@x2.alliance.net writes: > On Sun, Oct 05, 1997 at 12:45:09PM +0200, Gero Kuhlmann wrote: > > Maybe you can find out if you can remove your installed Koeppen > > bootrom and if it's possible to replace it by the one contained > > in neboot or etherboot. Then you will be able to simply use > > mknbi-linux for booting Linux. If you have an EPROM burner, then it might be worthwhile to remove the system's BIOS PROM chip and check its contents. If you are lucky, then the Koeppen Bootrom code is merely prepended to the rest of the system BIOS; if this is the case, you can easily remove the Koeppen code and replace it with one of the freely available loaders. You can detect a rom extension by its magic header bytes. You should see 0x55 (this is hexadecimal 55 or decimal 85) followed by 0xAA followed by a single byte telling you the size of the extension in units of 512 bytes. Rom extensions usually start on 16kB boundaries, but I would not rely too much on this fact. At the very least if would also check all 4kB or even 1kB boundaries. If you have a hex-editor (e.g. Emacs's hexl-mode), then it should be very obvious to tell, whether there are ROM extensions present. Markus -- Markus Gutschke Internet: markus@infoscape.com Infoscape, Inc Phone: +1-415-537-3778 657 Mission Street, Suite 200 San Francisco, CA 94105 Disclaimer: The above message represents my personal opinion; It does not constitute an offical statement by Infoscape!
For requests or suggestions regarding this mailing list archive please write to netboot@gkminix.han.de.