Mailing List Archive

Hi,

"Matthias Hunstig" <mhauktion@gmx.net> schrieb am 30.03.02:
> I use Syslog on a 486/66 Fli4L-DSL-Router in our family LAN. When the router
> started today, Syslinux asked for "boot:", which it had never done before.
> The Timeout parameter was set to 0. I have also tried to run it without any
> timeout parameter in syslinux.cfg, still the same problem.
> Do you have any idea what might be the reason for Syslinux to wait for
> input?

If any modifier key (Shift, Control, Alt) is pressed syslinux (also
pxelinux and isolinux AFAIK) does this. Maybe your keyboard has
some stuck keys?

Regards,

Josef

______________________________________________________________________________
Handeln wie die Profis, ganz ohne Risiko. Steigen Sie ein und erleben
Sie Berg- und Talfahrt an den Börsen unter http://boersenspiel.web.de

-----Ursprüngliche Nachricht-----
Von: "Josef Siemes" <jsiemes@web.de>
An: "Matthias Hunstig" <mhauktion@gmx.net>; <syslinux@zytor.com>
Gesendet: Sonntag, 31. März 2002 16:12


>>"Matthias Hunstig" <mhauktion@gmx.net> schrieb am 30.03.02:
>> I use Syslog on a 486/66 Fli4L-DSL-Router in our family LAN. When the
router
>> started today, Syslinux asked for "boot:", which it had never done
before.
>> The Timeout parameter was set to 0. I have also tried to run it without
any
>> timeout parameter in syslinux.cfg, still the same problem.
>> Do you have any idea what might be the reason for Syslinux to wait for
>> input?
>
>If any modifier key (Shift, Control, Alt) is pressed syslinux (also
>pxelinux and isolinux AFAIK) does this. Maybe your keyboard has
>some stuck keys?

Hi,

you were right, Capslock was stuck, now it works again. Thanks.

Matthias