> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.0/user-guide/user-interface/menu-bar/windows.md).

# Windows

This submenu allows you to manipulate windows on the screen. You can also:

* [Set video mode...](#set-video-mode) (text version)
* [Invoke external help](#invoke-external-help)
* [Consult keyboard layout](#keyboard-layout) (text version)

See also [Menu Bar](/9.0/user-guide/user-interface/menu-bar.md) submenus.

### Set Video Mode

```
Action    name: SetVideoMode
 
```

This command changes the current video mode. The list of allowed video modes is kept in the IDATUI.CFG file, the SCREEN\_MODES parameter.

Please note that there are two instances in this variable: one for MS-DOS and another for Windows.

If you use the MS DOS version, you need to specify the screen mode numbers valid for you video card in SCREEN\_MODES. Otherwise, this command will not work.

### Invoke external help

```
Action    name: ExternalHelp
 
```

This command invokes an external help.

In the MS Windows version of IDA, it starts WinHelp with the parameter taken from the cursor location.

The HELPFILE parameter in IDATUI.CFG/IDAGUI.CFG points to the help file name.

### Keyboard layout

```
Action    name: KeyboardHelp
 
```

This command displays the current keyboard layout.

You can change the layout in the configuration file

```
        IDATUI.CFG (for the text version)
        IDAGUI.CFG (for the GUI version)
```

This command is available in the text version only.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/9.0/user-guide/user-interface/menu-bar/windows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.