> For the complete documentation index, see [llms.txt](https://cytrence.gitbook.io/cytrence-kiwi-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cytrence.gitbook.io/cytrence-kiwi-document/faq/how-to-access-bios-on-the-target-device.md).

# How to access BIOS on the target device?

While Kiwi provides instant access to the target device, including the BIOS screens during boot-time, some ancient version of BIOSes may require a bit  additional steps for symptoms listed below:

* **Why there is a warning `No Video Input` for BIOS screen?**

  If there is a warning `No Video Input` on the right-bottom corner of Kiwi app window, it indicates no video output from the target device. If the video cable is plugged on and the screen come through after booting, there can a few reasons special to BIOS:

  * Computers with multiple video outputs may only send the BIOS screen to the Primary video output without mirroring to other outlets
  * Some server blades maybe have set the primary video OFF by default

  In such cases, please connect Kiwi to the primary video output and make sure it is ON to output the video signal. If the Kiwi App window shows all blank without warning, please collect the diagnostic information from the 'About' dialog and contact <support@cytrence.com>.

* **Why BIOS is not responding to keystrokes typed onto Kiwi App?**

  Some legacy devices only accept legacy mode for USB keyboards. In that case, check the '***Legacy Keyboard Mode***' option in [KB/Mouse Tab](/cytrence-kiwi-document/kiwi-settings/kb-mouse-tab.md) (even just temporarily) for better compatibility with BIOS.

{% hint style="info" %}
Some host computers, especially laptops, requires pressing `Fn` or `Function` key together in order to activate the function keys such as `F2` or `F10` to enter BIOS.
{% endhint %}

* **Why neither keyboard nor mouse works in BIOS mode?**\
  With the default '***Desktop Integration Mode***', some special keystrokes required for BIOS access can be intercepted by the host operating system; similarly, the mouse event capture for BIOS screen may also be distracted by the host desktop.  Switching the '***Interaction Mode***' to '***Capture/Release Mode***' in[General Tab](/cytrence-kiwi-document/kiwi-settings/interactive-blocks.md) will allow full range of keyboard/mouse capture in BIOS and will fix most of the HID-related issues.

{% hint style="info" %}
In either Interaction Mode, the Kiwi App window must be in-focus:

* In 'Desktop Integration Mode': click the Kiwi App's title bar to ensure in-focus
* In 'Capture/Release Mode': click inside the Kiwi App's main window (the target screen) to enter Capture mode (press Ctrl-Alt to Release)

&#x20;Otherwise, the keyboard/mouse events will not be captured by Kiwi App.&#x20;
{% endhint %}

* **Why mouse still doesn't work in BIOS even with 'Capture/Release Mode'?**

  Some version of BIOSes, including some from renown vendors, has GUI in BIOS but only support mouse in '***Boot-Mode***' which differs from regular mouse protocol over USB. The Kiwi App provide seamless way to enable mouse '***Boot-Mode***' mode. See [BIOS/Boot-Time Access](/cytrence-kiwi-document/kiwi-standard-features/bios-boot-time-access.md) for details.