I'd like to use the DN2800MT mobo in an embedded application. The one problem which could be fatal is that no matter how I configure it, there are conditions in which the BIOS will put up an error message and wait for user input, even if there is no keyboard connected. I'm not talking about the "A bootable device has not been detected error." That's fatal anyway. I'm talking about things like this:
The previous boot attempt failed.
Would you like to restore Fast Boot on the next boot? (Y/N)
Hitting reset results in the same message. Turning the power off and on again results in the same message. There is NO WAY that I can find to recover from this without plugging in a keyboard. (And of course, plugging in a monitor, so that you know why the system is just sitting there like an expensive brick.)
What can cause this to happen? Simple: interrupting the power at the point where the BIOS is about to try to load boot code from the boot device. This is something that can happen in the real world, in the course of general fiddling with the thing, for instance by turning the power on, and then kicking out the power cable by accident.
The BIOS obviously knows whether there is a keyboard connected: it only supports a USB keyboard. So why would it wait for input from a non-existent device?
I downloaded the tool for configuring the BIOS, hoping that there would be an option in there, but it only seems to give access to the same options that one gets in the BIOS screens themselves. Is there really no solution to this? I can't have people sending a unit back for service just because the BIOS is stuck in Stupid Mode.