|
From: Eric W B. <ebi...@ln...> - 2002-09-18 21:09:54
|
Anselm Martin Hoffmeister <ans...@gm...> writes: > > Last time I tried 5.1, it failed to even detect my BIOS. I'm think this > > is an E820-related problem that I've fixed once before already, but I just > > don't have time to hack on Etherboot at the moment. However, if someone > > can tell me why, on some machines, Windows 98 takes forever (45 mins+) to > > start up if booted via Etherboot's "Boot (L)ocal" option, then I might > > regain some spare time. :-) > > Could it be that the Etherboot code doesn't safely deactivate your hardware? > (But it shouldn't have initialized it if asking for "local boot", does it?) > However, you could have a look into the code. Only if it times out, and retries the boot process. > BTW: Try setting your BIOS to "PNPOS=No" for that board-not-found problem. > That seems to have helped several people with similar problems on other NICs. Click. PNPOS=Yes implies the OS can assign resources to the device. And we verify that some Resource is assigned to the pci device. The BIOS should assign all resouces to boot devices but it is quite possible to overlook a NIC as a boot device. Eric |
