On Thu, May 24, 2007 at 10:00:51AM -0500, Jason L Tibbitts III wrote:
>>>>> "BW" == Bruno Wolff
<bruno(a)wolff.to> writes:
BW> Because if the OS is borked, you might not be able to interrupt
BW> that next process.
So the first thing it should do is up the timeout and then set it back
after the boot process is done.
It's not as if issues like this haven't been solved elsewhere.
+1 Set it up expecting the boot to fail, and when it completes
successfully, set it back down. Windows notices when a previous boot
failed and offers you a menu without any keypresses...