Adding Etherboot to bios - problems w/ some machines
Posted: Fri Aug 05, 2005 6:28 pm
I am building terminal clients from old PC's(P166, award bios v4.51PG on all of them, only different mobos[some got replaced by warranty], other components same). The machines have a NE2k nic and I am trying to add etherboot into bios to elliminate any hard disk/floppy disk/cd drives. On one machine, I managed to get this working:
* removed unneccecary components with cbrom215 to make room for etherboot
* added etherboot to bios (/isa, c800:0)
* enabled with modbin video rom options (for the bios to search rom-s)
* flashed the bios
" configured the net adapter to io 300, irq3; disabled boot rom socket from net adapter (otherwise it overwrited the rom from bios)
But on other machines it does not work anyhow. I tried to replace all the hardware, but still nothing. It even does not extract the added isa rom to memory.
So, the question is: Does Award limit (compile time?) some bios modular functionality for some vendors, so that with some biosses it is not possible to add additional rom modules? (they get added by cbrom but not extracted/excecuted). Some sites say, that it does. Any suggestions to circumvent this issue? What about trying to use a bios program from a motherboard of same chipset?
* removed unneccecary components with cbrom215 to make room for etherboot
* added etherboot to bios (/isa, c800:0)
* enabled with modbin video rom options (for the bios to search rom-s)
* flashed the bios
" configured the net adapter to io 300, irq3; disabled boot rom socket from net adapter (otherwise it overwrited the rom from bios)
But on other machines it does not work anyhow. I tried to replace all the hardware, but still nothing. It even does not extract the added isa rom to memory.
So, the question is: Does Award limit (compile time?) some bios modular functionality for some vendors, so that with some biosses it is not possible to add additional rom modules? (they get added by cbrom but not extracted/excecuted). Some sites say, that it does. Any suggestions to circumvent this issue? What about trying to use a bios program from a motherboard of same chipset?