Re: Infinite loop attempting to find DHCP

Hello Phil,
please try gPXE. gPXE will exit and continue with the next boot device
after the DHCP request failed(unless your BIOS has issues with
that...). You shouldn't use Etherboot anymore if you don't really need
to, as it's unsupported and hasn't been updated in a while.

Thomas

On Fri, Dec 11, 2009 at 9:50 PM, Phil Selmer <[email protected]> wrote:
>
> I'm wondering if there is any way to have Etherboot quit and continue with
> the normal boot sequence if there is no DHCP server found.  I've tried
> multiple options from Rom-o-matic, but can't get one that will work.
>
> Currently, it will load the BIOS extension and ask "Boot from (N)etwork or
> (Q)uit" for the default 3 seconds before attempting to boot the default
> (which is network).  If it can't connect to a DHCP server, it asks again and
> waits 3 seconds.  It will do that indefinitely.
>
> Is there any way to have it quit if it can't find the DHCP server?  If a
> Rom-o-matic solution exists, I would prefer that as I do not have access to
> a Linux box.
>
> Thanks in advance.
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
> _______________________________________________
> Etherboot-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>
>

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev