USB keyboard problem at boot

  • Merv

    Merv - 2013-10-16

    Boot time defrag won't work, it fails to detect one keyboard, finds another one, and then prompts me to press a key to exit. Here is the contents of the log:

    2013-10-16 16:54:20.117 INFO: winx_set_dbg_log: log_path = \??\C:\Program Files\UltraDefrag\logs\boot-startup-phase.log
    2013-10-16 16:54:20.600 INFO: winx_get_windows_boot_options: NOEXECUTE=OPTIN - 48
    2013-10-16 16:54:20.600 ERROR: winx_fopen: cannot open \??\C:\Windows\pending-boot-off: 0xc0000034 status: object name not found
    2013-10-16 16:54:22.238 ERROR: kb_open_device: cannot open \Device\KeyboardClass1: 0xc000000e status: device not found

    I'm using the Windows 7 64-bit version.

    Last edit: Merv 2013-10-16
  • Stefan Pendl

    Stefan Pendl - 2013-10-17

    There are two stages of keyboard detection at boot, since some keyboards need some time to get online.

    The procedure is as follows:

    1. detect keyboards
    2. allow exit within 10 seconds, if one keyboard is functional
    3. detect keyboards anew to also get access to late registering keyboard drivers
    4. allow exit within 5 seconds

    This is the most reliable procedure that we found to handle late registering keyboards, without other users having to wait too long.

    In general boot time processing is done unattended, so the keyboard detection is not an issue at all.


    Last edit: Stefan Pendl 2013-10-17

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks